Migrating from Heroku to a Hosted/Cloud instance

docker

(Kim Pellikaan) #1

If you ever need to migrate away from Heroku to a currently supported infrastructure by discourse it can be quite troublesome.

We did the following to be able to create a backup which could thereafter be imported by discours’s hosted solution. These steps can also be used if you just want to migrate to your own cloud hosted instance.

Get the data out of Heroku

There are 2 parts you need to backup:

  • Database
  • Images

Note: Before you continue make sure the Heroku version is updated to the last version

Export the DB

To export the DB from Heroku to your development system follow the instructions here:

You can also login to the dashboard and create and download a PG dump.

Get the images

In our case we saved the images to AWS S3. To download all the images at once we used the AWS CLI.

  1. First make sure you have the AWS CLI installed.
    Installing the AWS Command Line Interface - AWS Command Line Interface
  2. Use the S3 argument to download your images.
    s3 — AWS CLI 1.14.18 Command Reference

For example:

aws s3 cp /tmp/foo/ s3://bucket/ --recursive

Build a new discourse instance

Create a new discourse instance by following the instructions:

Start the restore

Assuming that you have a working discourse instance and that the versions of both Heroku and the new cloud instance are the same (discourse versions) let’s start the import.

Get your backups from your local system in the docker container.

To get your images and db from your local to the vps I prefer scp. You can also do this with an sftp client if that is your preference.

An example of the SCP command assuming that your public key is set:

scp /tmp/latest.dump root@xxx.xxx.xxx.xxx:/tmp

Get the backups in the container

The Container has one volume mounted; /var/discourse/shared/standalone/

Copy the backups to this location and you can access them when your inside your container.

Importing your backups

Before we can start importing we need to convert the compressed pg dump that Heroku gave us to an sql file.

Else you get these kinds of issues:

Convert Compressed pg dump

You need to enter the Docker container inside your vps. Thereafter we can convert the dump to an sql file.

Commands:

cd /var/discourse
sudo ./launcher enter app
 sudo -u postgres pg_restore -O -f /tmp/latest.sql  /shared/latest.dump
exit
exit

Now you should have a file called latest.sql in you tmp folder.

Do the restore

Go to the following link and follow the instructions under the Restore header.

Rebuild container

Discourse relays heavily on caching. This means we need to rebuild the container after the DB is restored. Outside your container in the root of your vps do:

cd /var/discourse
sudo ./launcher rebuild app

Optional: Resetting your force_hostname value

There is a good chance that you set the force_hostname value to make sure all links are working correct. In the new environment this is no longer needed so you need to unset the value

cd /var/docker
sudo ./launcher enter app
su - discourse
bundle exec rails c
SiteSetting.force_hostname = “"
exit
exit
exit

Now you should be good to go! Create backups to be imported later or just let it run like this.


(Jeff Atwood) #2

Wow this is super detailed thank you for putting it together!


(Sam Saffron) #3

I wonder though, could you not enable daily backups to aws and use that? Or switch to a single dyno, do a manual backup from the admin interface and then use it?


(Kim Pellikaan) #4

@sam, heroku does not have pg_dump installed on the instance. Because of this the backups don’t work at all on heroku.