Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Update script that WorksForMe*
Might be a starting point for someone to develop a more useful general update solution (#720).
The constants have to be adjusted to your local (bare metal) environment.
I don't have enough experience with docker to approach that.
The (guided) update process goes through ~4 stages:
0: check for new release
1: put current site into maintenance mode (requires an extra vhost to be set up...meh)
2: backup partdb database (only mysql at the moment...meh); git pull
3: Build according to the docs, transfer required files to testing location (yet another vhost...)
4: Transfer testing site to live enviroment, end maintenance mode
The process can be interrupted at any stage, by errors or by user interaction.
Resumption through current stage stored in a file with the name of $FILE. While I'm writing this, I think it's easier to use an env var.
Also, media files are at least copied twice, so performance gain is possible.