kosmos/akkounts

1 Fork 0

Docker Compose dev setup: Garage + automated bootstrap #250

Open

raucao wants to merge 5 commits from chore/docker-compose-setup into master

pull from: chore/docker-compose-setup

Author	SHA1	Message	Date
raucao	2093f67a64	Merge pull request 'Allow remote access to dev services' (#253 ) from dev/remote_access into chore/docker-compose-setup CI / Test (pull_request) Successful in 45s Details Reviewed-on: #253	2026-10-06 17:37:49 +00:00
raucao	695977172f	Fix Liquor Cabinet performance in dev CI / Test (pull_request) Failing after 46s Details Can't handle enough requests without ThreadPool, so once you hit the limit, requests take 5s+ (having to wait for the keepalive timeout)	2026-10-06 19:36:26 +02:00
raucao	bc37df52a0	Allow remote access to dev services CI / Test (pull_request) Successful in 46s Details Release Drafter / Update release notes draft (pull_request) Successful in 19s Details	2026-10-06 19:34:24 +02:00
raucao	6279699c11	Switch dev object storage from MinIO to Garage CI / Test (pull_request) Successful in 43s Details MinIO no longer publishes prebuilt community images (quay.io returns 401, Docker Hub 404), so the dev setup cannot pull the image. Use a single-node Garage instance instead, which auto-creates the remotestorage bucket and a dev-key1 access key on first start, and point liquor-cabinet at it.	2026-10-06 13:52:38 +00:00
raucao	0d9c580a0a	Automate first-run LDAP and database setup The documented flow started web (with Solid Queue in Puma) before the databases existed, and required manually creating the 389ds back-end and seeding the LDAP directory and databases. Automate it: - add an ldap-init one-shot service that creates the 389ds back-end if it does not exist - add a web entrypoint that seeds LDAP and the databases on first start, and runs db:prepare on later boots - update README and AGENTS accordingly, including the reset steps	2026-10-06 13:52:38 +00:00