Reproducible development environment

[tomalrussell]

Consider dependencies and requirements for the various services:

• raster server: python + terracotta, access to TIFFs and build sqlite db
• vector server: node + tileserver-gl-lite, access to mbtiles
• frontend dev server: node + react etc, access to src, proxy to other endpoints
• backend API server: python, pipenv, connect to database
• database

Separately, snakemake workflow processes tiffs for terracotta and vector data into database then into vector tiles. Current way to run snakemake is to change to backend directory, run pipenv shell to pick up dependencies and database connection environment variables, then change over to etl and run snakemake commands.

Goal: improve ease and reproducibility of initial setup and everyday spinning up for development. See initial sketch with docker-compose for backend API and database. Current state is to open four terminals/tmux screens and run:

• npm start
• npm run raster
• npm run vector
• pipenv run uvicorn backend.app.main:app --host localhost --port 8888 (with database connection details in .env)

[thomas-fred]

There's a stab at this in: feature/containerise, but it's not finished. It still needs the certificates serving appropriately, and some general testing.

[tomalrussell]

Will be closed by feature/containerise-global which builds on feature/containerise