The minimalistic version of uwsgi script above was for debugging
purposes: all in one process, log output to screen, no memory limits
etc.

For virtualenv is very important the option
--home  /path/to/home/of/virtualenv

Then options can be tested and added one by one to create more
realistic configuration.

On 8 zář, 23:15, hynekcer <[email protected]> wrote:
> Although the Satchmo has some special solutions within the project
> (urls, optional modules loading etc.) from outside it is a common
> Django application and you can use any guidance for Django.
>
> A minimalistic configuration specific for uwsgi is
> == /etc/nginx/sites-available/yoursite
> # usual common static things ...
> ...
>         location / {
>                 # uWSGI server
>                 uwsgi_pass unix:///var/some/path.uwsgi.sock;
>                 include uwsgi_params;
>         }
> ...
>
> == project-startup-script-uwsgi
> #!/bin/bash
> uwsgi \
>           --pythonpath /var/yourprojectsdirectory \
>           --env DJANGO_SETTINGS_MODULE=yourprojectname.settings \
>           -w "django.core.handlers.wsgi:WSGIHandler()" \
>           -s /var/some/path.uwsgi.sock \
>           -C
> # I prefer easy option "-C", which means socket is created by uwsgi
> with permission 666. I manually restrict permissions of the directory
> where it is located.
>
> On 7 zář, 22:30, wizbit <[email protected]> wrote:
>
>
>
>
>
>
>
> > I am trying to get satchmo working with nginx + uwsgi.
>
> > I would very much like to see a nginx.conf and satchmo.wsgi example if
> > possible.

-- 
You received this message because you are subscribed to the Google Groups 
"Satchmo users" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/satchmo-users?hl=en.

Reply via email to