On Tue, Sep 23, 2008 at 1:22 PM, sotirac <[EMAIL PROTECTED]> wrote: > > Just trying to get a feel for what other developers are doing when > deploying to a production server. There are some differences between > my development machine and production server such as the location of > my media files, the database settings, and if I want to enable caching > or not. Right now my option is to comment out some of the code and > uncomment the other values. This is time consuming and error proned. > How do you deal with this issue of working in your development machine > and then having to deploy the same code into your production server. > > Some files I modify are the settings.py/url.py/views.py.
Remember that all of these are just Python files, there's nothing special. So I usually have files called dbsettings.py and mediasettings.py, that hold all my database and media info, then I just have settings.py import them. The stuff common between environments lives in settings.py, and the custom stuff only has to live in one place. Jay P. --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
