Hi, I started my project with a similar workflow but I soon ran into troubles so I adopted the following one:
- svn repository has a production branch and a trunk - my dev is done on trunk, on various machines (desktop, laptop, test server) - whenever I want to push something to the production server, i just merge my changes (sometimes selectively) to the production branch - the production server pulls the changes, runs some data migration scripts and restarts apache every night at a fixed time (cron) What I painfully learned in the early days of my project is that anything you have to do repetitively on a daily/weekly basis you will end up messing up once. In your case that would mean overwriting your data.db. I'm pretty sure that would be a bad thing :) The separate branches for dev and production are a nicety but not a must-have. If your project is small enough you can do without. On the other hand what I strongly urge you to do is stop manipulating your production data manually and have some scripts to do that for you every day/week. I would also suggest that you use another DB for production, like mysql or postgres. Also, you should really avoid pushing your data into the svn. my 2 cents, Philippe On Mar 20, 11:15 am, Fabio Natali <nat...@poisson.phc.unipi.it> wrote: > Dear all! > > My Django project comes in 3 copies: > > - svn repository > - local development on my pc > - real web site > > I use an sqlite file to store my data. I keep it in my project folder > itself. > > My workflow: > > - work locally > - update the svn repo > - log onto the web server and run an update from the svn repo > > However, on updating the website, I must be very *careful* and run a > selective update/merge: I must not overwrite the data.db file which is > on the web server and actually the most important piece of the story. > > Also, I need to perform backups of my sqlite data file. So I log onto > the webserver and commit data.db to the svn repo. > > Does this structure/workflow make any sense? Should I rather keep > data.db out of my svn repo and use a different tool to perform the > backup (e.g.: cron + rsync)? > > Any tips/feedback appreciated! > > If you think this is too much of an Svn issue rather than a Django > one, I apologize and won't push it any further. > > Thank you very much, > Fabio. > > -- > Fabio Natali --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
