Revision history  [back]

possible explanation What seems to me your system python paths might be inconsistent. Be careful with that. It is better to use virtual environment for the app, so it's completely isolated from the rest.

Look up "configuring mod_wsgi" with python virtual environment.

If you type some commands as root and then restart the webserver you can accidentally add your own environment variables to the root's and subsequently - the webserver.

how to upgrade:

• set up a second fully functioning environment in a separate blank database (no tables), with new software (but do not run syncdb or migrate yet).
• take your existing site down (possibly show some maintenance page)
• dump your current database
• load the database dump into the new (completely blank) database
• migrate the new database with command python manage.py migrate

It might be tempting to just write over the old files with the new, but this might lead to harder problems to solve - trying to remember what edits you made in the files or fix the broken database.

With the "live" and "staging" deployments you can quickly revert if something goes wrong.

possible explanation What seems to me your system python paths might be inconsistent. Be careful with that. It is better to use virtual environment for the app, so it's completely isolated from the rest.

Look up "configuring mod_wsgi" with python virtual environment.

If you type some commands as root and then restart the webserver you can accidentally add your own environment variables to the root's and subsequently - the webserver.

how to upgrade:

• set up a second fully functioning environment in a separate blank database (no tables), with new software (but do not run syncdb or migrate yet).yet.
• take your existing site down (possibly show some maintenance page)
• dump your current database
• load the database dump into the new database
• migrate the new database with command python manage.py migrate

It might be tempting to just write over the old files with the new, but this might lead to harder problems to solve - trying to remember what edits you made in the files or fix the broken database.

With the "live" and "staging" deployments you can quickly revert if something goes wrong.

possible explanation What seems to me your system python paths might be inconsistent. Be careful with that. It is better to use virtual environment for the app, so it's completely isolated from the rest.

Look up "configuring mod_wsgi" with python virtual environment.

If you type some commands as root and then restart the webserver you can accidentally add your own environment variables to the root's and subsequently - the webserver.

how to upgrade:

• set up a second fully functioning environment in a separate blank database (no tables), with new software (but do not run syncdb or migrate yet.softwaree
• take your existing site down (possibly show some maintenance page)
• dump your current database
• load the database dump into the new database
• migrate the new database with command python manage.py migrate

It might be tempting to just write over the old files with the new, but this might lead to harder problems to solve - trying to remember what edits you made in the files or fix the broken database.

With the "live" and "staging" deployments you can quickly revert if something goes wrong.

possible explanation What seems to me your system python paths might be inconsistent. Be careful with that. It is better to use virtual environment for the app, so it's completely isolated from the rest.

Look up "configuring mod_wsgi" with python virtual environment.

If you type some commands as root and then restart the webserver you can accidentally add your own environment variables to the root's and subsequently - the webserver.

how to upgrade:

• take your existing site down (possibly show some maintenance page)
• dump your current database
• set up a second fully functioning environment in a separate blank database (no tables), database, with new softwaree
• take your existing site down (possibly show some maintenance page)
• dump your current databasesoftware
• load the database dump into the new database
• migrate the new database with command python manage.py migrate

It might be tempting to just write over the old files with the new, but this might lead to harder problems to solve - trying to remember what edits you made in the files or fix the broken database.

With the "live" and "staging" deployments you can quickly revert if something goes wrong.

possible explanation What seems to me your system python paths might be inconsistent. Be careful with that. It is better to use virtual environment for the app, so it's completely isolated from the rest.

Look up "configuring mod_wsgi" with python virtual environment.

If you type some commands as root and then restart the webserver you can accidentally add your own environment variables to the root's and subsequently - the webserver.