Revision history [back]
Hi Benoit, I would install the beta version into the same directory that contains your settings.py file for the "beta" site and have the code cloned from github. That way you can merge the latest updates into the code and try them out.
With multiple deployments you need to consider how to set up the server configuration, database and the python code.
With the python part you can deploy copies of actual code into the site directories. Having more than one copy in the site-packages won't work because of the conflicts of the package names. You can also deploy with python virtualenv - with one virtual environment for each deployment.
For the database - if you want to point both production and "beta" instances to the same database, then you can do it only in the cases when the two instances have the same database schema. The schema changes from time to time, with the south migrations taking care of the transitions. The easiest way to tell whether the shema has changed is by typing python manage.py migrate --list; this command will list the migrations that have/have not been applied. Don't forget to add the --list parameter, or you will run the actual migration by accident (and remember to back up the database before applying the migrations). If the lists of migrations are the same in the two instances, it is safe to point both to the same database.
If the database schemas differ, then you'll have to have a separate database for the "beta" instance.
The server configuration depends obviously on the type of server you are using. With apache you can try using two WSGIScriptAlias statements within the same virtual host (if you want to use the same domain name), or you can set up two virtual hosts - forum.example.com and forum-beta.example.com. Can't advise you anyting regarding the webrick.
Askbot.org site runs the latest code from the master branch most of the time. I find it very simple to upgrade (fetch new code then merge) from github even though askbot.org is using a fork or the app (there are some modifications in the application files that make this site multilingual).
Hi Benoit, I would install the beta version into the same directory that contains your settings.py file for the "beta" site and have the code cloned from github. That way you can merge the latest updates into the code and try them out.
With multiple deployments you need to consider how to set up the server configuration, database and the python code.
With the python part you can deploy copies of actual code into the site directories. Having more than one copy in the site-packages won't work because of the conflicts of the package names. You can also deploy with python virtualenv - with one virtual environment for each deployment.
For the database - if you want to point both production and "beta" instances to the same database, then you can do it only in the cases when the two instances have the same database schema. The schema changes from time to time, with the south migrations taking care of the transitions. The easiest way to tell whether the shema has changed is by typing python manage.py migrate --list; this command will list the migrations that have/have not been applied. Don't forget to add the --list parameter, or you will run the actual migration by accident (and remember to back up the database before applying the migrations). If the lists of migrations are the same in the two instances, it is safe to point both to the same database.
If the database schemas differ, then you'll have to have a separate database for the "beta" instance.
The server configuration configuration depends obviously on the type of server you are using. With apache you can try using two WSGIScriptAlias statements within the same virtual host (if you want to use the same domain name), or you can set up two virtual hosts - forum.example.com and forum-beta.example.com. Can't advise you anyting regarding the webrick.
Askbot.org site runs the latest code from the master branch most of the time. I find it very simple to upgrade (fetch new code then merge) from github even though askbot.org is using a fork or the app (there are some modifications in the application files that make this site multilingual).
Hi Benoit, I would install the beta version into the same directory that contains your settings.py file for the "beta" site and have the code cloned from github. That way you can merge the latest updates into the code and try them out.
With multiple deployments you need to consider how to set up the server configuration, database and the python code.
With the python part you can deploy copies of actual code into the site directories. Having directories, having more than one copy in the site-packages won't work because of the conflicts of the package names. You can also deploy with python virtualenv - with one virtual environment for each deployment.
For the database - if you want to point both production and "beta" instances to the same database, then you can do it only in the cases when the two instances have the same database schema. The schema changes from time to time, with the south migrations taking care of the transitions. The easiest way to tell whether the shema has changed is by typing python manage.py migrate --list; this command will list the migrations that have/have not been applied. Don't forget to add the --list parameter, or you will run the actual migration by accident (and remember to back up the database before applying the migrations). If the lists of migrations are the same in the two instances, it is safe to point both to the same database.
If the database schemas differ, then you'll have to have a separate database for the "beta" instance.
The server configuration configuration depends obviously on the type of server you are using. With apache you can try using two WSGIScriptAlias statements within the same virtual host (if you want to use the same domain name), or you can set up two virtual hosts - forum.example.com and forum-beta.example.com. Can't advise you anyting regarding the webrick.
Askbot.org site runs the latest code from the master branch most of the time. I find it very simple to upgrade (fetch new code then merge) from github even though askbot.org is using a fork or the app (there are some modifications in the application files that make this site multilingual).
Hi Benoit, I would install the beta version into the same directory that contains your settings.py file for the "beta" site and have the code cloned from github. That way you can merge the latest updates into the code and try them out.
With multiple deployments you need to consider how to set up the server configuration, database and the python code.
With the python part you can deploy copies of actual code into the site directories, having more than one copy in the site-packages won't work because of the conflicts of the package names. You can also deploy with python virtualenv - with one virtual environment for each deployment.
For the database - if you want to point both production and "beta" instances to the same database, then you can do it only in the cases when the two instances have the same database schema. The schema changes from time to time, with the south migrations taking care of the transitions. The easiest way to tell whether the shema has changed is by typing python manage.py migrate --list; this command will list the migrations that have/have not been applied. Don't forget to add the --list parameter, or you will run the actual migration by accident (and remember to back up the database before applying the migrations). If the lists of migrations are the same in the two instances, it is safe to point both to the same database.
If the database schemas differ, then you'll have to have a separate database for the "beta" instance.
The server configuration configuration depends obviously on the type of server you are using. With apache you can try using two WSGIScriptAlias statements within the same virtual host (if you want to use the same domain name), or you can set up two virtual hosts - forum.example.com and forum-beta.example.com. Can't advise you anyting regarding the webrick.
Askbot.org site runs the latest code from the master branch most of the time. I find it very simple to upgrade (fetch new code then merge) from github even though askbot.org is using a fork or the app (there are some modifications in the application files that make this site multilingual).
Hi Benoit, I would install the beta version into the same directory that contains your settings.py file for the "beta" site and have the code cloned from github. That way you can merge the latest updates into the code and try them out.
With multiple deployments you need to consider how to set up the server configuration, database and the python code.
With the python part you can deploy copies of actual code into the site directories, having more than one copy in the site-packages won't work because of the conflicts of the package names. You can also deploy with python virtualenv - with one virtual environment for each deployment.
For the database - if you want to point both production and "beta" instances to the same database, then you can do it only in the cases when the two instances have the same database schema. The schema changes from time to time, with the south migrations taking care of the transitions. The easiest way to tell whether the shema has changed is by typing python manage.py migrate --list; this command will list the migrations that have/have not been applied. Don't forget to add the --list parameter, or you will run the actual migration by accident (and remember to back up the database before applying the migrations). If the lists of migrations are the same in the two instances, it is safe to point both to the same database.
If the database schemas differ, then you'll have to have a separate database for the "beta" instance.
The server configuration configuration depends obviously on the type of server you are using. With apache you can try using two WSGIScriptAlias statements within the same virtual host (if you want to use the same domain name), or you can set up two virtual hosts - forum.example.com and forum-beta.example.com. Can't advise you anyting regarding the webrick.