Shiloh/frappe_docker
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Update Moving to a new server

steffeydev 2025-07-17 21:05:03 +00:00
parent b2cacd6010
commit c107036c0b
1 changed files with 11 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
Moving-to-a-new-server.md

@ -1,15 +1,22 @@
First, switch domains to point at new servers.
On the old server:
1. Stop docker on old server: `systemctl stop docker`
2. Backup volumes:
3. Backup volumes:
* `docker run --rm -v frappe_db-data:/data -v /tmp:/backup busybox tar cvf /backup/db.tar /data`
* `docker run --rm -v frappe_sites:/data -v /tmp:/backup busybox tar cvf /backup/sites.tar /data`
On the new server:
3. Generate SSH keys, and add it to the authorized keys of the old server
4. Copy the archives over:
1. Generate SSH keys, and add it to the authorized keys of the old server
2. Copy the archives over:
* `scp <old-user>@<old-ip>:/tmp/db.tar /tmp`
* `scp <old-user>@<old-ip>:/tmp/sites.tar /tmp`
5. Create the new volumes and restore the data:
3. Create the new volumes and restore the data:
* `docker volume create frappe_db-data && docker run --rm -v frappe_db-data:/data -v /tmp:/backup busybox tar xvf /backup/db.tar`
* `docker volume create frappe_sites && docker run --rm -v frappe_sites:/data -v /tmp:/backup busybox tar xvf /backup/sites.tar`
4. Copy over `/root/frappe-compose.yml`
5. `docker compose -f /root/frappe-compose.yml up -d`
Service should now be back up and running. The proxy may need a minute to fetch the certs again, since we didn't copy those over.