Have you symlinked /etc/nginx/sites-available/mysite.comto /etc/nginx/sites-enabled/ mysite.com ?
Karl Sutt On Thu, May 3, 2012 at 10:23 PM, easypie <program...@gmail.com> wrote: > I'm not sure if I should post this in this thread of mine or start new > one. But it's still about the config files. > > After getting uwsgi to work. I tried to link nginx w/ it but that didn't > work. I go to localhost:80 and that takes me to the welcome page: "Welcome > to Nginx!". When I go to localhost:8000 (which I want), it doesn't load > (unable to connect). Please take a look at the code: > http://dpaste.org/oIjP9/ > > > On Thursday, May 3, 2012 10:22:54 AM UTC-7, Kurtis wrote: >> >> Hey, I'm glad to hear you got it working! If you run into any more >> problems, don't hesitate to ask. >> >> On Wed, May 2, 2012 at 1:31 AM, easypie <program...@gmail.com> wrote: >> >>> Thanks. I was missing the virtualenv=<path> mentions earlier. I'm glad I >>> know this those settings are meant for development only. I was a little >>> confused thinking that was ready for deployment. I'm new to all this and >>> get confuse sometimes. >>> >>> >>> On Tuesday, May 1, 2012 8:04:00 AM UTC-7, Kurtis wrote: >>>> >>>> Judging from your Import Error -- I think you're having a problem with >>>> Django not being on the Python path. In my uwsgi configuration file (I used >>>> .xml), it looks like this: >>>> >>>> <uwsgi> >>>> <master/> >>>> <env>DJANGO_SETTINGS_MODULE=**fi**reflie.settings</env> >>>> <processes>4</processes> >>>> <socket>0.0.0.0:7999</socket> >>>> <chdir>/home/fireflie/staging/****fireflie/</chdir> >>>> <module>django.core.handlers.**w**sgi:WSGIHandler()</module> >>>> <pythonpath>/home/fireflie/**sta**ging/fireflie/</pythonpath> >>>> <pythonpath>/home/fireflie/**sta**ging/</pythonpath> >>>> <daemonize>/var/log/uwsgi/**uwsg**i.log</daemonize> >>>> <pidfile>/tmp/fireflie-**staging**.pid</pidfile> >>>> </uwsgi> >>>> >>>> Note: That's not guaranteed to be production-ready (we're just using it >>>> for development) and I'm also not using a virtual environment (we use a >>>> whole sever for the single Django application). In other words, I'm not >>>> following best practices by a large margin. Good luck! >>>> >>>> >>>> On Mon, Apr 30, 2012 at 7:36 PM, Karl Sutt <k...@sutt.ee> wrote: >>>> >>>>> I am not entirely sure what you mean by that. If you mean the nginx >>>>> equivalent of Apache VirtualHosts then the nginx wiki explains it quite >>>>> nicely >>>>> http://wiki.nginx.org/**S**erverBlockExample<http://wiki.nginx.org/ServerBlockExample>. >>>>> Is that what you meant? >>>>> >>>>> Karl Sutt >>>>> >>>>> >>>>> >>>>> On Mon, Apr 30, 2012 at 7:04 PM, easypie <program...@gmail.com> wrote: >>>>> >>>>>> does your configuration allow for running multiple sites? >>>>>> >>>>>> >>>>>> On Sunday, April 29, 2012 12:01:27 PM UTC-7, Karl Sutt wrote: >>>>>>> >>>>>>> Here is my uWSGI command and nginx.conf contents: >>>>>>> >>>>>>> uwsgi -- >>>>>>> http://www.dpaste.org/**aiJuq****/<http://www.dpaste.org/aiJuq/> >>>>>>> nginx -- >>>>>>> http://www.dpaste.org/**bAG0o****/<http://www.dpaste.org/bAG0o/> >>>>>>> >>>>>>> I've used it for a Flask application, but I've just tested it and it >>>>>>> works for a Django project as well. Note that wsgi.py file in the uwsgi >>>>>>> command is the Python file that Django generates when you first create a >>>>>>> project, there is no need to change it. >>>>>>> >>>>>>> Good luck! >>>>>>> >>>>>>> Karl Sutt >>>>>>> >>>>>>> >>>>>>> On Sun, Apr 29, 2012 at 6:49 PM, easypie <program...@gmail.com>wrote: >>>>>>> >>>>>>>> I have this file that was created for me by one of the users in >>>>>>>> django's irc channel. I edited to have the right information inserted >>>>>>>> but >>>>>>>> I"m not sure what I'm doing wrong to not make it work. I've spent some >>>>>>>> time >>>>>>>> trying to understand each line by searching the web. There's still a >>>>>>>> thing >>>>>>>> or two that's missing from the puzzle. Maybe it's the server config >>>>>>>> that >>>>>>>> has a flaw or the way I went about it. I haven't done a fresh install >>>>>>>> of >>>>>>>> uwsgi and nginx yet. However, please take a look to see if there's an >>>>>>>> error >>>>>>>> or solution that could work. Thanks. >>>>>>>> >>>>>>>> Link to code: >>>>>>>> http://www.dpaste.org/**wW****Vd3/<http://www.dpaste.org/wWVd3/> >>>>>>>> >>>>>>>> -- >>>>>>>> You received this message because you are subscribed to the Google >>>>>>>> Groups "Django users" group. >>>>>>>> To view this discussion on the web visit >>>>>>>> https://groups.google.com/d/**ms****g/django-users/-/**2rekHP0I6V0J<https://groups.google.com/d/msg/django-users/-/2rekHP0I6V0J> >>>>>>>> . >>>>>>>> To post to this group, send email to django-users@googlegroups.com. >>>>>>>> To unsubscribe from this group, send email to >>>>>>>> django-users+unsubscribe@**googl****egroups.com<django-users%2bunsubscr...@googlegroups.com> >>>>>>>> . >>>>>>>> For more options, visit this group at http://groups.google.com/** >>>>>>>> group****/django-users?hl=en<http://groups.google.com/group/django-users?hl=en> >>>>>>>> . >>>>>>>> >>>>>>> >>>>>>> -- >>>>>> You received this message because you are subscribed to the Google >>>>>> Groups "Django users" group. >>>>>> To view this discussion on the web visit https://groups.google.com/d/ >>>>>> **ms**g/django-users/-/**sMsRN5iG9NQJ<https://groups.google.com/d/msg/django-users/-/sMsRN5iG9NQJ> >>>>>> . >>>>>> >>>>>> To post to this group, send email to django-users@googlegroups.com. >>>>>> To unsubscribe from this group, send email to >>>>>> django-users+unsubscribe@**googl**egroups.com<django-users%2bunsubscr...@googlegroups.com> >>>>>> . >>>>>> For more options, visit this group at http://groups.google.com/** >>>>>> group**/django-users?hl=en<http://groups.google.com/group/django-users?hl=en> >>>>>> . >>>>>> >>>>> >>>>> -- >>>>> You received this message because you are subscribed to the Google >>>>> Groups "Django users" group. >>>>> To post to this group, send email to django-users@googlegroups.com. >>>>> To unsubscribe from this group, send email to >>>>> django-users+unsubscribe@**googl**egroups.com<django-users%2bunsubscr...@googlegroups.com> >>>>> . >>>>> For more options, visit this group at http://groups.google.com/**group >>>>> **/django-users?hl=en<http://groups.google.com/group/django-users?hl=en> >>>>> . >>>>> >>>> >>>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Django users" group. >>> To view this discussion on the web visit https://groups.google.com/d/** >>> msg/django-users/-/**cPvZyCPXPNUJ<https://groups.google.com/d/msg/django-users/-/cPvZyCPXPNUJ> >>> . >>> >>> To post to this group, send email to django-users@googlegroups.com. >>> To unsubscribe from this group, send email to django-users+unsubscribe@* >>> *googlegroups.com <django-users%2bunsubscr...@googlegroups.com>. >>> For more options, visit this group at http://groups.google.com/** >>> group/django-users?hl=en<http://groups.google.com/group/django-users?hl=en> >>> . >>> >> >> -- > You received this message because you are subscribed to the Google Groups > "Django users" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/django-users/-/lU_hOfkWep0J. > > To post to this group, send email to django-users@googlegroups.com. > To unsubscribe from this group, send email to > django-users+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/django-users?hl=en. > -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
