-
Notifications
You must be signed in to change notification settings - Fork 436
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WSGI or similar deployment with Nginx #197
Comments
I managed to have it working with uWSGI. You need to use the radicale.wsgi entry point, which is present in the git tree, but not in the easy_install/pip package. Clone the git repo, and put something like this in your uwsgi config file
There is no really need for documentation, since it follows python's wsgi conventions, but .wsgi should be shipped with the easy_install/pip package. The Radicale team told me they are working on it. |
can you paste here complete radicale.ini config for uwsgi? thanks, |
who ? |
@chlarsen i'm running Radicale in a virtualenv behind gunicorn behind nginx, works well :) |
…on '/.web/': string indices must be integers, not 'str' when using LDAP Enhance logging
Dear All,
I have successfully installed Radicale 0.8, and am very impressed swith its size, speed and functionality. I managed to get somewhat better performance by disabling DNS lookups, und use LDAP at Radicale application level for user authentication. The whole thing sits behind an Nginx reverse proxy. While I am patiently waiting for the PostgreSQL backend to work proprely (hopefully with the next stable release?), I got stuck with donig any further (accelerating) magic with WSGI (or FastCGI) and Nginx. An documentation? Alternative, I have used gunicorn with great success in the Django domain- could this work here instead: Radicale -> Gunicorn -> Nginx reverse proxy?
Thanks a lot for this terrific peice of software, and your kind assistance.
Chris
The text was updated successfully, but these errors were encountered: