Changing the hostname

docker

(Jarrett Colby) #1

I installed Discourse with Docker per the official instructions.

At the time of installation, I didn’t have a domain name ready, so I just used an IP address as the hostname. Later, I got the domain name working, and Discourse is accessible via that hostname.

However, the IP address–which is no longer the correct hostname for this installation–still shows up in various places. One such place is outgoing emails. When a user receives a notification of a new post, the link back to the topic has the IP address as the hostname.

I’ve replaced the IP address where I could find it:

  • In the host OS at /var/discourse/containers/app.yml, the DISCOURSE_HOSTNAME key.
  • Inside the Docker container at /var/www/discourse/config/discourse.conf, the hostname key.

I tried SiteSetting.refresh! from the Rails console. I also tried restarting the Docker container with ./launcher restart app.

I see that in app/views/email/_post.html.erb, the links go to Discourse.base_url. From the Rails console, I see that Discourse.base_url is correct:

root@discourse:/var/www/discourse# rails console production
irb(main):001:0> Discourse.base_url
=> "http://myhost.example.com"

Yet the outgoing emails still have the IP address instead of the correct hostname. Any idea why that would happen, and how it might be fixed?


#2

I think rebuilding the container will resolve your issue. Double-check the hostname details in the app.yml and make sure they’re saved to your liking. Then rebuild Discourse’s container, which destroys the old one, bootstraps a new one, and starts it up.

Navigate to the Discourse directory:

cd /var/discourse

Then use the rebuild command:

./launcher rebuild app

Hope that helps!


(Jarrett Colby) #3

What becomes of the database upon a rebuild? Does it get wiped out? We already have content we’d like to preserve.

Instead of a rebuild, would it be possible to find where the setting is stored and edit it manually?


#4

Rebuild preserves the database. If you still are paranoid, just make a backup and download that, it contains all users, posts, etc.


#5

Fear not, the database is preserved through rebuilds. The only things that
could be “lost” are items mentioned in the app.yml. In this case, that
includes your old IP address! Also, if you ever want to install new
plugins, that process will also require app rebuilds.


(Eric Toombs) #9

Are you sure a rebuild is necessary? This post says a rebuild isn’t necessary for any changes to the env section.

update: I changed the hostname and restarted the service without rebuilding. It hasn’t exploded on me yet…


(system) #10

(Sam Saffron) #11

Environments updates require you destroy the old container and then start a new one.

This can be done with

./launcher destroy app
./launcher start app

People though get confused about this so we usually just prescribe

./launcher rebuild app

Which means you eat a bit more of an outage but it works for pretty much everything.


(Sam Saffron) #12