Plan server migration to refactored codebase
Need to plan this in advance. For now, some random points:
We have some related scripts here: https://git.lumc.nl/mutalyzer/server-migration-2014
Completed
- Find a new home for CLI-mate.
- Discuss any potential breakages with LOVD.
- Perhaps create a mailing list mutalyzer-announce (and mutalyzer-user).
- Use Ansible for server provisioning and deployment (see mutalyzer-deployment).
- Find a way to clone from GitLab over SSH on the server (port 22 is closed). Alternatively, open the repository and use HTTPS. (The latter was done.)
- Read through commit messages and pull requests linked to pull request !6 (merged).
- Configure automatic database backups.
- First test.mutalyzer.nl.
- Have an announcement on mutalyzer.nl some time before.
- Have a description of any user-visible changes on the wiki.
In progress
- Migrate mapping database (depends on #7 (closed)).
- Migrate cache directory and GBInfo database.
- Migrate stats database.
- Upgrade server to Debian 7.
Known backwards incompatible changes to be documented
- HTTPS only with redirects from HTTP.
- HTTP backdoors are removed.
- Many website entrypoints have changed URLs and form parameter names, but have redirects.
- JSON webservices have changed response formats.
- Remove old
/2.0/*
redirects. - Remove old
/projects/*
Trac redirects. - Obsolete
/getGS
and/Variant_info
? - ... (read through merge request !6 (merged) commit messages)
- In maintenance mode, all requests get a 503 Service Temporarily Unavailable response.