tarmo

Tarmo - Tampere Mobilemap

• Development
  • Frontend
  • Backend
  • Database migrations
• Data model
• Architecture

Development

0. Install Docker based on your platform's instructions.
1. Create a Python virtual environment and activate it.
2. pip install pip-tools
3. pip-sync requirements-dev.txt
4. pre-commit install

Frontend

Use Node>=v16. See instructions for acquiring an NLS API key (in Finnish). Optionally, see instructions for acquiring a Digitransit API key if you want bus stops on your map.

1. Build and start the development containers with docker-compose -f docker-compose.dev.yml up -d
2. Populate the database by running make test-all-layers.
3. Navigate into the web directory.
4. Copy .env.sample as .env and fill your NLS API key (plus optionally Digitransit API key).
5. Install dependencies:

   yarn

6. Run the development server in localhost:3000:

   yarn run start

Backend

1. Install also main requirements to the same python virtual environment:
   1. pip-sync requirements.txt requirements-dev.txt
   2. pre-commit install
2. Run tests with make pytest
3. Build and start the development containers with docker-compose -f docker-compose.dev.yml up -d
4. Edit the lambda functions and restart the containers with make rebuild to see the changes.

If test using pytest-docker get stuck, you can remove the dangling containers with:

docker ps --format '{{.Names}}' |grep pytest | awk '{print $1}' | xargs -I {} docker stop {}
docker ps --format '{{.Names}}' |grep pytest | awk '{print $1}' | xargs -I {} docker rm {}
docker network ls --format {{.Name}} |grep pytest | awk '{print $1}' | xargs -I {} docker network rm {}

Database migrations

1. Make sure your backend requirements are installed: pip-sync requirements.txt requirements-dev.txt.
2. Add your changes to the model sql.
3. Create a new database revision with make revision name="describe your changes". This creates a new random id (uuid) for your migration, and two things in the alembic versions dir:
   1. New revision file uuid_your_message.py,
   2. New revision sql directory uuid.
4. Add the needed difference SQL (generated e.g. manually or with pgdiff) as upgrade.sql inside the new uuid directory.
5. Add a downgrade.sql that will cancel the upgrade.sql operations in the same directory.
6. Run tests with make pytest to check that your new model.sql, upgrade.sql and downgrade.sql run properly.
7. Run make rebuild and make test-create-db to start development instance with the new model.
8. To update the database documentation to reflect the changes, install tbls and run tbls doc --force.
9. Commit model.sql, the uuid_your_message.py file and uuid directory content, as well as the documentation changes in dbdoc directory, to Github.

Data model

Database documentation

Architecture

Tarmo infra documentation