Re: How do you organize your deployment enviroment

I'm just wondering how you could handle database changes.

Let's say you have a existing working project and the client asks for some changes.

These changes force you to create an extra table and modify some tables (models).
On the development server I could modify the changes to the database and the models files myself.
But deploying these changes to the production server seems a bit harder to overcome without the fear of loosing your data.

I don't think the newly created models and database tables would form a problem. Simply running ./manage.py syncdb would create the table(s) for us without any problems.
But what about tables (models) that are modified ?

How would you best handle such cases of deployment ?

Op 23-mei-2011, om 09:00 heeft DK het volgende geschreven:

> Hi,
>
> I am having a django project that is being frequently deployed on clean linux installation. After a few deployments I have noticed that this process is very time consuming for me (every time I am preparing run scripts for everything, configuring cronjobs, paths to log files, etc) but this could be easily automated.
>
> What are a ready solutions to manage such deployments?
>
> My typical workflow is:
> 1) install packages on debian/ubuntu via aptitude (like database, etc)
> 2) creating new virtualenv + getting pip
> 3) pip install -r requirements (to setup enviroment)
> 4) fetch django project from code repository
> 5) setup runtime dir (I keep there: run - for pid files, logs, conf - for some config variables or scritps, scripts - some starting srcipts)
> 6) setup crontab jobs
> 7) setup webserver + django wsgi to be started
>
>
> Sure - I can write some custom made installer for that, but wondering if there is some generic tool for such things.
>
> PS. I have heard about fabric, but didn't investigate this tool yet.
>
>
>
>
> --
> 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@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/django-users?hl=en.

Jonas Geiregat
jonas@geiregat.org

--
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@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-users?hl=en.