Everthing is working, including e-mail delivery - but: the activation/test links in the emails are of the form: http://discuss.mysite.com:4000/… I’ve checked my app.yml and there’s no port 4000 in there. Is the system somehow thinking it’s running in development mode?

Installed via Docker, but imported a vBulletin database from inside the development environment (using git clone … → vagrant up → vagrant ssh → ruby script/import_scripts/vbulletin.rb etc.). Inside vagrant I then took a database dump using: pg_dump -xOf ./discourse-backup.sql -n public discourse_development Then copied this dump to my production discourse install and did inside psql: drop schema public cascade; create schema public; … Then on the command line sudo -u postgres psql -f /shared/discourse-backup.sql discourse Noticed that the gravatar paths are all wrong as well. Since the vBulletin import took ~8 hours (200 000 posts), I’m reluctant to start over. Can the email-path be edited inside the database (couldn’t find anything doing a simply ‘grep’ on the dump)?

[imagen] apotry: pg_dump -xOf ./discourse-backup.sql -n public discourse_development Why didn’t you use the backup/restore feature in Discourse? [imagen] apotry: Can the email-path be edited inside the database (couldn’t find anything doing a simply ‘grep’ on the dump) The discourse remap script might help you here.

Actually also noticed that the load times (in ms) show up on the left side of the screen. Does that mean my discourse is running in development mode and not in production? How can I change this? codinghorror: where do I find the “WARNING: DEVELOPER ONLY” settings?

[imagen] apotry: Actually also noticed that the load times (in ms) show up on the left side of the screen. Does that mean my discourse is running in development mode and not in production? It’s only displayed for administrators, even in production. [imagen] apotry: codinghorror: where do I find the “WARNING: DEVELOPER ONLY” settings? If you search for DEVELOPER ONLY in the site settings and you have results, then you’re definitely running in development mode (we hide them when running in production mode).

No, nothing comes up when I do that - No results found.

But if you imported a database from a development mode import, that setting might be present, I guess.

The odd thing is that it’s port 4000. That’s used for Unicorn, not the dev-mode webserver (which defaults to 3000, as does SiteSetting.port)… Anyway, try: /var/discourse/launcher enter app rails c SiteSetting.port = "" SiteSetting.force_hostname = "" SiteSetting.queue_jobs = true

SiteSetting.port returned 4000, so setting this to “” fixed the email issue. Thank you!

Test & activation emails are sent with port 4000 included

Product Support

codinghorror (Jeff Atwood) 25 Marzo, 2015 22:34 2

Do you have any of the WARNING: DEVELOPER ONLY settings set? Is this installed using our Docker guide?

Tema		Respuestas	Vistas
Install Discourse, change docker port 80 Self-hosting unsupported-install , docker	14	15244	11 Marzo 2024
Discourse-app container starts then silently stops Self-hosting unsupported-install	40	4359	20 Septiembre 2022
Verification Email will not send due to errors caused by Docker filesystem Self-hosting email	23	7183	4 Septiembre 2015
Avatar not found after updating to 1.4 beta because of port in URL Bug	9	2065	1 Noviembre 2015
Email doesn't work after fresh install Self-hosting docker , email	11	4460	29 Enero 2016

Test & activation emails are sent with port 4000 included

Temas relacionados