Philip Graae

That was also how I understood it, that once the first container was running, they basically just did a memcpy to spawn the others.

Since all of the potential gains from multi-threaded access lie in I/O operations, I'm wondering if it would not make more sense to move towards asyncio and async / await,...

Right, GDAL would be the blocker here. Seems very unlikely that they would decide to make an async interface.

I could still see some combination of asyncio and threading that would be beneficial. For example, using an ASGI framework for handling requests, then doing raster access in an external...

>I'm not against async in principle, but in this case the work should start with async raster retrieval, not database accesses. Yes that's also what I'm suggesting, but to wrap...

That is certainly possible and would be a nice feature. It should also only require a change to the preview app itself. Each dataset would just be another leaflet layer.

>Contrast sliders would have to be remodeled (or should the same contrast apply to all layers?) Maybe as a first go it would be alright to have the same contrast...

Sounds good @mccarthyryanc! I suffer from the same JS limitations as @dionhaefner, but I'll gladly help and give advice if needed.

Since we are using SQLAlchemy, I would suggest using Alembic https://alembic.sqlalchemy.org/en/latest/ Alembic is a CLI tool, but they also have a python API, so you can call their migration commands...

I had this error as well and managed to figure it out. the `tryBindPath` function in `/lib/docker.js` assumes that the serverless config file is called `serverless.yml`, in my case it...