I am just finishing a Django project that is managed by Subversion. I
have set up 3 web sites to manage it - a "development", "staging" and
"production" server. This is a common paradigm, nothing that I came up
with myself.
You can have active committing by developers to the repository and t
That's exactly what we're doing. Our "update production" script reads:
svn update /u/django/project
sudo /etc/init.d/apache2 restart
The only time this doesn't work is if someone has tweaked a model and
there's schema changes to be made in conjunction.
-joe
On 1/10/07, Cam <[EMAIL PROTECTED]> w
To deploy into production you should run all tests, tag a release and
have the webserver check out your tag.
cheers,
Cam.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group
On 10-Jan-07, at 8:58 PM, Aidas Bendoraitis wrote:
> 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 pub
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
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 website
6 matches
Mail list logo
