I’m currently migrating a discussion board to Discourse. I’m still learning about how Discourse is distributed and set up, but I’ve got the data imported and everything configured. After importing all the topics, I now have a long list of mappings from the old topic id to the new Discourse topic id. I’d like to put all of these into rewrite rules and add them to the Nginx server. My question: what is the best way to do this? I don’t think it’s a good idea to just put them in the /etc/nginx/conf.d/discourse.conf as that may cause issues when upgrading Discourse in the future. Or won’t it? Can I put them in a separate conf? Will that file survive when the server restarts and/or updates are made to the Docker container? (or is that not even an issue and should I stop worrying :tropical_drink: )

Yeah, for that there is this howto [imagem] Redirect old forum URLs to new Discourse URLs using permalinks packageMigrating to Discourse bookmark This reference explains how Discourse permalinks redirect old URL paths to new destinations, how permalink normalizations work, and how to test and troubleshoot redirects after a migration or URL structure change. person_raising_hand Required user level: Administrator computer Console access required only when creating permalinks from an importer, script, or Rails console When you migrate from another forum or change your site’s URL structure, old links from search engines,…

Add a template or a hook and do a replace rule. see the ssl template in the templates directory for an example.

No I think he means a list of old ID mapping to new IDs. @neil didn’t you add support for this kind of lookup table somewhere?

Thanks for the pointer. Since I’m a Ruby novice and I barely know enough to be dangerous, I’d prefer to keep this separate. It will also be easier (I hope) to update on the fly, if it turns out I forgot to map some rules once I have flipped the switch and turned on the Discourse forum. I’m going to try to use the Nginx map module first and see how that goes: https://meta.discourse.org/t/redirecting-old-forum-urls-to-new-discourse-urls/20930/10?u=peter_backx

[imagem] peter_backx: I’d prefer to keep this separate. It will also be easier (I hope) to update on the fly It’s definitely a preference. Yesterday I was able to add one rule to one site’s permalinks table because they wanted a certain redirect from their old forums to their new forums that we host. In our environment, this was much easier than updating haproxy config. I don’t want to fill our config files with countless arbitrary redirects from all our customers. It would be insane for us, but maybe not for you.

Correct way to add rewrite rules to Nginx

Product Support Self-hosting

sam (Sam Saffron) 1 Fevereiro , 2015 20:58 4

Yeah, for that there is this howto

Tópico		Respostas	Vistas
Redirect old URLs Marketplace	1	2006	1 Fevereiro , 2015
How can I use dynamic redirects? Self-hosting	5	841	12 Dezembro , 2020
URL rewrite for domain change in permalinks Product Support	6	2671	8 Março , 2017
Redirect vBulletin URLs to Discourse URLs Migrating to Discourse how-to	5	9999	25 Janeiro , 2018
Redirect URL with Nginx in Digital Ocean Self-hosting	14	1754	7 Agosto , 2022

Correct way to add rewrite rules to Nginx

Related topics