Order of Operations: When Updating Fluxer Server, Pull BEFORE Docker Down

(#4152) Bug Open: Needs triage self-hosting

Reproduction steps

Run bash ./install.sh --update

Expected behaviour

  1. Run bash ./install.sh --update
  2. Git pull
  3. Docker compose takes the services down
... X. Done

Actual behaviour

  1. bash ./install.sh --update
  2. Docker compose takes the services down
  3. Git pull
  4. Patch
.... X. Done

Platform

Self-hosting

Evidence

As Fluxer gets larger, being able to make sure the git pull succeeds first should take precedence over making sure the server shuts down properly. At this point in time, the longer it takes for the server to pull the latest build, the longer it takes for the server to come back online instead of only waiting for the down -> compilation/patch -> up.

Comments

Sign in with Fluxer to comment and vote.

No comments yet.