Repository navigation
Compare: v0.6.1...v0.6.2
A health-report fix, and the deployment and CI fixes after the first automatic deploy of v0.6.1.
Fixed
- The detailed health report (
/v1/health?detailed=true) said the Earth Engine service account was not configured on a host that uses default credentials (GEE_USE_DEFAULT_CREDENTIALS); it now reports credentials from either source. - The first automatic deploy after a merge into
masterconfigured the host from its first-boot checkout, where the configure script did not exist, and failed; a branch deploy now checks outorigin/<branch>. Tag deploys were unaffected.
Changed
- The deploy targets a GitHub environment named after the site,
dt4lc.org, instead ofdemo; the workflow is "Deploy dt4lc.org", and the Deployments page links to the site. Sync dev with masterfast-forwardsdevtomasterafter a release whendevhas no commits of its own, with a deploy key that thedevruleset admits (SYNC_DEPLOY_KEY), so the two branches point at the same commit; whendevhas moved on it opens the pull request as before.- The
Release gateadmitsci/*branches with workflow and documentation changes only, likedocs/*(CONTRIBUTING).
Container Images
Both images are published to GitHub Container Registry. Pull with:
docker pull ghcr.io/ipt-mmda/dt4lc/backend:0.6.2
docker pull ghcr.io/ipt-mmda/dt4lc/frontend:0.6.2Run with Docker Compose
The compose file builds the images from source:
git clone --branch v0.6.2 https://github.com/IPT-MMDA/dt4lc.git
cd dt4lc
cp .env.example .env # API keys are optional; without them the bundled Ollama model is used
docker compose --profile ollama up -d # UI at http://localhost, API docs at http://localhost/docs