Feature
To replace the need for a hosted ODK Central instance for ruODK testing (both local dev and GH actions), it would be nice to run ODK Central in a devcontainer.
This would need to setups: one for local dev (mounting the application code as main service) and one for Gh actions (only running the ODK Central containers).
A working example has been implemented for R package ckanr (which needs a running CKAN instance).
Challenges: Provision SSL certificates for the respective hostname. In the devcontainer, accessing ODK Central via the Codespaces hostname may collide with the Codespaces SSL tunnelling.
References
Run ODK Central on GH Actions, check hostname and get SSL cert:
https://github.com/getodk/central/blob/next/.github/workflows/test.yml
https://github.com/getodk/central/blob/next/test/test-images.sh
Integration R package vs microservices docker compose: https://github.com/ropensci/ckanr/tree/main/.devcontainer
Feature
To replace the need for a hosted ODK Central instance for ruODK testing (both local dev and GH actions), it would be nice to run ODK Central in a devcontainer.
This would need to setups: one for local dev (mounting the application code as main service) and one for Gh actions (only running the ODK Central containers).
A working example has been implemented for R package ckanr (which needs a running CKAN instance).
Challenges: Provision SSL certificates for the respective hostname. In the devcontainer, accessing ODK Central via the Codespaces hostname may collide with the Codespaces SSL tunnelling.
References
Run ODK Central on GH Actions, check hostname and get SSL cert:
https://github.com/getodk/central/blob/next/.github/workflows/test.yml
https://github.com/getodk/central/blob/next/test/test-images.sh
Integration R package vs microservices docker compose: https://github.com/ropensci/ckanr/tree/main/.devcontainer