GitHub template repository for creating new services on the Javabin platform.
| File | Purpose |
|---|---|
app.yaml |
Platform service configuration — compute, routing, resources, auth |
Dockerfile |
Multi-stage build (Java/Temurin by default, adapt for your runtime) |
.github/workflows/deploy.yml |
CI entrypoint — calls javabin.yml reusable workflow |
README.md |
Starter README with getting-started steps |
- Click "Use this template" on GitHub to create a new repo under
javaBin/ - Edit
app.yaml— set your service name, team, compute settings, routing, and any resources - Ensure your team is registered in javaBin/registry (
teams/{name}.yaml) and add the repo to your GitHub team - Push to
main— the platform CI builds, plans, reviews, and deploys automatically
name— service name (required, lowercase + hyphens, max 20 chars)team— owning team, must exist in the registry (required)compute— CPU, memory, port, desired count, health check pathrouting— hostname underjavazone.noand ALB priorityresources— S3 buckets, DynamoDB tables, Secrets Manager secrets, SQS queuesauth— Cognito integration:internal,external,both, ornoneenvironment— custom environment variablesbudget_alert_nok— monthly budget alert threshold in NOK
Full reference: app.yaml reference
The default Dockerfile uses eclipse-temurin:21 for a Java/Maven project. Replace it with your own if you use a different runtime (Node.js, Go, Python, etc.).
This template includes .github/workflows/deploy.yml which calls the platform's reusable workflow javaBin/platform/.github/workflows/javabin.yml@main. No additional workflow config needed.
- javaBin/platform — shared infrastructure and reusable modules
- javaBin/registry — team registration
- javaBin/javabin-cli —
javabin registerautomates team registration