Switch N8N server

[mkllnk]

We got the new server: n8n.openfoodnetwork.org

We still got the old server running lots of worklfows: n8n.openfoodnetwork.org.uk

Many workflows can be transferred without changing anything else. But workflows triggering webhooks have a different URL on the new server. We need to update all integrations to use the new server.

One example is the Connected Apps feature within OFN. Every connected app has a link in its data to delete OFN data from the app and end the connection. We will need a migration to update all those entries.

Once we migrated all workflows to the new server, we can also point the old URL to the new server to achieve backwards compatibility. Then we don't actually need to update URLs. But updating URLs will reduce maintenance because we don't need to maintain n8n.openfoodnetwork.org.uk any longer.

Task list:

• Activate API workflows on the new server and use them.
• Deactivate API workflows on the old server.
• Use new Connected App workflows. (Done for Disco Regen)
• Deactivate old Connected App workflows. (Done for Disco Regen)

[mkllnk]

@rioug What you think about pointing the old domain to the new server? Is it easy to connect n8n to two domains? Obviously, we have to activate all the need workflows first and can't do that just yet.

[rioug]

We need to make sure we can access prod DB from the new router before doing that as well.

Looks like it's fairly easy to connect n8n to two domain, it should be just a matter of configuring traefik (Edge router) to point the two domain to the n8n container, ie: https://frigi.ch/en/2022/07/multiple-domains-for-the-same-container-with-traefik/

And then updating the DNS record to point to the server.