What if someone commits something that brakes the live website? My recommendation is to checkout into the live folders the version/tag/branch you want. Or checkout somewhere, test the app, and then copy the files. Just don't run the website from a codebase where developers are commiting.
On 1/10/07, Aidas Bendoraitis <[EMAIL PROTECTED]> wrote: > > I have an SVN-specific question which doesn't really fit into Django > groups. Anyway, maybe somebody of you will have enough experience and > competence to answer it. > > We are going to set our Django projects under > version control on a dedicated server. We will also publicly run > several Django websites on the same server. So what is a better > practice -- to use the code under source > control for the public websites directly, or to have copies (tags) of > the subversioned code for the public websites? > > How is this managed with djangoproject.com and djangobook.com? > > Regards, > Aidas Bendoraitis aka Archatas > > > > -- Julio Nobrega - http://www.inerciasensorial.com.br --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---