Create a version of TM with sandboxed OSM for training data generation

[spwoodcock]

What type of PR is this? (check all applicable)

• 🍕 Feature
• 🐛 Bug Fix
• 📝 Documentation
• 🧑‍💻 Refactor
• ✅ Test
• 🤖 Build or CI
• ❓ Other (please specify)

Describe this PR

• I created a demo local setup for using a bundled version of OSM that is sandboxed.
  • We need something like this as part of a TM specifically for generating training data for fAIr.
• It adds a database and OpenStreetMapwebsite/API service to the stack.
• The version of OSM includes a pre-generated user 'admin@hotosm.org' with password 'Password1234'.
• There is also a pre-generated OAuth2 application, with the redirect URI set to that in the tasking-manager.env REDIRECT_URI variable.

Things still to do:

• Instead of creating an OAuth2 App setup and requiring login, we could possibly just generate an access token in the database, then use that as the access_token to hardcoded for iDEditor (in editor.js?).

Alternative Approaches Considered

• Instead of pushing to a sandboxed OSM, we could delete all existing geoms in live OSM (not ideal).
• There is also OSM dev servers we would request access to? https://wiki.openstreetmap.org/wiki/Using_the_dev_server

Testing / Setup

1. First build the OSM container:

cd contrib/tm-training
docker compose build osm

2. Set the REDIRECT_URL correctly in tasking-manager.env:

3. Run all services together:

dc -f docker-compose.yml -f contrib/tm-training/docker-compose.yml up -d

4. Get the generated Client ID and Client Secret:

dc -f docker-compose.yml -f contrib/tm-training/docker-compose.yml logs osm

5. Update the env vars in tasking-manager.env.

6. Restart all services:

dc -f docker-compose.yml -f contrib/tm-training/docker-compose.yml up -d

Extra resources

• OSM docker install: https://github.com/openstreetmap/openstreetmap-website/blob/master/DOCKER.md#initial-setup
• OSM OAuthToken model? https://github.com/openstreetmap/openstreetmap-website/blob/5dc9fb3dc550a7b81ee6df5d6ca97e050798aba9/app/models/oauth_token.rb#L38
• OSM OAuth tests: https://github.com/openstreetmap/openstreetmap-website/blob/5dc9fb3dc550a7b81ee6df5d6ca97e050798aba9/test/integration/oauth2_test.rb#L151 (for inspiration)

Checklist before requesting a review

• 📖 Read the Tasking Manager Contributing Guide: https://github.com/hotosm/tasking-manager/blob/develop/docs/developers/contributing.md
• 📖 Read the HOT Code of Conduct: https://docs.hotosm.org/code-of-conduct
• 👷‍♀️ Create small PRs. In most cases, this will be possible.
• ✅ Provide tests for your changes.
• 📝 Use descriptive commit messages.
• 📗 Update any related documentation and include any relevant screenshots.

[optional] What gif best describes this PR or how it makes you feel?

[sonarcloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud

[ramyaragupathy]

Would this fit the need for end to end mapping testing grounds @spwoodcock @dakotabenjamin ?

[dakotabenjamin]

What is this file?

[dakotabenjamin]

Yes, but from what I understand of the setup as written its not something we would push to production but would rather spin up standalone for a training event for example.

perhaps a task for later but ideally we can specify which osm backend to write to during project creation. For the sandbox, we would probably want to setup some processes for cleaning the database regularly as well.