This git repository helps you get up and running quickly w/ a Django
installation on OpenShift. The Django project name used in this repo
is 'openshift' but you can feel free to change it. Right now the
backend is sqlite3 and the database runtime is found in
$OPENSHIFT_DATA_DIR/sqlite3.db.
Before you push this app for the first time, you will need to change
the Django admin password.
Then, when you first push this
application to the cloud instance, the sqlite database is copied from
wsgi/openshift/sqlite3.db with your newly changed login
credentials. Other than the password change, this is the stock
database that is created when python manage.py syncdb is run with
only the admin app installed.
On subsequent pushes, a python manage.py syncdb is executed to make
sure that any models you added are created in the DB. If you do
anything that requires an alter table, you could add the alter
statements in GIT_ROOT/.openshift/action_hooks/alter.sql and then use
GIT_ROOT/.openshift/action_hooks/deploy to execute that script (make
sure to back up your database w/ rhc app snapshot save first :) )
Create an account at http://openshift.redhat.com/
Install the RHC client tools if you have not already done so:
sudo gem install rhc
Create a python-2.6 application
rhc app create -a django -t python-2.6
Add this upstream repo
cd django
git remote add upstream -m master git://github.com/nistur/DjangoShift.git
git pull -s recursive -X theirs upstream master
Then push the repo upstream
git push
Here, the admin user name and password will be displayed, so pay special attention.
That's it. You can now checkout your application at:
http://django-$yournamespace.rhcloud.com
As the git push output scrolls by, keep an eye out for a
line of output that starts with CLIENT_MESSAGE: . This line
contains the generated admin password that you will need to begin
administering your Django app. This is the only time the password
will be displayed, so be sure to save it somewhere. You might want
to pipe the output of the git push to a text file so you can grep for
the password later.
In theory this will work on a Python-2.7 gear, however the static files
aren't being hosted correctly at this point. Also for some reason,
calling python in the Python-3.3 gear will run a python 2.6 executable
So .openshift/action_hooks/deploy will pick up the wrong version of
python. I'm not sure if there's a nice way to get the correct version of
the gear, so for now, if you need 3.3, manually change deploy (you also
need to modify the path to
$OPENSHIFT_HOMEDIR/$cartridge_type/virtenv/venv/bin/activate and change bits
of settings.py)