2016-08-24 17:54 GMT+02:00 Michael Macdonald <[email protected] >:
> Interestingly enough, just this morning, after a couple times being bitten > with differences in behavior between use of runserver in development vs. > wsgi in production, I've decided to do all development on my local machine > under lighttpd. In the process of (mis?)configuring it now. > > I'm pretty thoroughly convinced that using runserver isn't such a good > idea, nor is it particularly useful. Development I've done under Eclipse > and MS VisualStudio in the past did initial local unit testing on a local > server; there is ample precedent for this approach. And, it is best > practice to make the development environment as close to the same as the > production environment as possible. > > In retrospect, I'm surprised I ever used runserver... > > On Wednesday, August 24, 2016 at 12:25:52 AM UTC-7, Lekan Wahab wrote: >> >> Good morning, >> I was recently given a django project to manage at work. >> However, i noticed the project has neither a django-admin.py or a >> manage.py file. >> Is that normal? >> If it is, how do i run the project on my local machine for testing >> purposes? >> >> The file structure is something like this: >> Project Name >> app1 >> app2 >> app3 >> app4 >> app5 >> models.py >> forms.py >> __init__.py >> urls.py >> views.py >> admin.py >> >> >> Each app contains the following: >> models.py >> forms.py >> __init__.py >> urls.py >> views.py >> admin.py >> > -- > You received this message because you are subscribed to the Google Groups > "Django users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at https://groups.google.com/group/django-users. > To view this discussion on the web visit https://groups.google.com/d/ > msgid/django-users/f72d16e6-eb11-4a48-a89e-b51a6006d24e%40googlegroups.com > <https://groups.google.com/d/msgid/django-users/f72d16e6-eb11-4a48-a89e-b51a6006d24e%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > What you get with runserver is automatic reloading - you don't get that running the application behind a webserver. If you run a django app behind anything else except runserver, you will need to restart the server every time you change your code. You will still need to try the application in a production environment, but that is why you have a staging environment (or test). You also need to have a place where QA can test everything (or the product owner) - this environment should be as close to the production environment as possible - so that discrepancies can be found there. Regards, Andréas -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CALXYUb%3DsXv2xtVW2Bet6jwLQRaQgV1DB9EbiUAHdF43tKPKRZA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
