KoalaGeo

@doublebyte1 that sounds great to me!

If your updating PostGres, and the pygeoapi config for the connection stays the same, could you not run the pygeoapi deployment on a schedule in sync with the postgres updates...

You're correct. If you're adding a new table in postgis then yes the config will need updating. I was assuming the new data would be added to the existing postgis...

Maybe you could stick with the one table, and amend your new data with a "last updated" datetime attribute, then the user could use the api filtering to only pull...

> Yes, we like metadata, on the other hand it may be frustrating for novice users to write a configuration which has a lot of required configuration properties The configs...

Hi @justb4, Thanks for the feedback, I'll take a look & see what I can do

Hi @kalxas & @justb4, I've got the conditions working nicely, `build` runs: ``` on: push: branches: - master paths-ignore: - '**.md' pull_request: branches: - master paths-ignore: - '**.md' release: types:...

DockerHub workflow looks good but I can't test as `geopython/pygeoapi` is hard coded, I'd need to make it `koalageo/pygeoapi` to test then revert 

Changing to my personal namespace worked - https://hub.docker.com/r/koalageo/pygeoapi I've reverted target DockerHub repo to geopython/pygeoapi

@tomkralidis Sorry, Xmas and COVID working it's way through the family. I was thinking from @justb4 review the workflow would build both dockerhub & ghcr, but the docs would refer...