Before you start
- User-owned S3-compatible bucket with private objects and bucket-scoped credentials
- Stable HTTPS origin; seven bounded services with persistent PostgreSQL and Redis
Configuration that needs your attention
Includes the backend, frontend, reverse proxy, combined Celery/export worker and periodic beat scheduler.
Uploaded media lives in the configured customer bucket; short-lived signed URLs are used and public ACL headers are disabled. Configure bucket CORS for your HTTPS origin.
Keep the database, signing keys and bucket recovery policy together. No shared RWX volume or root initializer is required. SMTP remains optional upstream configuration.
Required secrets
Configure these scoped secrets during deployment review in your Hakopod installation. Secret values stay out of the application TOML.
-
database-password -
redis-password -
session-secret -
jwt-secret -
storage-access-key -
storage-secret-key
This preset needs a public site URL. Set the correct origin before starting the application.
Use this preset
- Open the Catalog in your own Hakopod dashboard and select Baserow.
- Choose the project, environment, and application name. Set the required values and secret references.
- Review the generated configuration, resource requests, networking, and storage plan.
- Deploy, then inspect readiness and logs. Configure backups for persistent data before relying on the service.