Philip Graae

Adding to this, it would be awesome to have the same kind of version format as in Versioneer: A build 5 commits ahead tag 0.20.0, latest commit being `abcd123` would...

@sl304227-nh Thanks, `poetry-dynamic-versioning` seems somewhat broader in scope than this project, AFAICT it already supports the behavior that I'm looking for, i.e. using the Git tag as the source of...

>An additional model could be to save raster metadata on the rasters themselves. In that case, it would be much less likely for the raster metadata to go out of...

But the DB would still be "managed" by Terracotta, right? As in tc would still provide the tools for setting up a DB, adding keys and so on?

>I'm not sure. I think it would be good to do that for the most common DB usecase(s), but we should also have the option to have databases that are...

> Not sure though in what way the SQLite DB would be easier to use than the filesystem. Ingest == dump the file into an S3 bucket sounds like the...

> Well, the data has to live somewhere? S3 was just an example, could be any filesystem. Right, I'm just thinking out loud, trying to cover every angle from the...

OAuth 2.0 seems to be the standard for APIs that require authentication. Something like this maybe: https://docs.authlib.org/en/latest/flask/2/

I think the easiest and also the most common mechanism, is a session cookie, stored in the database and passed by the user as a query param on every request...

Then the actual mechanism for handing out the session cookie (which I think is a bit more tricky to get right, security-wise) can be totally independent of the given deployment...