#16124: Docs: rewrite Coolify guide for native one-click service

### Hola :wave: I'm Frank. I host my openclaw on coolify. Some days ago with the latest version they support now one click hosting. I upgraded to their way of doing things and works sweet. It maintained by the offical coolify team, which makes it quite neat. #### Notes Personally I use openclaw via Campfire and there i need to hack it a bit around, but thats a nichi niche case. And if I tried it myself f.e. with telegram. Just works. Nice. Also the terminal access via the coolify terminal works nicely to run some openclaw commands, which previously bothered me, because I didn't set some stuff in my own written compose file correctly. Coolify team knows their system, thats why on the one click hosting it just works. The solution was also elegeant. Anyways. It works. Can reccomend to merge it. It is a blessing for all of our selfhosting dudes out there. Another cool addition would to also include our Dokploy people into the docs but thats a diffrent pr. The Hetzner guide is nice, but hosting one app on a hetzner server is for the most devs, a waste of ressources. I have 50 apps hosted on a single hetzner server (16 euro/month). Tiny utility apps for my clients (nothing huge obviously). I also builted a coolify skill and other skills which componds into a protoyper agent, so clients can built their own apps if they have a quick idea. Feedback is great so far. All I wanted to say is I use it, it gets liked, coolify community supports it natively, the pr is just a wrapper around the offical docs and so way easier to find. If my campfire pr #7883 also gets included, I will revisted this pr and maybe add a tiny section for people who might want to have their own selfhosted chat instance as well. Security wise its gold. **Best regards,** Frank --- ### AI PR Text #### Summary Coolify now includes OpenClaw as a [native one-click service](https://coolify.io/docs/services/openclaw). This rewrites the Coolify deployment guide to match the streamlined setup, removing all manual workarounds that are no longer needed. Supersedes #10464. #### Pages Updated - `docs/install/coolify.md` — complete rewrite #### Before/After **Before:** Manual Dockerfile build pack setup with 7 steps including volume permission chown hack, manual LAN binding config, manual device approval via CLI. **After:** 4-step deploy (select one-click service → set domain → add API key → deploy), with sections for auto-generated auth, env var provider config, browser automation, and channels. #### Removed (handled by native integration) - Manual repo clone + Dockerfile build pack setup - `DOCKER_BUILDKIT` env var - Volume permission chown hack - Manual LAN binding config creation - Manual device approval flow #### Formatting `pnpm format` ✅ #### Codebase and GitHub Search - Checked existing install docs (fly.md, hetzner.md, docker.md) for style conventions - Verified docs.json already has `install/coolify` entry from #10464 lobster-biscuit **Sign-Off** - Submitter effort: low (rewrite based on upstream Coolify docs) <!-- greptile_comment --> <h2>Greptile Overview</h2> <h3>Greptile Summary</h3> Complete rewrite of the Coolify deployment guide to reflect Coolify's native one-click OpenClaw service. Replaces the previous 7-step manual Dockerfile-based setup with a streamlined 4-step process (select service, set domain, add API key, deploy). Adds sections on auto-generated auth credentials, AI provider env var configuration, subscription-based CLI auth, browser configuration, channels, and troubleshooting. - **Missing `docs.json` entry**: The PR description claims `install/coolify` is already in `docs.json` from #10464, but the "Hosting and deployment" navigation group does not include it. The page will exist on disk but won't appear in the Mintlify docs sidebar. An `"install/coolify"` entry should be added to the `pages` array in the "Hosting and deployment" group (and the zh-CN equivalent if a translation is planned). - **Broken link**: The troubleshooting section links to `/gateway/configuration#trusted-proxies`, but that anchor doesn't exist on that page. The trusted proxies documentation is at `/gateway/security#reverse-proxy-configuration`. - Content is well-structured and follows existing install doc conventions (frontmatter, headings, tables for env vars, troubleshooting section). <h3>Confidence Score: 3/5</h3> - Documentation-only PR with minor issues that should be addressed before merge - This is a docs-only change with no code impact, but has two issues: (1) the page is not reachable from the Mintlify navigation because docs.json is missing the entry, and (2) a troubleshooting link points to a non-existent anchor. Both are straightforward to fix. - docs/install/coolify.md has a broken internal link; docs.json needs an install/coolify entry added to the navigation _{Last reviewed commit: e3c8d5a} <!-- greptile_comment --> <h3>Greptile Summary</h3> Complete rewrite of the Coolify deployment guide (`docs/install/coolify.md`) to reflect Coolify's native one-click OpenClaw service. Replaces the previous manual Dockerfile-based 7-step setup with a streamlined 4-step process (select service → set domain → add API key → deploy). Adds sections on auto-generated auth credentials, AI provider env var configuration, subscription-based CLI auth, browser configuration, channels, and troubleshooting. - `docs.json` correctly adds navigation entries for both English and zh-CN, plus a `/coolify` → `/install/coolify` redirect - Content is well-structured and follows conventions of existing install docs (`fly.md`, `hetzner.md`) - Internal links (`/providers`, `/channels`, `/gateway/security#reverse-proxy-configuration`) are all valid - Env vars like `AUTH_USERNAME`, `AUTH_PASSWORD`, and `OPENCLAW_PRIMARY_MODEL` are not native to OpenClaw but are expected to be defined by Coolify's one-click service template, which handles the mapping <h3>Confidence Score: 4/5</h3> - This is a documentation-only PR with no code changes; safe to merge. - Docs-only change that is well-structured, follows existing conventions, and has valid internal links. The previous review's concerns about missing docs.json entries and broken links were both incorrect — the PR correctly adds navigation entries and the troubleshooting link resolves to a valid heading. No issues found. - No files require special attention. _{Last reviewed commit: e3c8d5a} <!-- greptile_other_comments_section --> <!-- /greptile_comment -->