michtio/craftcms-claude-skills / skills/craft-fortrabbit
craft-fortrabbit
Verifiedfortrabbit (fortrabbit.com) — managed PHP hosting with a Craft CMS software template. Covers git push-to-deploy through the fortrabbit GitHub App, the build and post-deploy commands of the Craft template (migrate/all, project-config/apply, clear-caches/all), the merge deployment strategy with the /config/project replace pattern, the deploy file (.fortrabbit/deploy.yml) and its replace-by-default trap, the CRAFT_* ENV vars mapped from FORTRABBIT_DB_* platform variables, production settings (dev mode, admin changes, updates off), the persistent storage for asset volumes and rsync sync, MySQL over SSH and an SSH tunnel, the Craft queue and image transforms in a worker job, crons, platform limits (no root, no sendmail, heavy binaries in jobs only), and DDEV local development.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 10.9 KB |
| references/asset-storage.md | markdown | 4.2 KB |
| references/database.md | markdown | 4.3 KB |
| references/deploy-and-environments.md | markdown | 11.9 KB |
| references/limitations.md | markdown | 6.0 KB |
| references/local-dev.md | markdown | 3.3 KB |
references/local-dev.md
View on GitHub# Local Development for fortrabbit Projects
fortrabbit has no first-party local environment and no `ddev pull` provider. DDEV is the common local stack for Craft on fortrabbit; set it up the normal way (see the `ddev` skill). Database and assets come down over SSH: `mysqldump` and `rsync`.
Local is where code, schema and plugin changes happen. They reach fortrabbit with a git push. Content flows the other way: production → local.
## Documentation
- DDEV on fortrabbit: https://docs.fortrabbit.com/integrations/local-development/ddev
- Craft install: https://docs.fortrabbit.com/guides/craft-cms/install
- Craft ENV vars: https://docs.fortrabbit.com/guides/craft-cms/env-vars
- Craft multi-environment config: https://craftcms.com/docs/5.x/configure.html
## DDEV setup
```sh
ddev config --project-type=craftcms --docroot=web --database=mysql:8.0
ddev start
```
fortrabbit runs MySQL 8: use MySQL locally, not DDEV's MariaDB default, so dumps import cleanly in both directions. Match the PHP version to the environment's PHP version in the dashboard (`--php-version`, or `php_version` in `.ddev/config.yaml`).
SSH from inside the container (for `ddev exec rsync` or Composer over SSH) needs the local keys:
```sh
ddev auth ssh
```
## Local `.env`
The environment's ENV vars come from the dashboard; locally Craft reads `.env`. The keys match, so the same config files work in both places:
```sh
CRAFT_ENVIRONMENT=dev
CRAFT_DEV_MODE=true
CRAFT_ALLOW_ADMIN_CHANGES=true
CRAFT_ALLOW_UPDATES=true
CRAFT_SECURITY_KEY=… # same value as on fortrabbit when the database moves between them
PRIMARY_SITE_URL=https://my-project.ddev.site
```
`CRAFT_ENVIRONMENT` on fortrabbit holds the environment name, e.g. `production` or `staging`. Multi-environment config in `config/general.php` can key off it, see Craft's configuration docs.
## Pull production down
Database (see `database.md` for push and the tunnel):
```sh
ssh <env>@ssh.<region>.frbit.app \
'mysqldump --single-transaction --set-gtid-purged=OFF --no-tablespaces "$FORTRABBIT_DB_NAME"' \
| gzip > /tmp/<env>.sql.gz
ddev import-db --file=/tmp/<env>.sql.gz
ddev craft clear-caches/all
```
Assets (see `asset-storage.md`):
```sh
rsync -avz <env>@ssh.<region>.frbit.app:web/uploads/ ./web/uploads/
```
Both overwrite local data. Pulled dumps hold customer data: keep them outside the repo.
## Push up
Code, `composer.lock` and `config/project` go up with `git push`. Pushing the database or assets up is the exception (first launch, a migration): see `database.md` and `asset-storage.md`, and back up the environment first.
## Common Pitfalls
1. **MariaDB locally, MySQL on fortrabbit** — dumps carry engine-specific syntax and collations. Use MySQL in DDEV.
2. **Different PHP versions** — Composer resolves packages locally that fail in the build. Match `php_version` to the environment, or set `config.platform.php` in `composer.json`.
3. **Different security keys** — a database pulled down can't decrypt stored values. Use one `CRAFT_SECURITY_KEY` for local and the environments that share data.
4. **Editing schema on staging to "test it there"** — `CRAFT_ALLOW_ADMIN_CHANGES=false` blocks it. Make the change locally, push, let the post-deploy commands apply it.
5. **SSH keys missing in the container** — `Permission denied (publickey)` from `ddev exec`. Run `ddev auth ssh`.
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 |