How to change the domain for an existing deployment?

[dennisvang]

Suppose we want to migrate an existing FDP to a new domain.

Here's what we did:

• configured our reverse-proxy to handle the new domain
• updated all triples in the triple store to match the new domain
• updated the instance.persistentUrl setting, in the FDP configuration, to match the new domain

However, the FDP-client still fails with a status 404 Not Found.

Do we need to do anything else?

[dennisvang]

The FDP stores its (internal) application data in mongodb.

This includes references to its domain, in URIs in the ACL and metadata collections.

So, these need to be updated too.

Unfortunately, there is no built-in solution for this yet, so we need to update the mongodb content manually.

Here's a quick and dirty way to do this using the mongodb shell (mongosh):

1. log in to your host
2. tear down the fdp container, if it is running

   docker compose down fdp

3. open a mongosh shell in the running mongodb container:

   docker compose exec mongo mongosh

4. activate the FDP database, typically called fdp (you can list all databases using e.g. show dbs):

   use fdp
   

5. [optional] inspect the ACL and metadata collections to verify that the old domain is present:

   db.ACL.find()
   db.metadata.find()
   

6. update the URIs in the ACL collection:

   db.ACL.updateMany(
     {instanceId: {$regex: /<old-uri-pattern>/}},
     [{$set: {instanceId: {$replaceOne: {input: "$instanceId", find: "<old-uri>", replacement: "<new-uri>"}}}}]
   )
   

7. update the URIs in the metadata collection:

   db.metadata.updateMany(
     {uri: {$regex: /<old-uri-pattern>/}},
     [{$set: {uri: {$replaceOne: {input: "$uri", find: "<old-uri>", replacement: "<new-uri>"}}}}]
   )
   

8. inspect the collections again to verify the changes (see 5.)
9. exit the mongodb shell:

   .exit
   

10. set up the fdp container again:

docker compose up -d fdp