ericrisco/rsc-harness / skills/coolify
coolify
FlaggedUse when self-hosting apps and databases with Coolify on a VPS you own — install, first-admin lockdown, Git-to-deploy (Nixpacks/Dockerfile/compose), managed Postgres/Redis, scheduled S3 backups, domains + auto-SSL. NOT a PaaS someone else runs (that is `railway`), NOT sizing/hardening the box (that is `hetzner`), NOT authoring Dockerfiles (that is `docker`).
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 13.1 KB |
| evals/README.md | markdown | 1.5 KB |
| evals/cases.yaml | config | 4.1 KB |
| references/databases-and-backups.md | markdown | 4.5 KB |
| references/deploy-recipes.md | markdown | 4.7 KB |
| references/install-and-proxy.md | markdown | 4.4 KB |
| scripts/verify.shexecutable | script | 5.2 KB |
references/databases-and-backups.md
View on GitHub# Managed databases & backups — deep dive
Source facts: coolify.io/docs/databases/backups and database docs, accessed 2026-06-02.
Coolify provisions Postgres, MySQL, MariaDB, MongoDB, Redis (and more) in-product with generated
credentials. This skill provisions and backs up; SQL/schema/tuning is the `postgresdb` skill; backup
strategy/RPO/RTO doctrine across systems is the `backups` skill. Here we wire the concrete in-product job.
## Connection wiring
Each managed database gets an **internal Docker network hostname** (the service name Coolify assigns).
Connect apps to it over that private hostname — never a public IP.
```text
# GOOD — app env var points at the internal hostname on the private network:
DATABASE_URL=postgres://<user>:<password>@<internal-db-hostname>:5432/<db>
# Inject <password> as a Coolify secret, not a committed literal.
```
Do **not** enable the database's "public port" toggle unless an external client genuinely needs it. An
open 5432/3306/27017/6379 is scanned within minutes. If you must expose it, bind deliberately and firewall
to known source IPs at the cloud layer.
**Every database service needs a named volume.** Recreating a service with only an anonymous volume wipes
the data — the most common Coolify data-loss incident. Coolify's managed DBs set this up; verify it before
trusting the instance with real data.
## Scheduled backups
Coolify runs the engine's native dump on a cron expression, stores it locally, and optionally pushes to
S3-compatible storage.
| Engine | Dump command Coolify runs | Restore = |
| --- | --- | --- |
| PostgreSQL | `pg_dump` | download → decompress → `psql`/`pg_restore` replay |
| MySQL / MariaDB | `mysqldump` | download → decompress → `mysql <` replay |
| MongoDB | `mongodump` | download → `mongorestore` |
Configure per database:
1. **Enable scheduled backup** on the resource.
2. **Cron schedule** — e.g. `0 3 * * *` nightly 03:00; `0 */6 * * *` every 6h. Match to your tolerable
data loss (RPO).
3. **Retention** — keep N copies/days so storage doesn't grow unbounded.
4. **Destination** — local only, or local + an S3-compatible target (below).
## S3-compatible destinations
Add these as Coolify storage destinations. Provide endpoint + region + bucket + access key/secret — always
as Coolify secrets, never in a committed file.
| Provider | Endpoint shape | Notes |
| --- | --- | --- |
| AWS S3 | `s3.<region>.amazonaws.com` | Standard region + bucket |
| Cloudflare R2 | `https://<accountid>.r2.cloudflarestorage.com` | Region usually `auto`; zero egress fees |
| Backblaze B2 | `https://s3.<region>.backblazeb2.com` | S3-compatible endpoint, cheap storage |
| MinIO (self-hosted) | `https://minio.example.com` | Your own object store; force path-style if needed |
| Wasabi | `https://s3.<region>.wasabisys.com` | Flat-rate storage |
Off-box storage is the entire point: a dump sitting on the same disk as the database dies with the disk.
## The restore runbook — run it before you need it
A backup you have never restored is a guess. Do this once now, and on a recurring drill.
```bash
# 1. Pull the latest dump from the destination (UI download, or via the S3 client).
# e.g. from R2/B2/MinIO/S3 with the AWS CLI pointed at the endpoint:
aws --endpoint-url "$S3_ENDPOINT" s3 cp "s3://$BUCKET/<path>/dump.sql.gz" ./dump.sql.gz
# 2. Decompress.
gunzip dump.sql.gz
# 3. Replay into a THROWAWAY database (never the live one during a drill).
# Postgres:
psql "postgres://user:pass@host:5432/restore_test" < dump.sql
# MySQL/MariaDB:
mysql -h host -u user -p restore_test < dump.sql
# MongoDB (from a mongodump archive/dir):
mongorestore --uri "mongodb://user:pass@host:27017/restore_test" ./dump
# 4. VERIFY: compare row counts / key tables against production expectations.
# e.g. Postgres:
psql "postgres://.../restore_test" -c "SELECT count(*) FROM orders;"
# 5. Drop the throwaway DB. Record the drill date in 02-DOCS/wiki/stack/coolify.md.
```
## Consistency caveats
- These dumps are **logical, point-in-time snapshots at dump start**, not continuous PITR. Between dumps,
writes are unprotected — size the cron to your RPO.
- For true point-in-time recovery (WAL archiving / continuous replication) you need engine-level setup
beyond Coolify's scheduled dump — that is `postgresdb` / `backups` territory.
- For a large/active database, a logical dump can take time and add load; schedule it off-peak and watch
that the dump window doesn't overlap the next one.
- Test restores against the **same major engine version**; cross-version replays can fail or silently
change behavior.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |