What do you mean by "shouldn't this live somewhere remote"? The input data is on S3 and/or Zenodo, but you need to download it and put it in PostgreSQL. You ca

What do you mean by "shouldn't this live somewhere remote"? The input data is on S3 and/or Zenodo, but you need to download it and put it in PostgreSQL. You can't just give arbitrary people remote access to a PostgreSQL database. The rest of what you've described is pretty much the happy path of what I've already got, where one container has the DB and one has the API. There's a complication you're missing because you can't load data into the DB if you're not running the DB container, and also there is apparently no way to script Compose to start the API when the DB is ready. So actually you start the containers first, and the DB container spends a while loading the data and the API spends a few hours saying "I don't have data yet, sorry :(". So even the happy path has this step where you wait for five hours and hope things are working. But most people don't land on the happy path.