A curated collection of Docker Compose files and documentation for use with Coolify.io - the open-source & self-hosted Heroku/Netlify alternative.
This repository serves multiple purposes:
- Archive default Coolify one-click service configurations
- Provide custom compose files optimized for Coolify
- Share documentation and guides for common deployment patterns
- Maintain scripts and tools for Coolify management
.
├── coolify-defaults/ # Official Coolify one-click configurations
├── custom/ # Custom compose configurations
├── docs/ # Guides and documentation
│ ├── databases/ # Database setup guides
│ ├── deployment/ # Deployment patterns
│ └── examples/ # Example configurations
└── scripts/ # Helper scripts and tools
- A running Coolify instance
- Basic understanding of Docker Compose
- Familiarity with Coolify's UI and concepts
- Choose a compose file from either
coolify-defaults/
orcustom/
- Create a new service in Coolify using "Docker Compose" as the source
- Paste the compose configuration
- Configure environment variables through Coolify's UI
- Deploy!
Each compose file should include:
- Header documentation with links, slogan, tags, and exposed ports
- Required Coolify labels for service management
- Proper service dependencies and healthchecks
- Volume configurations for persistent data
Coolify uses specific patterns for environment variables:
${SERVICE_FQDN_NAME_PORT}
- Service URLs and ports${SERVICE_PASSWORD_NAME}
- Standard passwords${SERVICE_PASSWORD_64_NAME}
- High-entropy passwords/secrets${SERVICE_USER_NAME}
- Service usernames${SERVICE_SETTING_NAME}
- API keys and settings${SERVICE_BASE64_NAME}
- Base64 encoded values${SERVICE_REALBASE64_NAME}
- True base64 encoded values
All services should include standardized healthchecks:
healthcheck:
test: ['CMD', 'command', 'args']
interval: 5s
timeout: 10s
retries: 3
- Never commit sensitive data
- Use Coolify's variable management
- Follow least privilege principles
- Implement proper service isolation
- Use secure defaults
- Optimized for Coolify's UI components
- Database backup integration
- Service-specific configuration fields
- Environment variable management
- Health check implementations
Contributions are welcome! Please read our Contributing Guide for details on:
- Code of Conduct
- Submission process
- Compose file standards
- Documentation guidelines
- Never commit sensitive data or secrets
- Use Coolify's UI for managing sensitive environment variables
- Follow security best practices in compose configurations
This project is licensed under the MIT License - see the LICENSE file for details.