4.2
ROOT /
pages /
upgrade-guide.md
17 lines | ISO-8859-1 | 1 KB

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:
    1. Edit file /path/to/k8s-resources/production/kustomization.yaml to change property newTag to a new OneDev version (for instance 3.0.4)
    2. Run command kubectl apply -k . from the production directory
  • If you are running OneDev on bare metal machine:
    1. Assume OneDev is installed at /opt/onedev, stop OneDev by running command /opt/onedev/bin/server.(sh|bat) stop
    2. Make sure database server is up and running if you are using external database
    3. Extract new OneDev version to a separate folder, say _/path/to/new-onedev
    4. Open a command window and change to directory /path/to/new-onedev/bin
    5. Run command ./upgrade.(sh|bat) /opt/onedev to perform the upgrade
    6. /opt/onedev will be upgraded and you may launch it to check if things are in order
    7. You may remove /path/to/new-onedev afterwards if everything is fine
Please wait...
Page is in error, reload to recover