Skip to content

Latest commit

 

History

History
65 lines (40 loc) · 1.82 KB

UPDATING.md

File metadata and controls

65 lines (40 loc) · 1.82 KB

Updating

Note: To update make sure to update your copy of this repo (refer to repository update) and from there you can update Chevereto application (refer to Chevereto update).

Chevereto update

To update instances to a new Chevereto version re-build the container image (see BUILDING) to reflect the target version.

One-click Chevereto updating

Run the following command to update all instances. The process will swap every instance to the new container image and perform the necessary database updates.

make update

Manual Chevereto updating

Swap to the new container image by down plus up-d by passing the NAMESPACE of your project. Once done, execute the app/bin/legacy -C update command to perform the necessary database updates.

make down NAMESPACE=yourproject
make up-d NAMESPACE=yourproject
make exec NAMESPACE=yourproject COMMAND="app/bin/legacy -C update"

Repository update

To update your containers to the latest version of this repository make sure to run for every instance:

make down NAMESPACE=yourproject

💡 If you forget to run this you can rollback the repo and execute the above command.

Manual repo updating

Pull changes in your copy of this repo.

git fetch --tags -f && git pull --rebase --autostash

Switch to the new branch/tag.

git switch 4.1

GitHub one-click repo updating

  1. Go to Actions
  2. Select Update under Workflows
  3. Click on Run Workflow and confirm

Update template

🤖 When done a bot will create a pull request in your repo so you can review and confirm the changes.

Update merge

Troubleshooting

Refer to persistance troubleshoot If the system prompts to re-install.