On Wed, Feb 9, 2011 at 11:38 AM, Dev@CB <d...@churchbudget.com> wrote:
> Well, the "python manage.py runserver" command returned a screen full > of errors. What would be the appropriate way to post that? I don't > want to burn anyone's special eyes. > And since we are using Apache, I'm going to say we are also using > wsgi. > > > Well, the first thing to see when deploying a django project is the > > settings.py file. Here you'll see the database information. > > > > Then the second step will be testing it (with the command python > > manage.py runserver, it should start the development server, NOT for > > using in production). > > > > The last thing will see the Apache configuration, and it'll depend if > > you're using wsgi or fcgi... More information here: > http://docs.djangoproject.com/en/dev/howto/deployment/http://www.djangobook.com/en/beta/chapter21/ > > > > Hope it isn't that difficult, you can see the configs from the old > > server, right? > > > > Good luck! > > Andres- Hide quoted text - > > > > - Show quoted text - > > -- > 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. > > As far as getting errors on the development server, you need to look in settings.py. The values in this file will be different for development than for the production machine. Find the development version of this file. (It might be similarly named) -- Joel Goldstick -- 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.
