<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Deployment on Arivu</title>
		<link>https://arivu.app/tags/deployment/</link>
		<description>Recent content in Deployment on Arivu</description>
		<generator>Hugo</generator>
		<language>en-us</language>
		
		
		
		
			<lastBuildDate>Sat, 24 Oct 2026 00:00:00 +0000</lastBuildDate>
		
			<atom:link href="https://arivu.app/tags/deployment/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Run Arivu with Docker Compose</title>
				<link>https://arivu.app/chronicle/run-arivu-with-docker-compose/</link>
				<pubDate>Sat, 24 Oct 2026 00:00:00 +0000</pubDate>
				<guid>https://arivu.app/chronicle/run-arivu-with-docker-compose/</guid>
				<description>&lt;p&gt;The guided installer has been the way to run Arivu on your own server: one command on a Linux VPS, and it sets up the app, complete capture, the proxy, and backups. That still works and is still what we recommend for a server you manage by hand.&lt;/p&gt;&#xA;&lt;p&gt;But plenty of people already run their self-hosted apps a different way, on a Docker host or a self-hosted platform such as Dokploy. Starting with Arivu 1.8.3, Arivu fits there too.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
