Files
wild-directory/loomio/notes.md
Paul Payne 4d983819c9 feat(supabase): add services and statefulset for database management
feat(synapse): update ingress to use traefik ingress class and bump version

feat(syncthing-discovery): introduce syncthing discovery service with deployment and ingress

feat(syncthing-relay): add syncthing relay server with deployment and ingress configuration

fix(taiga): update liveness and readiness probes to use tcpSocket for health checks

fix(taiga): change PVC access mode to ReadWriteMany for media and static storage

feat(traefik): add icon and ignore rules for traefik service

docs(ushahidi): add notes for Redis configuration and Laravel startup probe adjustments

feat(ushahidi): implement dedicated Redis deployment for Ushahidi

fix(vllm): update deployment strategy and readiness/liveness probes for improved stability

fix(writefreely): pin writefreely image version to v0.15.1 for consistency

docs(zulip): add notes for TLS-terminating reverse proxy configuration and expected behavior
2026-07-02 21:34:27 +00:00

873 B

Loomio — Notes

Custom startup command must reproduce ENTRYPOINT setup steps

Loomio's Docker image uses docker_start.sh as its ENTRYPOINT, which copies client3-build/public/client3/ before starting Rails. Overriding the entrypoint with a direct Rails command skips this step, leaving client3/ unpopulated and causing 500 errors on all routes serving the SPA.

Fix: reproduce the copy step explicitly in the deployment command::

command: ["/bin/bash", "-c"]
args:
  - |
    set -e
    mkdir -p /loomio/public/client3
    cp -r /loomio/client3-build/* /loomio/public/client3/
    bundle exec rake db:migrate db:seed
    bundle exec thrust puma -C config/puma.rb

General rule: whenever you override command:, inspect the image's ENTRYPOINT/CMD (via docker inspect or the Dockerfile) and reproduce any required setup steps.