Changeset 5ca18786bead451a5cb57d6937aa8fdfe0291017 for README
- Timestamp:
- 11/15/09 08:59:00 (3 years ago)
- Parents:
- 3ccc2c04c3f36a81995af945ae032ce88de76afe
- Children:
- 19f22bdad6f95208a3c37fbaf34958778dd38d36
- git-committer:
- Luis Rodrigues <lfrodrigues@gmail.com> / 2009-11-15T16:59:00Z+0000
- Files:
-
- 1 modified
Legend:
- Unmodified
- Added
- Removed
-
README
r6de20ab r5ca1878 9 9 :Author: The Rancho Team 10 10 :Contact: info@getrancho.com 11 :Date: 2009- 06-2511 :Date: 2009-11-15 12 12 :Web site: http://www.getrancho.com 13 13 :License: Rancho is published under the GNU AGPL v3 license. … … 109 109 110 110 $ python manage.py syncdb 111 $ python manage.py migrate 111 112 112 113 Answer yes to the question to create a superuser and then supply the rest of the information asked. … … 128 129 **Important**: It is advisable to back up all your data before upgrading Rancho. 129 130 130 The first thing to do after having upgraded Rancho is to synchronize the database131 The first thing to do after having upgraded Rancho is to migrate the database 131 132 using the following command:: 132 133 133 $ python manage.py syncdb 134 135 If there are changes to the database, a message will be returned warning that an 136 evolution is needed. 137 138 To perform the evolution, run the command:: 139 140 $ python manage.py evolve --execute 134 $ python manage.py migrate 141 135 142 136 If all went well, Rancho will be ready to be run.
