<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>OneDev CI/CD on StackOnward</title><link>https://stackonward.com/tags/onedev-ci/cd/</link><description>Recent content in OneDev CI/CD on StackOnward</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Fri, 11 Sep 2026 04:24:00 +0800</lastBuildDate><atom:link href="https://stackonward.com/tags/onedev-ci/cd/index.xml" rel="self" type="application/rss+xml"/><item><title>OneDev Tutorial: Docker Compose, Git, and CI/CD on One Server</title><link>https://stackonward.com/posts/onedev-production-deployment/</link><pubDate>Fri, 11 Sep 2026 04:24:00 +0800</pubDate><guid>https://stackonward.com/posts/onedev-production-deployment/</guid><description>&lt;p&gt;A OneDev tutorial starts with one instance that can host Git, review, issues, CI/CD, artifacts, and packages. Keep code on a server you operate, and skip running a separate Git service, CI, and package registry, when that trade-off is worth the ops work. The official single-node baseline is also lower than full GitLab.&lt;/p&gt;
&lt;p&gt;The environment is one 64-bit Linux host: OneDev and PostgreSQL run under Docker Compose, and Caddy terminates HTTPS. After the instance is ready, create a Go project and prove push, tests, image build, production deploy, backup, restore, and upgrade. A container in &lt;code&gt;running&lt;/code&gt; is not enough. The repository, Git SSH, the pipeline, and restore still have to work.&lt;/p&gt;</description></item></channel></rss>