Operations grimoire/Login: Difference between revisions
From Nasqueron Agora
(Doc for deploy or upgrade) |
({{Configuration as Code}} done) |
||
(One intermediate revision by the same user not shown) | |||
Line 13: | Line 13: | ||
=== Start a new container === | === Start a new container === | ||
<code> | <code>salt equatower state.apply roles/paas-docker/containers/auth-grove</code> | ||
=== Upgrade a live container === | === Upgrade a live container === | ||
Line 53: | Line 53: | ||
=== URL issue === | === URL issue === | ||
If URL are in http://localhost, ensure the web server passes proxy forwarding information (include proxy_params in nginx), as the application guess links. | If URL are in http://localhost, ensure the web server passes proxy forwarding information (include proxy_params in nginx), as the application guess links. | ||
Latest revision as of 10:37, 22 September 2018
Login is handled by Auth Grove
Application information
- Repository: rGROVE
- Maintainer: Dereckson
- Written in PHP, use Laravel, Laravel Socialite and Keruald libraries
Run it
Deployment information
Start a new container
salt equatower state.apply roles/paas-docker/containers/auth-grove
Upgrade a live container
- Enter notifications container as app user :
docker exec -it --user=app login bash
- Check we're on the master branch and the history is clean
- Update code rebasing the production branch against origin/master
- If composer has been touched,
composer update
(could be faster to docker pull, stop this container and start a new container) - To upgrade database schema,
php artisan migrate
- If entered as root, fix ownership with
chown -R app:app /var/wwwroot/default
- Restart PHP FPM with
sv restart php-fpm
- Run
php optimize
to refresh compiled class - Restart again PHP FPM with
sv restart php-fpm
For longer upgrade, you can put the application in maintenance mode with php artisan down
.
If preferences are updated (in the code or by us), update the cache: php artisan config:cache && sv restart php-fpm
is needed.
How to rebase against master?
- update master to match origin/master
- rebase production against master
$ git fetch
$ git checkout master
$ git rebase origin/master
$ git checkout production
$ git rebase master
If there is a merge conflict:
- Edit the conflict files
git add <edited files>
git rebase --continue
Troubleshooting
URL issue
If URL are in http://localhost, ensure the web server passes proxy forwarding information (include proxy_params in nginx), as the application guess links.