Skip to main content

Upgrade Guide

Running as Docker Container

If you are running OneDev as docker container:

  1. Stop container if it is still running:
    $ docker stop onedev
  2. Delete container:
    $ docker rm onedev
  3. Pull latest image:
    $ docker pull 1dev/server
  4. Run container again. Wait a while for OneDev to upgrade and start.

Running on Virtual Machine/Bare Metal

If you are running OneDev on virtual machine/bare metal:

  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. Run below command to perform the upgrade:
    $ /path/to/new-onedev/bin/upgrade.(sh|bat) /opt/onedev
  5. /opt/onedev will be upgraded and you may launch it to check if things are in order
  6. You may remove /path/to/new-onedev afterwards if everything is fine

Deploying to Kubernetes

If you are deploying OneDev into Kubernetes, just run below commands:

$ helm upgrade onedev onedev --repo https://dl.cloudsmith.io/public/onedev/onedev/helm/charts --namespace onedev --reuse-values