On Fri, 22 Jul 2016 00:39:07 -0300, Marcelo Santana <[email protected]> wrote:
[...] > The question is: > What would be the most appropriate way to solve this issue thinking > about future releases of weblate and perhaps packaging it in debian? I think now I have found a best solution. I started using mod_wsgi in daemon mode and now everything are working correctly even with the newest version of python-cryptography. I understood better after read this: https://github.com/pyca/cryptography/issues/2916 If someone is interested, below is an example of configuration file with mod_wsgi in daemon mode for Apache2: <VirtualHost *:80> ServerAdmin [email protected] ServerName example.com Alias /robots.txt /var/www/html/weblate/data/static/robots.txt Alias /favicon.ico /var/www/html/weblate/data/static/favicon.ico Alias /static/ /var/www/html/weblate/data/static/ <Directory /var/www/html/weblate/data/static/> Require all granted </Directory> WSGIDaemonProcess example.com python-path=/var/www/html/weblate WSGIProcessGroup example.com WSGIApplicationGroup %{GLOBAL} WSGIScriptAlias / /var/www/html/weblate/weblate/wsgi.py process-group=example.com WSGIPassAuthorization On <Directory /var/www/html/weblate/weblate/> <Files wsgi.py> Require all granted </Files> </Directory> </VirtualHost> Kind regards, -- Marcelo Santana (aka msantana) <[email protected]> 4096R/5B76053D: 8E9B 1014 4019 3526 C1C6 B0AC A3C0 DA1E 5B76 053D
pgp0MEJvYmnpq.pgp
Description: OpenPGP digital signature
_______________________________________________ Weblate mailing list [email protected] https://lists.cihar.com/cgi-bin/mailman/listinfo/weblate
