|
|
|
`cd` into the shared app directory, then:
|
|
|
|
|
|
|
|
1. `awesim maintenance on` if the update will occur while users are using the app (do this only if a public/503.html exists, as requests to the app will be redirected to this page)
|
|
|
|
2. `git pull` and checkout the appropriate code
|
|
|
|
3. `awesim update` to rebuild assets and restart the app for everyone
|
|
|
|
4. `awesim lint` to verify everything is still setup correctly
|
|
|
|
5. `awesim maintenance off` takes the app out of maintenance mode
|
|
|
|
|
|
|
|
If `awesim lint` returns errors that are not easy to fix, you may have to run `awesim setup` again.
|
|
|
|
|
|
|
|
At this time, the next time users access the app Passenger will reload their running instance.
|
|
|
|
|
|
|
|
If you don't have any active users, you can omit steps 1 & 5. If it is a minor modification, you can probably just get away with a `git pull` followed by a `awesim update`.
|
|
|
|
|
|
|
|
|
|
|
|
A few things about updates:
|
|
|
|
|
|
|
|
* database migration changes between versions of an app are not supported; if a user accesses an app with a database that has not run all the migrations of the apps shared code, they will see a warning! |
|
|
|
\ No newline at end of file |
