Deployed OpenCloud file-sharing platform at opencloud.basicstack.de with: - Namespace: opencloud - Encrypted hcloud volumes (100Gi PVC) - Pocket ID OIDC integration (opencloud_admins group) - SMTP notifications via opencloud@basicstack.de - All credentials stored as SealedSecrets - Search service excluded due to v7.2.0 bug (GitHub #1740) Configuration follows official docker-compose pattern: - Image: opencloudeu/opencloud-rolling:7.2.0 - Command: opencloud init || true; opencloud server - External IDP mode with auto-provisioning - OC_EXCLUDE_RUN_SERVICES: search Files: - opencloud-deployment.yaml: Main deployment with OIDC, SMTP config - opencloud-configmap.yaml: OpenCloud config (search disabled) - tika-deployment.yaml: Apache Tika for future search enablement Co-Authored-By: Paperclip <noreply@paperclip.ing> |
||
|---|---|---|
| .. | ||
| backup | ||
| bookstack | ||
| directus | ||
| forgejo | ||
| opencloud | ||
| paperclip | ||
| passbolt | ||
| platform-prod | ||
| pocket-id | ||
| stalwart | ||
| README.md | ||
Applications
This directory contains deployment configurations for all applications running on the basicstack.de cluster.
Structure
Each application should have its own subdirectory containing:
- Kubernetes manifests: Deployment, StatefulSet, Service, ConfigMap, Secret definitions
- Helm values: If using Helm charts, include values.yaml files
- Configuration files: Application-specific configs (TOML, JSON, YAML)
- Documentation: README or guide specific to the application deployment
- Patches: Any kubectl patches or modifications needed
Example: Stalwart
The stalwart/ directory serves as a reference implementation, containing:
- Multiple deployment variants (basic, with OIDC, etc.)
- Helm values files
- Monitoring dashboard configurations
- Backup/restore procedures
- Operational documentation
Adding a New Application
- Create a new directory:
apps/<application-name>/ - Add your Kubernetes manifests
- Include a README.md explaining:
- What the application does
- How to deploy it
- Configuration options
- Troubleshooting steps
- Test the deployment in a dev environment
- Commit with a descriptive message
Naming Conventions
- Directory names: lowercase, hyphen-separated (e.g.,
my-app) - Manifest files: descriptive names indicating resource type (e.g.,
deployment.yaml,service.yaml) - Use consistent naming across applications