OneDev

Prerequisites

Before you deploy, make sure you have:

• An active Azure subscription
• An SSH key pair
• A VNet and subnet in the target region
• A Standard_B2ms VM size (2 vCPU / 8 GiB RAM), which is a good starting point. Scale up for more concurrent builds and larger repositories.
• NSG inbound rules that allow 22/tcp from your management network, 80/tcp for the web UI, and 6611/tcp if you want to clone over SSH

For public exposure, front the web UI with TLS (see Enabling HTTPS).

Step 1 - Deploy from the Azure Marketplace

1. Sign in to the Azure Portal, choose Create a resource, and search the Marketplace for OneDev by SecureAnyCloud.
2. Select Create.
3. On Basics, pick your subscription, resource group, region and size.
4. Under Administrator account, choose SSH public key and paste your key.
5. Under Inbound port rules, allow SSH (22) and HTTP (80).
6. On the Disks tab, review the dedicated data disk.
7. Select Review + create, then Create.

Step 2 - Deploy from the Azure CLI

Accept the Marketplace terms, create the VM, then open port 80.

# Accept the Marketplace terms once per subscription (required before the first CLI deploy)
az vm image terms accept --urn sac1647283583153:onedev-ubuntu-24-04:default:latest
az vm create \
  --resource-group <your-rg> \
  --name onedev \
  --image sac1647283583153:onedev-ubuntu-24-04:default:latest \
  --size Standard_B2ms \
  --admin-username azureuser \
  --ssh-key-values ~/.ssh/id_ed25519.pub \
  --vnet-name <your-vnet> --subnet <your-subnet> \
  --public-ip-sku Standard
az vm open-port --resource-group <your-rg> --name onedev --port 80 --priority 1010

Step 3 - Connect to your VM

Connect over SSH.

ssh azureuser@<vm-public-ip>

Step 4 - Confirm the services are running

Check that OneDev and nginx are active.

systemctl is-active onedev.service nginx.service

Both services report active. OneDev runs its database migrations on the very first boot, so allow a minute or two after deployment before the web UI answers.

Step 5 - Retrieve your admin password

The administrator account is created uniquely on the first boot of your VM. Its password is written to a root-only file. Read the file.

sudo cat /root/onedev-credentials.txt

This file contains ONEDEV_ADMIN_USER (admin) and ONEDEV_ADMIN_PASSWORD, plus the URL for the web UI. Store the password somewhere safe.

Step 6 - Check the health endpoint

nginx serves an unauthenticated health endpoint for load balancers and probes. Call it.

curl -s http://localhost/health

It returns ok.

Step 7 - Sign in to the web UI

Browse to http://<vm-public-ip>/ and sign in as admin with the password from Step 5.

There is no setup wizard. The administrator account and system settings were seeded on first boot. The login page is the entry point to repositories, CI/CD, issue boards and the package registry.

After you sign in, you land on the projects dashboard, where you create your first repository and browse existing ones.

OneDev's built-in CI/CD gives you a Builds view across all your projects, with saved queries for successful, failed, running and pending builds.

The Issues view tracks work items with rich saved queries (open, in progress, in review, assigned to me), alongside the code and CI/CD that act on them.

Step 8 - Use the REST API

OneDev exposes a REST API under /~api that accepts HTTP Basic authentication. Confirm that the admin account authenticates and returns its own profile.

curl -s -u admin:<ONEDEV_ADMIN_PASSWORD> http://localhost/~api/users/me; echo

You get a JSON object describing the admin user. A wrong password returns HTTP 401.

The interactive API reference is served in-product at http://<vm-public-ip>/~help/api.

Step 9 - Create a project and clone it over HTTPS

Create a repository from the web UI (New Project), then clone it using the admin credentials. Run this from your workstation.

git clone http://admin@<vm-public-ip>/<your-project>.git

OneDev prompts for the admin password (or an access token you create under My Profile then Access Tokens).

The nginx proxy is configured with a 2 GB body size, so large pushes and LFS objects go through cleanly.

Step 10 - Clone over SSH (optional)

OneDev runs a git-over-SSH listener on port 6611.

Add your SSH public key under My Profile then SSH Keys in the web UI, and open 6611/tcp on the NSG. Then clone.

git clone ssh://git@<vm-public-ip>:6611/<your-project>.git

Step 11 - Confirm data lives on the dedicated disk

All repository data is stored on the dedicated Azure data disk. This includes the embedded database, Git repositories, compiled outputs and attachments. The data survives OS changes and can be resized independently. Check the mount.

findmnt /var/lib/onedev

The mount is backed by a separate Azure data disk captured into the image and re-provisioned on every VM.

Enabling HTTPS

The nginx reverse proxy terminates plain HTTP on port 80. For public exposure, put a certificate in front of it.

The simplest path is to add a DNS name for the VM and use the companion SecureAnyCloud nginx-ssl-certbot image as a TLS reverse proxy. Alternatively, install certbot and extend the existing nginx site with a listen 443 ssl; server block and your certificate paths.

Keep OneDev itself bound to loopback, so the only public web surface is the authenticated, TLS-terminated proxy.

After you enable TLS, update the server URL under Administration then System Setting, so OneDev emits correct clone URLs.

Maintenance

• Configuration: OneDev's HTTP and SSH ports live in /opt/onedev/conf/server.properties. The database connection is in /opt/onedev/conf/hibernate.properties (the image uses the embedded HSQLDB on the data disk). To apply changes, edit the files and run sudo systemctl restart onedev.
• Backups: Snapshot the /var/lib/onedev data disk, or use OneDev's built-in database backup under Administration then Database Backup.
• Upgrades: OneDev's web UI offers in-product upgrade guidance. For a clean upgrade, replace the /opt/onedev runtime with a newer release, preserve /var/lib/onedev, and restart the service.
• Security patches: Unattended-upgrades remains enabled, so the OS continues to receive security updates automatically.

Support

SecureAnyCloud provides 24/7 expert support for this image. Contact sales@secureanycloud.com.

OneDev is a trademark of its respective owner. This image is produced by SecureAnyCloud and is not affiliated with or endorsed by the OneDev project. OneDev is distributed under the MIT License.

Deploy on Azure

Launch OneDev on Ubuntu 24.04 LTS on Azure with 24/7 support from SecureAnyCloud.

View this image

Need Help?

Our support team is available 24/7.

sales@secureanycloud.com