Appearance
Documentation Deployment
The documentation portal is a VitePress static site located in documentation/ and published at https://docs.usecontent.app.
Coolify Static App settings
| Setting | Value |
|---|---|
| Domain | docs.usecontent.app |
| Base Directory | /documentation |
| Install Command | npm ci |
| Build Command | npm run docs:build |
| Publish Directory | /dist |
| Auto Deploy | Triggered by the documentation Coolify webhook from GitHub Actions |
Why no Dockerfile is required
VitePress produces static files after build. Coolify can serve those files directly as a static application, so a separate nginx container would add complexity without improving the deployment model.
The repository workflow triggers a separate Coolify webhook for the documentation resource after a push to master. Coolify then checks out the repository, runs the VitePress build from the documentation directory and publishes the static output.
The main application is served from usecontent.app, while documentation is served independently from docs.usecontent.app.
The documentation resource does not need MongoDB, MinIO, wallet RPC variables or backend secrets. Its deploy can fail or be restarted without recreating the application containers, which makes it safe to update architecture notes frequently during development.
Deployment checklist
- Create a new Coolify Static App from the same GitHub repository.
- Select the branch that should publish documentation.
- Set the root directory to
documentation. - Use
npm cias the install command. - Use
npm run docs:buildas the build command. - Use
distas the publish directory. - Set the public domain to
https://docs.usecontent.app. - Trigger the resource from GitHub Actions through
COOLIFY_DOCS_WEBHOOK_URL.
No additional environment variables are required for this documentation site.