Changes between Version 15 and Version 16 of how-to/roundcube-upgrade

Timestamp:

Oct 19, 2022, 6:25:51 PM (3 years ago)

Author:

Jamie McClelland

Comment:

--

how-to/roundcube-upgrade

@@ -6 +6 @@
 We have both a dev/testing site (`/srv/roundcube-dev`, accessible via https://roundcube.dev.mayfirst.org) and the live site (`/srv/roundcube`, accessible via https://roundcube.mayfirst.org).
 
-Both installations are maintained via git. In addition, there is a roundcube-code user that owns the code. Be sure to add your OpenPGP user id to `/home/roundcube-code/.monkeysphere/authorized_user_ids` and run (as root): `monkeysphere-authentication update-users roundcube-code` then login as the `roundcube-code@stallman.mayfirst.org` when making all changes.
+Both installations are maintained via git. In addition, there is a roundcube-code user that owns the code. 
 
 == Basic Setup (only needed once) ==
@@ -18 +18 @@
 git remote update
 }}}
- * Now, checkout (and create a branch) for the mfpl branch of the gmo remote.
-   {{{
-0 jamie@animal:roundcube$ git checkout -b mfpl-0.9 gmo/mfpl-0.9
+
+== Create a target branch for the upgrade
+
+The idea is to create a new branch for us - that is based on the target version of roundcube to which we are upgrading.
+
+In other words, if we want to upgrade to roundcube 1.4.13:
+
+{{{
+0 jamie@animal:roundcube$ git checkout -b mfpl-1.4.13 1.4.13
 Branch mfpl set up to track remote branch mfpl from gmo.
-Switched to a new branch 'mfpl-0.9'
+Switched to a new branch 'mfpl-1.4.13'
 0 jamie@animal:roundcube$
 }}}
@@ -29 +35 @@
 == Doing an upgrade ==
 
-We're leaning toward rebasing as a matter of common practice, and leaving a trail of signed tags:
+Note: Firt do everything in the dev directory as the roundcube-dev user. After testing, repeat for the live site.
 
- * start by rebasing, inspecting, verifying, signing a tag, and then pushing to `git.mayfirst.org`:
-   {{{
-git rebase 0.9.5
-# examine the changelog and the git history; make sure things look sane.
-git tag -s -m 'Tagging roundcube with MF/PL changes version 0.9.5' roundcube-0.9.5-mfpl1
-git push gmo --tags
-git push -f gmo
-}}}
- * Now, as `roundcube-code@stallman.mayfirst.org`, verify the tag and check it out if it looks reasonable:
-   {{{
-cd /srv/roundcube-dev
-git remote update
-git tag -v roundcube-0.9.5-mfpl1
-git checkout roundcube-0.9.5-mfpl1
-}}}
- * Test via: https://roundcube.dev.mayfirst.org/
- * If all works fine, pull into the live server via `roundcube-code@stallman.mayfirst.org`:
-   {{{
-cd /srv/roundcube
-git remote update
-git tag -v roundcube-0.9.5-mfpl1
-git checkout roundcube-0.9.5-mfpl1
-}}}
- * and test it one last time at https://roundcube.mayfirst.org/
+USER=roundube-dev
+DIR=/srv/roundcube-dev
+DATABASE=roundcube-dev
+
+# run the gc script, so there's no need to backup old session records
+su - $USER
+cd $DIR
+php ./bin/gc.sh
+
+# backup database 
+cd /home/$USER
+pg_dump -v -b -C DATABASE | gzip -9 > roundcube.$(date +%F).sql.gz
+
+# fetch source (as user `roundcube-code')
+su - roundcube-code
+cd $DIR
+git fetch gmo
+git checkout TAG
+# composer updates
+composer update --no-dev
+# if you get a giant error...
+# rm vendor/composer/installed.json
+# See https://craftcms.stackexchange.com/questions/36551/unknown-package-has-no-name-defined-composer-error-on-upgrade
+composer install --no-dev
+# javascript dependencies
+php bin/install-jsdeps.sh
+lessc -x styles/styles.less > styles/styles.css
+lessc -x styles/print.less > styles/print.css
+lessc -x styles/embed.less > styles/embed.css
+su - $USER
+# database stuff (as user roundcube)
+php ./bin/update.sh
+php ./bin/indexcontacts.sh
+