I’m trying to migrate discourse from a personal hosting to a Amazon LightSail server. I’ve searched the forum and read all the posts about migrating servers and settings up discourse: Move your Discourse Instance to a Different Server Restore a backup from the command line How To Install Discours…

If you’re not going to use the same S3 bucket then there is a hidden setting that forces the backup to download the S3 files. You can look in the settings file for the name and set it at the rails console. There’s a topic that discusses it, but it might be easiest to look in settings.yml. You don’t…

The goal is ideally to “lift n shift” but that’s not possible with amazon lightsail since one cannot import an existing image. So yes it would be using the exact same S3. It seems like your approach is closest to lift n shift. If I understand what you’re saying, I can just tar/gz the entire /var/di…

Yes, move the files however makes sense to you. Yes, you’ll need to do a rebuild to build and launch a new container.

Thanks. Apparently lift n shift wasn’t as clean as I thought, there are a few checks to be done before and after to ensure a smooth lift n shift operation (Postgress was being upgraded from12.0 to 13.0 which taught me a few lessons in the lift n shift process). Here’s a step by step guide for future…

[이미지] RBoy: without having to go through a discourse setup process? Do you mean without running discourse-setup or do you mean without building the container that is required to run Discourse? If you mean the latter, it’s possible by pushing the old image to a repo that the new server could u…

[이미지] pfaffman: but you’d still have some fiddly bits on getting the new server to get the let’s encrypt certs Yep, that’s the only thing that was preventing me from doing a ./discourse-setup on the new server and then restore from the S3 image (and how to do this without access to the web ad…

If you copy over the yml files inside of containers then you don’t need discourse-setup (it can adjust memory params if they are different on the new server, but you could do that afterward). You’d just ./launcher rebuild app.

Okay I think I see what you’re saying but to be sure let me restate my understanding. In the original server, it was set up to backup discourse to S3 (which are the settings and site content). By copying the yml files from the containers, it will copy all the original server configuration over to …

If you copy the old /var/discourse you’ll get the certificates and the rebuild will work as expected. You can restore from the command line from inside the container.

Thanks for the detailed steps, I just had to do something similar, moving to a new host. Since the site was working, I did not like to go through the backups, so I followed the steps here. It almost worked but the rebuild on the new host failed. It turns out the UID/GID mapping was not entirely t…

같은 DNS 이름을 유지하면서 Discourse를 다른 서버로 이전하는 방법

제품 지원 자체 호스팅

RBoy (RBoy) 4월 12, 2024, 12:08오후 12

1GB RAM을 사용하는 경우, 재구축 실패를 방지하기 위해 최소 4GB의 스왑을 생성하도록 하십시오. 관련 링크: 3.1.x to 3.2.0 upgrade hangs/fails on 1GB instance

글		댓글	조회수
Move Discourse to a new server without setting up the web UI first? Self-hosting	11	3089	9월 3, 2022
Move your Discourse Instance to a Different Server Self-Hosting migrations , how-to	11	294249	8월 11, 2026
Transfer from bitnami to normal discourse Self-hosting	7	2981	6월 7, 2019
Migrating Discourse from one DigitalOcean droplet to another without downtime Self-hosting	12	1845	12월 30, 2020
How to switch Discourse servers? Self-hosting	6	1102	1월 19, 2023

같은 DNS 이름을 유지하면서 Discourse를 다른 서버로 이전하는 방법

Related topics