On a fresh import, I see that Discobot creates cooked posts that contain If you’d like to learn more, select below and bookmark this personal message . If you do, there may be a in your future! It would seem to me hard-coding the site URL isn’t necessary here, though there could well be something that I’m missing that makes including the site name in the URL desirable or necessary. Also, I see that avatars get cooked like this, also with the host name similarly included. cmomoney: \n" + try this again: https://www.dropbox.com/s/8b1lo2hndsu782t/save_game_logic_1_2.zip?dl=0\n" + " \n" + Oh, and uploads are also cooked like this: \n" + " YGYPYG.jpg 1919x1079 435 KB \n" + " Working on some game assets and decided to make some art with it as well. ", Perhaps all of these need the hostname embedded to make multisite work? I think that my immediate solution is to set force_hostname before I run the importer. Does that seem right? The other solution that I can think of would be to rebake posts that contain importer_hostname in cooked. Also, the more I think about it, the more I think that discobot should be disabled by default on imports. @gerhard, @tgxworld, What do you think? If you agree, I’ll endeavor to submit a PR wtih that in base.rb. Or maybe turn it off before import and restore it after the import is done?

[image] pfaffman: Perhaps all of these need the hostname embedded to make multisite work? No, that shouldn’t be the case. … You can use script/discourse remap to replace, that is a lot faster.

[image] pfaffman: I think that my immediate solution is to set force_hostname before I run the importer. Does that seem right? I believe that setting has caused a lot of trauma recently (and as I understand it, is meant to be strictly local dev only) so I’m surprised you would reach for it again.

I’m curious, are you importing in development or production mode?

[image] zogstrip: I’m curious, are you importing in development or production mode? This is in production mode, on a variation of phpbb3.template.yml. In the past I’ve always used a development environment, so perhaps I have some fundamental misunderstanding of how it works in Development. [image] codinghorror: I believe that setting has caused a lot of trauma recently (and as I understand it, is meant to be strictly local dev only) so I’m surprised you would reach for it again. Sorry about that. I suspect that it was more traumatic for Josh and Team than I know. Yes, hence: [image] pfaffman: Or maybe turn it off before import and restore it after the import is done? My notion was that if I set that then the above-mentioned URLs would have to correct hostname so they wouldn’t need to be remapped. But script/discourse remap seems to be the solution that I’m searching for. Speaking of trauma, I’ve got 2 imports (one for a hosted customer) that each took over a week to run that went off the rails, so I really want to make sure that I don’t goof it up again.

[image] pfaffman: This is in production mode I’m always setting the DISCOURSE_HOSTNAME to the correct hostname when I’m running an import within a Docker container. Is that not an option? [image] pfaffman: I think that discobot should be disabled by default on imports. I’m not sure about that. Imported users might also need to learn how to use Discourse…

[image] gerhard: I’m always setting the DISCOURSE_HOSTNAME to the correct hostname when I’m running an import within a Docker container. Is that not an option? Doh! That’s what I should be doing. It somehow didn’t occur to me since it’s not the host name of the import machine. So that’s how to “force” the hostname. [image] gerhard: I’m not sure about that. Imported users might also need to learn how to use Discourse Hmm.When you say it like that, it makes me sound foolish. :wink: It’s just that with tens or hundreds of thousands of users, it makes for a big sidekiq queue. . .

Discobot, avatars, uploads include hard-code hostname in cooked

Product Support Migration

codinghorror (Jeff Atwood) April 19, 2018, 9:54pm 3

I believe that setting has caused a lot of trauma recently (and as I understand it, is meant to be strictly local dev only) so I’m surprised you would reach for it again.

Topic		Replies	Views
Migrate a phpBB3 forum to Discourse Migrating to Discourse how-to	464	109830	September 4, 2025
phpBB 3 Importer (old) Feature	89	18590	October 8, 2014
Missing avatars and site images after import of a backup Product Support	7	1357	October 31, 2019
Migrate a vBulletin 4 forum to Discourse Sysadmins how-to	183	35098	November 9, 2025
Large Drupal forum migration, importer errors and limitations Migration drupal	28	3139	August 10, 2023

Discobot, avatars, uploads include hard-code hostname in cooked

Related topics