Rub21
commented
3 weeks ago I have been working on creating the development environment in the Kubernetes cluster. We now have a namespace for development that shares the same cluster with staging, and I have also deployed some required services necessary for development, such as TM.
@erictheise, as we discussed last time, here is the latest version of the TM deployed in the development environment.
- TM API: https://tm-api.development.staging.openhistoricalmap.org
- TM Web: https://tasks.development.staging.openhistoricalmap.org This is still in progress, as CloudFront is taking time to serve the page.
Also if you want deploy changes, here is the branch https://github.com/OpenHistoricalMap/ohm-deploy/tree/development
We are currently running both staging and production environments, but we recently encountered a setback with Tasking Manager, which was running in staging and was difficult to move from staging to production. This is why we had to roll back the changes link to proceed with other pending tasks.
To prevent similar issues in the future, it would be beneficial to set up a dedicated development environment, allowing us to test services in development before promoting them to staging for further testing. Right now, we’re using staging for development as well, which isn’t ideal. In a recent conversation with @erictheise, he needs a Tasking Manager API to continue work on tasking-manager iD. Therefore, I plan to spin up a new environment within staging cluster, dedicated to development.
cc. @erictheise @danrademacher