Plan for moving portmap to Cloud Run :
Make a ticket or three for all this
App engine can continue to run “portmap.dtinit.org”
Meanwhile setup cloud run
with its own URL not DTI related (which we’ll fix when we switch over)
Deploy steps - replace the portmap deploy steps (In a branch? So main can keep deploying to app engine until we switch over)
Config data e.g. keys for database access
Make the cloud run instance talk to the same database & test
Transfer the domain name over via DNS entry point ‘portmap’ to the new location
Delete the app engine instance
This will allow us to have portmap, writefreely and the trust registry all running with consistent operations - they will all have their own Google Cloud Projects (for billing and future use of permissions )
When using CLI, tell the CLI which project you are working on for commands to have the right project context
How to avoid losing all your configuration?
Aarón is still investigating this part
Plan for moving portmap to Cloud Run : Make a ticket or three for all this App engine can continue to run “portmap.dtinit.org” Meanwhile setup cloud run with its own URL not DTI related (which we’ll fix when we switch over) Deploy steps - replace the portmap deploy steps (In a branch? So main can keep deploying to app engine until we switch over) Config data e.g. keys for database access Make the cloud run instance talk to the same database & test Transfer the domain name over via DNS entry point ‘portmap’ to the new location Delete the app engine instance This will allow us to have portmap, writefreely and the trust registry all running with consistent operations - they will all have their own Google Cloud Projects (for billing and future use of permissions ) When using CLI, tell the CLI which project you are working on for commands to have the right project context How to avoid losing all your configuration? Aarón is still investigating this part