You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current setup to maintain and deploy the various services is semi-automated: Ansible is used, but with full GitOps, coupling GitHub, GH Workflows with Ansible, we get several advantages:
as pygeoapi Docker builds are moved to GH Workflows, will be easier to integrate (now HTTP-callback from DockerHub)
any other service like the "Home" page will be automagically deployed on GH push
repo is well-prepared to later move to OSGeo SAC infrastructure
As example of a fully fledged GitOps pygeoapi deployment the Geonovum OGC API Testbed project can serve as example:
The current setup to maintain and deploy the various services is semi-automated: Ansible is used, but with full GitOps, coupling GitHub, GH Workflows with Ansible, we get several advantages:
pygeoapi
Docker builds are moved to GH Workflows, will be easier to integrate (now HTTP-callback from DockerHub)As example of a fully fledged GitOps
pygeoapi
deployment the Geonovum OGC API Testbed project can serve as example:The text was updated successfully, but these errors were encountered: