renaming-services
Rename Service Documentation
This skill guides you through renaming a service in the Coolify documentation, ensuring all references are updated correctly.
When to Use This Skill
- Service name changed in the Coolify repository
- Fixing incorrect service naming (e.g., camelCase to kebab-case)
- Consolidating duplicate service documentation
- Correcting typos in service slugs
Critical: Four Locations Must Be Updated
When renaming a service, you MUST update all four locations:
- Documentation file (
docs/services/) - Services list (
docs/.vitepress/theme/components/Services/List.vue) - All services directory (
docs/services/all.md) - Nginx redirects (
nginx/redirects.conf)
More from coollabsio/coolify-docs
adding-documentation-pages
Creates documentation pages for guides, tutorials, knowledge base articles, and troubleshooting content in docs/. Use when adding how-to guides, writing KB articles, creating troubleshooting docs, adding pages to get-started/, applications/, databases/, knowledge-base/, or integrations/. NOT for service pages - use adding-service-documentation for docs/services/.
14adding-service-documentation
Documents new Coolify one-click services by creating markdown pages in docs/services/, downloading logos to docs/public/images/services/, and updating List.vue catalog. Use when adding service documentation, creating service pages, onboarding services from templates/compose/, or updating the services catalog with new entries.
4disabling-services
Hides or disables a service from the documentation listing while preserving the page for SEO and bookmarks. Use when deprecating services, marking services unavailable, adding disabled:true to List.vue, or adding warning callouts to service pages. Keeps docs/services/ pages accessible via direct URL.
3