Apache is slower, heavier and more complicated to setup than Nginx. But it’s also -much more famous:
+Apache is heavier than Nginx. But it’s also much more famous:
This setup is considered as slow, but you will still benefit from Apache -robustness.
+First, make sure you have mod_wsgi installed and enable by running (as admin):
+a2enmod wsgi
+This enable mod_wsgi. It it doesn’t, install it first (on ubuntu, the package +is libapache2-mod-wsgi).
+Then create an Apache configuration file, usually in /etc/apache/sites-available/. +Name it zerobin:
+<VirtualHost *:80>
+ ServerName www.yourwebsite.com
+
+ WSGIDaemonProcess zerobin user=www-data group=www-data processes=1 threads=5
+ WSGIScriptAlias / /path/to/zerobin/app.wsgi
+
+ <Directory /path/to/zerobin/zerobin/>
+ WSGIProcessGroup zerobin
+ WSGIApplicationGroup %{GLOBAL}
+ Order deny,allow
+ Allow from all
+ </Directory>
+</VirtualHost>
+Activate the website (as admin):
+a2ensite zerobin
+And reload the apache configuration (as admin):
+service apache2 reload
+You’ll note that we refer to a file named app.wsgi. It’s a Python file +creating the application Apache is going to use to start the Python process:
+import os, sys
+
+# make sure the zerobin module is in the PYTHON PATH and importable
+ZEROBIN_PARENT_DIR = os.path.dirname(os.path.dirname(__file__))
+sys.path.insert(0, ZEROBIN_PARENT_DIR)
+
+# create the wsgi callable
+from zerobin.routes import get_app
+settings, application = get_app(compressed_static=True)
+You can of course create your own, as the get_app function is the only +way to pass settings to 0bin with this setup. You would do this by creating +a configuration file and passing it to the function:
+import os, sys
+
+ZEROBIN_PARENT_DIR = '/path/to/zerobin/parent/dir'
+sys.path.insert(0, ZEROBIN_PARENT_DIR)
+
+from zerobin.routes import get_app
+settings, application = get_app(settings_file='/path/to/settings.py')
+You can also run 0bin using CGI, but infortunaly we didn’t have time to cover +it yet. Please contact us if you ever get the need to use it.
Vous must create a Nginx configuration file for 0bin. On GNU/Linux, they usually go into /etc/nginx/conf.d/. Name it zerobin.conf.
-The minimal file to run the site is:
-But you can make some adjustement to get better perfomances:
+The minimal configuration file to run the site is:
+server {
+ listen 80;
+ server_name www.yourwebsite.com;
+
+ location / {
+ proxy_pass http://127.0.0.1:8000;
+ }
+}
+proxy_pass just passes the external request to the Python process. +The port much match the one used by the 0bin process of course.
+You can make some adjustements to get a better user experience:
+server {
+ listen 80;
+ server_name www.yourwebsite.com;
+
+ location /favicon.ico {
+ root /path/to/zerobin/static/img;
+ }
+
+ location /static/ {
+ root /path/to/zerobin;
+ gzip on;
+ gzip_http_version 1.0;
+ gzip_vary on;
+ gzip_comp_level 6;
+ gzip_proxied any;
+ gzip_types text/plain text/css application/json application/x-javascript text/xml application/xml application/xml+rss text/javascript;
+ gzip_buffers 16 8k;
+ # Disable gzip for certain browsers.
+ gzip_disable ~@~\MSIE [1-6].(?!.*SV1)~@~];
+ expires modified +90d;
+ }
+
+ location / {
+ proxy_pass http://zerobin_cherrypy;
+ }
+}
+This make Nginx serve the favicon and static files, set the expire HTTP headers +and make sure gzip compression is used with browsers that support it.
diff --git a/docs/.build/html/en/options.html b/docs/.build/html/en/options.html index cb523fb..e4d7409 100644 --- a/docs/.build/html/en/options.html +++ b/docs/.build/html/en/options.html @@ -51,12 +51,7 @@–host=STR
-The host on which to listen for incomming request. Usually 127.0.0.1 to -listen locally or 0.0.0.0 to listen from the outside.
-Default: 127.0.0.1 -Setting file : HOST
-0bin’s behavior can be adjusted with options passed using a configuration file or directly using the command line. Some parameters are only available diff --git a/docs/.build/html/en/theming.html b/docs/.build/html/en/theming.html index cf4712a..5671842 100644 --- a/docs/.build/html/en/theming.html +++ b/docs/.build/html/en/theming.html @@ -53,8 +53,8 @@
0bin comes a complete theming support, but for now it’s not well ingrated.
-If you wish to create your own theme, you’ll need to create template similar +
0bin comes with a complete theming support, but for now it’s not well integrated.
+If you wish to create your own theme, you’ll need to create templates similar to the ones in zerobin/view, and add the path to the director containing them to the settings file.
You’ll also need to copy static files from zerobin/static to a new direcotry diff --git a/docs/.build/html/en/using_supervisor.html b/docs/.build/html/en/using_supervisor.html index c55b3e7..c87f36a 100644 --- a/docs/.build/html/en/using_supervisor.html +++ b/docs/.build/html/en/using_supervisor.html @@ -26,8 +26,8 @@ - - + +
diff --git a/docs/.build/html/fr/using_supervisor.html b/docs/.build/html/fr/using_supervisor.html index 648fd87..b0fe78e 100644 --- a/docs/.build/html/fr/using_supervisor.html +++ b/docs/.build/html/fr/using_supervisor.html @@ -26,7 +26,7 @@ - + @@ -37,7 +37,7 @@ indexSupervisor est un très bon moyen de gérer des processus Python. Nous n’allons +pas couvrir son installation (qui la plupart du temps se résume à +apt-get install supervisor ou pip install supervisor), mais voici un rapide +résumé de comment l’utiliser:
+Créez un fichier de configuration nommé supervisor.ini:
+[unix_http_server]
+file=/tmp/supervisor.sock;
+
+[supervisorctl]
+serverurl=unix:///tmp/supervisor.sock;
+
+[rpcinterface:supervisor]
+supervisor.rpcinterface_factory=supervisor.rpcinterface:make_main_rpcinterface
+
+[supervisord]
+logfile=/tmp/zerobin.log
+logfile_maxbytes=50MB
+logfile_backups=2
+loglevel=trace
+pidfile=/tmp/supervisord.pid
+nodaemon=false
+minfds=1024
+minprocs=200
+user=zerobin
+
+[program:zerobin]
+command=/chemin/vers/zerobin/zerobin.py --port 80 --compressed-static
+directory=/chemin/vers/zerobin/
+environment=PYTHONPATH='/chemin/vers/zerobin/'
+user=zerobin
+autostart=true
+autorestart=true
+Les 4 premières entrées sont juste de la configuration standard et vous pouvez +les copier telles qu’elles.
+La dernière entrée définie un processus (il peut y en avoir plusieurs) +que supervisor doit gérer.
+Cela veut dire qu’il va lancer la commande:
+/chemin/vers/zerobin/zerobin.py --port 80 --compressed-static
+Et ceci dans le dossier, avec l’environnement et l’utilisateur défini, le tout +en arrière plan en tant que daemon.
+autostart et autorestart permettent simplement de le lancer et de l’oublier: +supervisor redémarera le processus automatiquement en cas d’arrêt impromptu.
+La première fois que vous lancez supervisor, passez lui le fichier de configuration:
+supervisord -c /chemin/vers/supervisor.ini
+Ensuite vous pouvez gérer les processus avec:
+supervisorctl -c /chemin/vers/supervisor.ini
+Cela va démarrer un shell depuis lequel vous pouvez faire un start/stop/restart +sur le service.
+Toutes les erreurs seront logguées dans /tmp/zerobin.log.
+Note
+Si vous avez installé zerobin dans un virtualenv, vous devriez définir la +commande pour qu’elle s’éxécute depuis le virtualenv:
+command=/chemin/vers/le/virtualenv/bin/zerobin --port 80 --compressed-static
+