Graham McIntire
8f87d4bbab
Created build system for minimal Debian 13 (Trixie) image with Erlang/OTP and Elixir runtime pre-installed. This will speed up CI/CD builds by caching the runtime environment. Features: - Multi-stage Dockerfile for minimal final image (~150-200 MB) - Build script with automatic tagging (versioned, latest, dated) - Update script for easy security patch rebuilds - Makefile for common operations - Comprehensive documentation (README + QUICKSTART) Benefits: - Faster CI/CD: Saves 30-60s per build (no apt-get install runtime deps) - Smaller images: Only essential runtime packages included - Security: Easy to rebuild weekly/monthly with latest patches - Consistency: Same runtime across all environments Usage: cd k8s/base-image make build # Build the image make test # Verify it works make push # Push to registry Then update k8s/Dockerfile to use the custom base image. This replaces the previous Dockerfile.base approach with a more comprehensive and maintainable build system. |
||
|---|---|---|
| .. | ||
| base-image | ||
| certificate.yaml | ||
| deployment.yaml | ||
| Dockerfile | ||
| ingressroute.yaml | ||
| kustomization.yaml | ||
| namespace.yaml | ||
| poddisruptionbudget.yaml | ||
| README.md | ||
| service-headless.yaml | ||
| service.yaml | ||
Kubernetes Deployment
Secrets Management
Secrets are managed directly in the cluster and must be created before deploying the application.
Required secrets in the towerops namespace:
gitlab-registry- Docker registry credentials for pulling imagestowerops-secrets- Application secrets (RELEASE_COOKIE, SECRET_KEY_BASE)towerops-db- Database connection credentialstowerops-aws- AWS credentials (AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, AWS_REGION)
For local development, the project root .envrc is used by direnv.
Deployment Timestamp
The application footer displays the deployment timestamp to track when the current version was deployed. This is automatically set by GitLab CI during deployment:
# GitLab CI sets this during deploy
- kubectl set env deployment/towerops DEPLOY_TIMESTAMP=$(date -u +"%Y-%m-%dT%H:%M:%SZ") -n towerops
All pods in the deployment share the same timestamp (when the deployment was initiated), regardless of when individual pods were created. This is displayed in the footer as "Last deployed X ago · YYYY-MM-DD HH:MM:SS UTC".
For manual deployments without GitLab CI, set the timestamp:
kubectl set env deployment/towerops DEPLOY_TIMESTAMP=$(date -u +"%Y-%m-%dT%H:%M:%SZ") -n towerops
Deploying
Apply all resources using kustomize:
kubectl apply -k k8s/
Or individually:
kubectl apply -f k8s/namespace.yaml
kubectl apply -f k8s/secret.yaml
kubectl apply -f k8s/deployment.yaml
kubectl apply -f k8s/service.yaml
kubectl apply -f k8s/service-headless.yaml
kubectl apply -f k8s/certificate.yaml
kubectl apply -f k8s/ingressroute.yaml