Upgrade Guide
Based on your chosen method, the upgrade procedure diffs:
- If you are running OneDev as docker container, the upgrade happens automatically every time you start the container
- If you are deploying OneDev into Kubernetes:
- Edit file /path/to/k8s-resources/production/kustomization.yaml to change property newTag to a new OneDev version (for instance 3.0.4)
- Run command
kubectl apply -k .from the production directory
- If you are running OneDev on bare metal machine:
- Assume OneDev is installed at /opt/onedev, stop OneDev by running command /opt/onedev/bin/server.(sh|bat) stop
- Make sure database server is up and running if you are using external database
- Extract new OneDev version to a separate folder, say _/path/to/new-onedev
- Open a command window and change to directory /path/to/new-onedev/bin
- Run command ./upgrade.(sh|bat) /opt/onedev to perform the upgrade
- /opt/onedev will be upgraded and you may launch it to check if things are in order
- You may remove /path/to/new-onedev afterwards if everything is fine