From 6532fe29e493dee1fe7ed5a70e6e599646f33c7f Mon Sep 17 00:00:00 2001
From: Christoph Cullmann <cullmann@kde.org>
Date: Mon, 8 Apr 2019 23:09:35 +0200
Subject: tell how to move web server stuff

---
 content/posts/webserver-transition.md | 47 +++++++++++++++++++++++++++++++++++
 1 file changed, 47 insertions(+)
 create mode 100644 content/posts/webserver-transition.md

diff --git a/content/posts/webserver-transition.md b/content/posts/webserver-transition.md
new file mode 100644
index 0000000..4bdc8d8
--- /dev/null
+++ b/content/posts/webserver-transition.md
@@ -0,0 +1,47 @@
+---
+title: "Web-Server Transition"
+date: 2019-04-08T22:45:00+02:00
+draft: false
+---
+
+Several years the [kate-editor.org](https://kate-editor.org) & [cullmann.io](https://cullmann.io) pages got hosted on a [Hetzner](https://www.hetzner.de/) root server.
+To reduce costs and switch away from old hardware they got now moved to a [OpenVZ](https://openvz.org/) based virtual server at [Host Europe](https://www.hosteurope.de).
+
+On both servers [CentOS](https://centos.org) 7.x is running, it did always provide a stable foundation of the web services.
+
+As with any server move in the past, I always need to search how to best move the data/config from one server to the other.
+To document this for me and others, here the quick way to move the basic things needed for web services using just plain [Apache](https://httpd.apache.org/) & [MariaDB](https://mariadb.org/).
+
+The following steps assume you have installed the same packages on both machines and the new machine is allowed to ssh as root to the old one.
+If you have non-system users, you should create them with the same ids as on the old server.
+
+For the following shell commands, the old server address is $SERV and the MariaDB root password is $PASS on both machines.
+Best use the raw IP as address if you are in parallel updating your DNS entries to avoid confusion (and wrong syncs).
+
+**Attention: Wrong syncing of stuff can have disastrous consequences! Check all commands again before executing them, don't trust random people like me without verification!**
+
+* sync your data, assuming it is in /home and /srv/(ftp/www)
+
+> rsync --delete -av root@$SERV:/home/ /home<br>
+> rsync --delete -av root@$SERV:/srv/ftp /srv<br>
+> rsync --delete -av root@$SERV:/srv/www /srv<br>
+
+* transfer your databases
+
+> ssh root@$SERV "mysqldump -u root -p$PASS --all-databases > /root/db.sql"<br>
+> scp root@$SERV:/root/db.sql /root/<br>
+> mysql -u root -p$PASS < /root/db.sql<br>
+
+* sync configs (you might need more, this is just apache & vsftp)
+
+> rsync --delete -av root@$SERV:/etc/httpd /etc<br>
+> rsync --delete -av root@$SERV:/etc/letsencrypt /etc<br>
+> rsync --delete -av root@$SERV:/etc/vsftpd /etc<br>
+
+* get crontabs over for later re-use, store them in the root home
+
+> rsync --delete -av root@$SERV:/var/spool/cron /root
+
+Now all things should be there and after some service restarts e.g. [WordPress](https://wordpress.org/) powered pages should be up-and-running again.
+
+I hope this short how-to helps others and allows me to avoid searching stuff in the future once again from scratch.
-- 
cgit v1.2.3