<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: MOHAMMAD TAGHI</title>
    <description>The latest articles on DEV Community by MOHAMMAD TAGHI (@mohammad_taghi_9ae1cbacc0).</description>
    <link>https://dev.to/mohammad_taghi_9ae1cbacc0</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4179716%2Ffbb8a9fb-fd21-4ec9-9ad3-9b36254ddb4c.jpg</url>
      <title>DEV Community: MOHAMMAD TAGHI</title>
      <link>https://dev.to/mohammad_taghi_9ae1cbacc0</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/mohammad_taghi_9ae1cbacc0"/>
    <language>en</language>
    <item>
      <title>Move a Coolify project to another server in two terminals</title>
      <dc:creator>MOHAMMAD TAGHI</dc:creator>
      <pubDate>Wed, 21 Oct 2026 20:18:44 +0000</pubDate>
      <link>https://dev.to/mohammad_taghi_9ae1cbacc0/move-a-coolify-project-to-another-server-in-two-terminals-3ac</link>
      <guid>https://dev.to/mohammad_taghi_9ae1cbacc0/move-a-coolify-project-to-another-server-in-two-terminals-3ac</guid>
      <description>&lt;p&gt;Moving a Coolify app to a new VPS can mean rebuilding the project, moving database data and volumes, copying environment variables, and sorting out domains by hand. I built &lt;strong&gt;Coolify Mirror&lt;/strong&gt;, a free, open-source tool to make that move super easy to start and simple to review.&lt;/p&gt;

&lt;p&gt;Here's the flow:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;On the &lt;strong&gt;old server&lt;/strong&gt;, install Coolify Mirror and choose a project, individual resources, or the whole server. It creates an encrypted backup and prints a restore command with a share code.&lt;/li&gt;
&lt;li&gt;On the &lt;strong&gt;new server&lt;/strong&gt;, paste that command. The tool downloads and verifies the backup, checks the target, and shows what it plans to restore. Nothing is changed until you confirm.&lt;/li&gt;
&lt;li&gt;After the restore, check the running resources and point DNS at the new server.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fraw.githubusercontent.com%2Fmtalavi%2Fcoolify-mirror%2Fmain%2Fdocs%2Fdemo-light.gif" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fraw.githubusercontent.com%2Fmtalavi%2Fcoolify-mirror%2Fmain%2Fdocs%2Fdemo-light.gif" alt="A move from the source server to the destination server" width="559" height="371"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Try it
&lt;/h2&gt;

&lt;p&gt;SSH into the old server and run:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;curl &lt;span class="nt"&gt;-fsSL&lt;/span&gt; https://raw.githubusercontent.com/mtalavi/coolify-mirror/main/install.sh | &lt;span class="nb"&gt;sudo &lt;/span&gt;sh
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Choose &lt;strong&gt;Back up apps&lt;/strong&gt;, select your project, and choose to share through Coolify's proxy on port 443. Keep the share running and copy the command it prints. Paste &lt;strong&gt;that generated command&lt;/strong&gt; on the new server; the share code in it is unique to your backup. Review the restore preview, then confirm when you're ready.&lt;/p&gt;

&lt;p&gt;The backup can include project configuration, environment variables and secrets, volumes and host files, database data, images, and proxy settings. Coolify Mirror runs preflight checks for version, space, and conflicts, then checks that the restored resources are running. It is designed to be fast to get started and easy to use; the actual transfer time depends on your data and connection.&lt;/p&gt;

&lt;h2&gt;
  
  
  Before you start
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Both servers need self-hosted &lt;strong&gt;Coolify v4.3 or v4.4 on the exact same version&lt;/strong&gt;, with root or sudo access. If they differ, update first.&lt;/li&gt;
&lt;li&gt;A whole-server restore needs an empty target Coolify. A selective project restore can merge into a Coolify already in use, subject to conflict checks.&lt;/li&gt;
&lt;li&gt;DNS, webhooks, and scheduled tasks may still need a manual switch after the restore. Check the &lt;a href="https://github.com/mtalavi/coolify-mirror#limitations" rel="noopener noreferrer"&gt;limitations&lt;/a&gt; for your setup.&lt;/li&gt;
&lt;li&gt;For a large backup, use &lt;code&gt;tmux&lt;/code&gt; so a dropped SSH session does not interrupt the copy.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The &lt;a href="https://coolify-mirror.pages.dev" rel="noopener noreferrer"&gt;website&lt;/a&gt; shows the full two-terminal demo. The &lt;a href="https://github.com/mtalavi/coolify-mirror" rel="noopener noreferrer"&gt;GitHub repository&lt;/a&gt; has the source, walkthrough, limitations, and issue tracker. Coolify Mirror is independent and not affiliated with Coolify. If you try it, feedback and feature ideas are welcome.&lt;/p&gt;

</description>
      <category>coolify</category>
      <category>devops</category>
      <category>opensource</category>
    </item>
  </channel>
</rss>
