{
  "source": "https://coolify.io/docs/llms.txt",
  "fetched_at": "2026-09-14T14:33:40.973Z",
  "etag": "\"6aa7a22f-1d433\"",
  "last_modified": "Mon, 14 Sep 2026 07:28:47 GMT",
  "entries": 845,
  "text": "# Docs\n\n- [Home](/): Welcome to Coolify Documentation\n\n- **Get Started**\n- [Choose your path](/choose-your-path): Decide between self-hosted Coolify and Coolify Cloud based on your goals, responsibilities, and operational comfort level.\n- [Start with Self-hosted](/start-with-self-hosted): Install and run self-hosted Coolify with a clear path for automated or manual setup.\n- [Start with Coolify Cloud](/start-with-cloud): Start with Coolify Cloud using your own servers while the Coolify team manages the Coolify instance for you.\n- [Deploy your first app](/deploy-your-first-app): Deploy your first application on Coolify using the Docker Image option with a simple nginx example.\n- [Deploy your first database](/deploy-your-first-database): Deploy your first Redis database on Coolify using the one-click resources list and test the connection from terminal.\n- [Deploy your first service](/deploy-your-first-service): Deploy your first one-click service on Coolify using Umami and sign in to verify it is running.\n\n- **Resources**\n- [Product UI](/screenshots)\n- [Sponsors](/sponsors): Meet the companies and organizations sponsoring Coolify development including hosting, infrastructure, and developer-tool partners.\n- [Offers](/offers): Offers, credits, and partner resources for Coolify users.\n- [Support](/support): Find the right place to ask for Coolify help and what to include so people can help faster.\n- [Team](/team): Meet the international team developing Coolify including founder Andras Bacsai, core developers, community leads, and documentation maintainers.\n\n- **Contribute**\n- [Guidelines](/contribute/guidelines)\n- [Coolify Core](/contribute/coolify)\n- [Documentation](/contribute/documentation)\n- [Service Templates](/contribute/service)\n- Core\n\n  - **Understand Coolify**\n  - [What is Coolify](/core/what-is-coolify): A practical introduction to Coolify for people new to self-hosting.\n  - [How Coolify works](/core/how-coolify-works): How the Coolify instance, connected servers, Docker, and reverse proxies work together.\n  - [Self Hosted vs Coolify Cloud](/core/selfhosted-cloud-comparison): Compare self-hosted Coolify and Coolify Cloud by ownership, responsibilities, and cost.\n  - [Build and Deployment Model](/core/build-deployment-model): How Coolify builds or pulls application images and replaces running containers on connected servers.\n  - [Docker and Containers](/core/docker-and-containers): How Docker images, containers, persistent storage, networks, and Compose fit into a Coolify deployment.\n  - [Networking in Coolify](/core/networking-in-coolify): How public traffic, reverse proxies, Docker networks, and direct ports fit together in Coolify.\n  - [Security Model](/core/security-model): Understand Coolify's security boundary, built-in controls, and the infrastructure and workloads you must secure.\n\n  - **Manage Coolify**\n  - Instance Management\n    - [Instance settings](/core/instance-management/instance-settings): Configure self-hosted Coolify instance settings for URL, access, updates, backups, email, OAuth, and scheduled jobs.\n    - [Update Coolify](/core/instance-management/update): Update a self-hosted Coolify instance from the dashboard or terminal, and configure automatic updates.\n    - [Update Coolify Database](/core/instance-management/update-coolify-database): Update or roll back the internal PostgreSQL database used by a self-hosted Coolify instance.\n    - [Downgrade Coolify](/core/instance-management/downgrade): Return a self-hosted Coolify instance to an earlier release from the terminal, with backup and recovery safeguards.\n    - [Uninstall Coolify](/core/instance-management/uninstallation): Permanently remove a self-hosted Coolify control plane and its local data from a server.\n  - Backup and Recovery\n    - [Back up Coolify](/core/backup-and-recovery/instance-backup): Create and verify self-hosted Coolify instance backups, save the instance encryption key, and configure recurring backups.\n    - [Restore Coolify](/core/backup-and-recovery/instance-restore): Restore a self-hosted Coolify instance on the same machine or move it to a replacement machine.\n    - [Reset Root Password](/core/backup-and-recovery/reset-root-password): Recover access to a self-hosted Coolify instance by resetting the root account password from the server terminal.\n    - [Change Root Email](/core/backup-and-recovery/change-root-email): Recover access to a self-hosted Coolify instance by changing the root account login email from the server terminal.\n    - [Reset 2FA](/core/backup-and-recovery/reset-2fa): Recover access to a self-hosted Coolify account by clearing its two-factor authentication setup from the server terminal.\n\n  - **Persistent Storage**\n  - Storage mounts\n    - [Overview](/core/persistent-storage/storage-mounts/overview): Understand how persistent storage keeps application and database data outside replaceable containers and choose the correct mount type in Coolify.\n    - [Volume mounts](/core/persistent-storage/storage-mounts/volume-mounts): Add a named Docker volume to a Coolify application or database and verify that its data survives redeployments.\n    - [Bind mounts](/core/persistent-storage/storage-mounts/bind-mounts): Map a specific directory on a Coolify deployment server into an application or database container.\n    - [File mounts](/core/persistent-storage/storage-mounts/file-mounts): Mount one Coolify-managed file or an existing host file at an exact path inside a container.\n    - [Backup](/core/persistent-storage/storage-mounts/backups): Schedule local and S3 backups for application volume and directory mounts, set retention, and verify each execution.\n  - S3 Storage\n    - [Overview](/core/s3-storage/overview): Configure S3-compatible storage for Coolify backups with Amazon S3, Cloudflare R2, Supabase Storage, and other supported providers.\n    - [Amazon S3](/core/s3-storage/aws): Connect Amazon S3 to Coolify by creating a bucket, IAM policy, IAM user, and access key.\n    - [Cloudflare R2](/core/s3-storage/r2): Configure Cloudflare R2 S3-compatible storage for Coolify backups with bucket creation, API token setup, and access credentials.\n    - [Supabase Storage](/core/s3-storage/supabase): Configure Supabase Storage as an S3-compatible backup destination using your project endpoint, bucket, region, and access keys.\n\n  - **Infrastructure**\n  - Servers\n    - [Overview](/core/infrastructure/servers/overview): Understand server roles in Coolify and choose the right way to add, provision, and manage a server.\n    - [Add Server](/core/infrastructure/servers/add-server): Connect an existing Linux server to Coolify with SSH and prepare it for deployments.\n    - [Provision Cloud Server](/core/infrastructure/servers/provision-cloud-server): Purchase and create a Hetzner, DigitalOcean, or Vultr server from the Coolify dashboard.\n    - [Manage Server](/core/infrastructure/servers/manage-server): Update a connected server's connection, domain, timezone, build role, and cloud-provider link.\n    - [Remove Server](/core/infrastructure/servers/remove-server): Remove a server from Coolify, optionally delete its resources, and understand provider deletion.\n    - [OpenSSH](/core/infrastructure/servers/openssh): Configure OpenSSH for the localhost server or a remote server connected to Coolify.\n    - [Firewall](/core/infrastructure/servers/firewall): Open the firewall ports required by Coolify, its proxy, connected servers, and dashboard features.\n    - [Non-root User](/core/infrastructure/servers/non-root-user): Create a non-root SSH user and give it the access Coolify needs to manage a server.\n    - [Build Servers](/core/infrastructure/servers/build-servers): Add a dedicated build server and configure an application to use it for Docker image builds.\n    - [Server Patching](/core/infrastructure/servers/server-patching): Check for operating-system package updates and install selected updates from the Coolify dashboard.\n    - [Automated Docker Cleanup](/core/infrastructure/servers/automated-docker-cleanup): Configure scheduled Docker cleanup and safely remove unused images, volumes, and networks from a server.\n    - [Web Terminal](/core/infrastructure/servers/web-terminal): Open a browser terminal for a server or container and enable or disable terminal access for a server.\n  - Scaling\n    - [Overview](/core/infrastructure/scaling/overview): Understand the scaling options available for applications deployed with Coolify and choose when to add servers or a cloud load balancer.\n    - [Multi-server Deployments](/core/infrastructure/scaling/multi-server-deployments): Deploy one Coolify application to multiple standalone servers by using a shared Docker image and registry.\n    - [Cloud Load Balancing](/core/infrastructure/scaling/cloud-load-balancing): Put a provider-managed load balancer in front of an application deployed by Coolify to multiple servers.\n    - [Docker Swarm (Deprecated)](/core/infrastructure/scaling/docker-swarm): Understand the Docker Swarm deprecation in Coolify and the requirements for maintaining an existing Coolify v4 deployment.\n\n  - **Networking**\n  - Destinations\n    - [Overview](/core/networking/destinations/overview): Understand how Coolify uses Docker network destinations to deploy resources on your servers.\n    - [Create a Destination](/core/networking/destinations/create): Create another Docker network destination in Coolify or scan a network that already exists on a server.\n    - [Manage Destinations](/core/networking/destinations/manage): Review resources, rename destinations, select deployment networks, and clone resources to another destination.\n    - [Delete Destination](/core/networking/destinations/delete): Safely remove a destination and its Docker network after reviewing every attached resource.\n  - [Domains](/core/networking/domains): Configure domains, HTTPS, target ports, paths, redirects, search engine indexing, and generated domains for Coolify applications and services.\n  - [DNS](/core/networking/dns): Point domains to Coolify servers, verify DNS records, and configure wildcard domains and DNS validation.\n  - Proxy\n    - [Overview](/core/networking/proxy/overview)\n    - Traefik\n      - [Overview](/core/networking/proxy/traefik/overview)\n      - [Basic Authentication](/core/networking/proxy/traefik/basic-auth): Protect Coolify applications and Docker Compose services with Traefik HTTP basic authentication.\n      - [Custom SSL Certificates](/core/networking/proxy/traefik/custom-ssl-certs): Load certificates from a Coolify server into Traefik with dynamic configuration.\n      - [Dashboard](/core/networking/proxy/traefik/dashboard): Expose the Traefik dashboard through a dedicated authenticated domain in Coolify.\n      - [Custom Middlewares](/core/networking/proxy/traefik/custom-middlewares): Add reusable Traefik request middleware and redirects to Coolify resources.\n      - [Dynamic Configuration](/core/networking/proxy/traefik/dynamic-config): Add file-based Traefik routers, services, middleware, and TLS settings through Coolify.\n      - [Load Balancing](/core/networking/proxy/traefik/load-balancing): Route one Traefik domain to multiple reachable upstream servers or containers.\n      - [DNS Challenge](/core/networking/proxy/traefik/dns-challenge): Configure Traefik to obtain Let's Encrypt certificates through a DNS provider API.\n      - [Wildcard Certificates](/core/networking/proxy/traefik/wildcard-certs): Request and use a Traefik certificate that covers an apex domain and its subdomains.\n      - [Protect with Authentik](/core/networking/proxy/traefik/protect-services-with-authentik): Add Authentik forward authentication to Coolify resources through Traefik middleware.\n    - Caddy\n      - [Overview](/core/networking/proxy/caddy/overview)\n      - [Basic Authentication](/core/networking/proxy/caddy/basic-auth): Protect Coolify applications with Caddy HTTP basic authentication.\n      - [DNS Challenge](/core/networking/proxy/caddy/dns-challenge): Build Caddy with a DNS provider module and use DNS-based ACME validation in Coolify.\n\n  - **Team Management**\n  - Members\n    - [Overview](/core/team/members/overview): Understand how team membership controls access to team-scoped resources and choose the right member management task.\n    - [Add a Member](/core/team/members/add-a-member): Invite a person to a Coolify team by email or with a generated invitation link.\n    - [Remove a Member](/core/team/members/remove-a-member): Remove a person from a Coolify team without deleting their account or the team's resources.\n    - [Delete a User](/core/team/members/delete-user): Delete a user account from a self-hosted Coolify instance, with automatic team ownership transfer and resource cleanup rules.\n    - [Manage Members](/core/team/members/manage-members): Review a Coolify team, change member roles, and manage pending invitations.\n  - [Roles & Permissions](/core/team/roles-and-permissions): Compare Owner, Admin, and Member access across team management, resources, servers, credentials, and API tokens.\n  - [Shared Variables](/core/team/shared-variables): Create team, project, environment, and server-scoped values and reference them in Coolify resource configuration.\n\n  - **Security**\n  - Authentication\n    - OAuth\n      - [Overview](/core/security/authentication/oauth/overview): Understand OAuth sign-in behavior in Coolify and choose a provider-specific setup guide.\n      - [GitHub](/core/security/authentication/oauth/github): Configure GitHub OAuth sign-in for Coolify by creating an OAuth App and registering the Coolify callback URL.\n      - [GitLab](/core/security/authentication/oauth/gitlab): Configure GitLab.com or self-managed GitLab OAuth sign-in for Coolify with a read-user application.\n      - [Google](/core/security/authentication/oauth/google): Configure Google OAuth sign-in for Coolify with a web OAuth client and the Coolify callback URL.\n      - [Azure](/core/security/authentication/oauth/azure): Configure Microsoft Entra ID OAuth sign-in for Coolify with an app registration, tenant ID, and client secret.\n      - [Bitbucket](/core/security/authentication/oauth/bitbucket): Configure Bitbucket Cloud OAuth sign-in for Coolify with an OAuth consumer and email permission.\n      - [Discord](/core/security/authentication/oauth/discord): Configure Discord OAuth sign-in for Coolify with a Discord application and registered redirect URI.\n      - [Infomaniak](/core/security/authentication/oauth/infomaniak): Configure Infomaniak OAuth sign-in for Coolify with an Application credential and callback URL.\n    - SSO\n      - [Overview](/core/security/authentication/sso/overview): Configure centralized Coolify sign-in with Authentik, Clerk, or Zitadel.\n      - [Authentik](/core/security/authentication/sso/authentik): Configure Authentik SSO for Coolify with an OAuth2/OpenID Connect provider, application, and base URL.\n      - [Clerk](/core/security/authentication/sso/clerk): Configure Clerk SSO for Coolify by creating a Clerk OAuth application and using its Frontend API URL.\n      - [Zitadel](/core/security/authentication/sso/zitadel): Configure Zitadel SSO for Coolify with a confidential web application, client secret, and instance base URL.\n    - [2FA](/core/security/authentication/2fa): Configure two-factor authentication, save recovery codes, and manage 2FA for a Coolify account.\n  - Credentials\n    - [SSH Keys](/core/security/credentials/ssh-keys): Create, authorize, rotate, and remove the SSH keys Coolify uses for servers and private Git repositories.\n    - [Cloud Tokens](/core/security/credentials/cloud-tokens): Create and manage the Hetzner, DigitalOcean, and Vultr credentials Coolify uses for cloud servers.\n    - [Cloud-Init Scripts](/core/security/credentials/cloud-init-scripts): Create reusable cloud-init YAML for Hetzner, DigitalOcean, and Vultr server provisioning.\n    - [API Tokens](/core/security/credentials/api-tokens): Create, scope, store, rotate, and revoke Coolify API tokens for integrations and automation.\n\n  - **Observability**\n  - Monitoring\n    - [Overview](/core/observability/monitoring/overview): Understand how Coolify monitors server availability, container state, disk usage, backups, and CPU and memory metrics.\n    - [Sentinel](/core/observability/monitoring/sentinel): Configure and troubleshoot Coolify Sentinel for server health, container status, disk usage, and metrics collection.\n    - [Metrics](/core/observability/monitoring/metrics): Enable and view Coolify CPU and memory metrics for servers, applications, and standalone databases.\n  - Log Drains\n    - [Overview](/core/observability/log-drains/overview): Understand how Coolify forwards application, database, and service container logs to an external destination.\n    - [Axiom](/core/observability/log-drains/axiom): Send Coolify application, database, and service container logs to an Axiom dataset.\n    - [New Relic](/core/observability/log-drains/new-relic): Send Coolify application, database, and service container logs to New Relic Logs.\n    - [Custom Fluent Bit](/core/observability/log-drains/custom-fluent-bit): Configure Coolify to forward resource container logs with a complete custom Fluent Bit configuration.\n\n  - **Notifications**\n  - [Overview](/core/notifications/overview): Understand how Coolify sends team notifications through email, Discord, Telegram, Slack, Mattermost, Pushover, and webhooks.\n  - [Notification Events](/core/notifications/events): Choose which deployment, backup, scheduled task, container, and server events Coolify sends through each notification channel.\n  - Notification Channels\n    - [Email](/core/notifications/channels/email): Configure Coolify email notifications with hosted email, self-hosted instance-wide transactional email, SMTP, or Resend.\n    - [Discord](/core/notifications/channels/discord): Send Coolify notifications to a Discord channel through an incoming webhook.\n    - [Telegram](/core/notifications/channels/telegram): Configure a Telegram bot, chat, and optional topic IDs for Coolify notifications.\n    - [Slack & Mattermost](/core/notifications/channels/slack-mattermost): Send Coolify notifications to Slack or Mattermost through a Slack-compatible incoming webhook.\n    - [Pushover](/core/notifications/channels/pushover): Send Coolify push notifications through a Pushover application.\n    - Webhook Notifications\n      - [Setup](/core/notifications/channels/webhook/setup): Configure Coolify to send notification events as JSON POST requests to an HTTP or HTTPS endpoint.\n      - [Payload Reference](/core/notifications/channels/webhook/payload-reference): Reference for Coolify webhook notification event identifiers, JSON fields, optional values, and example payloads.\n\n  - **Automation**\n  - Scheduled Tasks\n    - [Overview](/core/automation/scheduled-tasks/overview): Understand how Coolify runs scheduled commands inside application and service containers.\n    - [Create a Task](/core/automation/scheduled-tasks/create-a-task): Create a scheduled command for a Coolify application or service and verify its first execution.\n    - [Manage Tasks](/core/automation/scheduled-tasks/manage-tasks): Update, enable, disable, run, and delete scheduled tasks in Coolify.\n    - [Execution History](/core/automation/scheduled-tasks/execution-history): Read scheduled task status, timing, output, and downloadable logs in Coolify.\n  - Tags\n    - [Overview](/core/automation/tags/overview): Group Coolify applications and services with team-scoped tags for filtering and bulk deployment.\n    - [Manage Tags](/core/automation/tags/manage-tags): Create, assign, reuse, and remove tags from Coolify applications and services.\n    - [Deploy by Tag](/core/automation/tags/deploy-by-tag): Redeploy a group of Coolify applications and services from the dashboard or a tag webhook.\n  - [Deploy Webhooks](/core/automation/deploy-webhooks): Trigger Coolify resource or tag deployments from CI and external automation with an authenticated webhook URL.\n  - [Cron Syntax](/core/automation/cron-syntax): Write five-field cron expressions and use Coolify's supported named schedules.\n- Applications\n\n  - **Understand Applications**\n  - [What is an application](/applications/what-is-an-application): Understand what an application is in Coolify and what you need before deploying one.\n  - [How Applications Work](/applications/how-applications-work): Follow how Coolify turns application source or an existing image into running Docker containers.\n  - [Choose a Deployment Method](/applications/choose-deployment-method): Choose whether Coolify deploys a Git repository, a Dockerfile entered without Git, a Git-based Docker Compose definition, or an existing image.\n  - [Coming from Managed Platforms](/applications/coming-from-managed-platforms): Map managed deployment platform concepts to Coolify, Docker, and servers you control.\n\n  - **Source Code**\n  - [Overview](/applications/sources/overview): Choose how Coolify accesses a public or private Git repository.\n  - [Public Repositories](/applications/sources/public-repositories): Deploy a public Git repository without creating a Git source or deploy key.\n  - [Deploy Keys](/applications/sources/deploy-keys): Give Coolify read-only SSH access to one private Git repository.\n  - [Cursor Origin](/applications/sources/cursor-origin): Deploy a private Cursor Origin repository with Coolify by sharing a deploy key between Coolify and Origin.\n  - GitHub\n    - [Overview](/applications/sources/github/overview): Choose a GitHub source method for public and private application repositories.\n    - [GitHub Actions](/applications/sources/github/actions): Build and publish an application image in GitHub Actions, then trigger a Coolify deployment.\n    - [GitHub Auto Deploy](/applications/sources/github/auto-deploy): Automatically deploy applications from GitHub with a GitHub App, GitHub Actions, or a repository webhook.\n    - [GitHub Preview Deployments](/applications/sources/github/preview-deploy): Deploy pull requests separately with scoped access, variables, domains, and GitHub comments.\n    - [Deploy a Public GitHub Repository](/applications/sources/github/public-repository): Deploy an application by giving Coolify the URL of a public GitHub repository.\n    - [GitHub Deploy Key](/applications/sources/github/deploy-key): Give Coolify read-only access to one private GitHub repository.\n    - [Set Up a GitHub App](/applications/sources/github/app): Give Coolify scoped access to selected private or public GitHub repositories.\n    - [Switch GitHub Apps](/applications/sources/github/switch-apps): Move an existing application to another GitHub App source.\n  - [GitLab](/applications/sources/gitlab): Deploy public and private GitLab repositories with a GitLab App, deploy key, or repository URL.\n  - [Bitbucket](/applications/sources/bitbucket): Deploy Bitbucket repositories and configure repository and pull-request webhooks.\n  - [Gitea](/applications/sources/gitea): Deploy Gitea repositories and configure push and pull-request webhooks.\n  - [Other Git Providers](/applications/sources/other-providers): Deploy from another Git-compatible provider with public HTTPS access or an SSH deploy key.\n\n  - **Builds**\n  - [Overview](/applications/builds/overview): Compare how Coolify prepares Docker images for Applications created from Git source.\n  - Nixpacks\n    - [Overview](/applications/builds/nixpacks/overview): Understand how Nixpacks detects an application's codebase and generates image build instructions.\n    - [Deploy with Nixpacks](/applications/builds/nixpacks/deploy): Deploy a server or static application from Git source with Nixpacks.\n    - [Node.js Versioning](/applications/builds/nixpacks/node-versioning): Select a Node.js major version in Nixpacks or pin a nixpkgs archive when an exact package set is required.\n  - [Railpack](/applications/builds/railpack): Create an application image from Git source with Coolify's Railpack Beta build method.\n  - [Static](/applications/builds/static): Package prebuilt static files in an Nginx image and deploy them with Coolify.\n  - [Dockerfile](/applications/builds/dockerfile): Build an application image from a repository-owned Dockerfile or a Dockerfile entered directly in Coolify.\n  - [Docker Compose](/applications/builds/docker-compose): Deploy Docker Compose from a Git repository or a definition stored directly in Coolify.\n  - [Docker Registries](/applications/builds/docker-registries): Pull existing application images and push images built by Coolify to a Docker registry.\n  - [Custom Docker Options](/applications/builds/custom-docker-options): Add supported Docker run options to a Coolify application without replacing its Dockerfile.\n\n  - **Configuration**\n  - [Overview](/applications/configuration/overview): Find the Coolify settings used to configure an application after it is created.\n  - [General](/applications/configuration/general): Configure an application's identity, build method, domains, image settings, ports, labels, and deployment commands.\n  - [Advanced](/applications/configuration/advanced): Configure advanced application build, deployment, Git, proxy, restart, logging, and GPU behavior.\n  - [Environment Variables](/applications/configuration/environment-variables): Configure application values for the build phase, the running container, and preview deployments.\n  - [Persistent Storage](/applications/configuration/persistent-storage): Configure application volume, directory, and file mounts and keep data outside replaceable containers.\n  - [Health Checks](/applications/configuration/health-checks): Configure HTTP or command health checks in Coolify, a Dockerfile, or Docker Compose.\n  - [Resource Limits](/applications/configuration/resource-limits): Limit the CPU and memory available to an application container.\n\n  - **Deployments**\n  - [Overview](/applications/deployments/overview): Understand application deployment triggers, history, logs, and lifecycle actions in Coolify.\n  - [Docker Image](/applications/deployments/docker-image): Deploy an existing Docker image without connecting a Git repository or building source code.\n  - [Automatic Deployments](/applications/deployments/automatic-deployments): Deploy automatically with a Git provider webhook or an authenticated deployment request from external CI.\n  - [Manual Git Webhooks](/applications/deployments/manual-webhooks): Configure repository events for applications connected by a public URL or deploy key.\n  - [Preview Deployments](/applications/deployments/preview-deployments): Deploy pull requests separately with scoped access, variables, domains, and Git provider events.\n  - [Rolling Updates](/applications/deployments/rolling-updates): Understand how Coolify replaces an application container and what the application must do to avoid downtime.\n  - [Rollbacks](/applications/deployments/rollbacks): Redeploy an older application image that is still available on the deployment server.\n\n  - **Operations**\n  - [Overview](/applications/operations/overview): Monitor, troubleshoot, maintain, and protect a running application.\n  - [Scheduled Tasks](/applications/operations/scheduled-tasks): Run recurring commands inside an application container and verify their execution.\n  - [Resource Operations](/applications/operations/resource-operations): Clone an application to another destination or move it between projects and environments.\n  - [Migrate an Application](/applications/operations/migrate-between-instances): Migrate one application and its persistent state to another Coolify instance.\n  - [Danger Zone](/applications/operations/danger-zone): Permanently delete an application and choose which related Docker resources Coolify removes.\n\n  - **Framework Examples**\n  - JavaScript\n    - [NextJS](/applications/framework-examples/javascript/nextjs): Deploy Next.js applications on Coolify with server-side rendering, static builds, Nixpacks, or custom Dockerfile configurations.\n    - [Vite](/applications/framework-examples/javascript/vite): Deploy Vite applications on Coolify with TypeScript or JavaScript, Nixpacks build process, and static site generation.\n    - [Vue](/applications/framework-examples/javascript/vuejs): Deploy Vue.js applications on Coolify with server builds using Node/Express or static SPA builds with routing support.\n    - [Nuxt](/applications/framework-examples/javascript/nuxt): Deploy Nuxt applications on Coolify with server builds, static generation, and Nitro support using Nixpacks build configurations.\n    - [SvelteKit](/applications/framework-examples/javascript/svelte-kit): Deploy SvelteKit applications on Coolify with static builds using adapter-static or Node server builds with adapter-node.\n  - Python\n    - [Django](/applications/framework-examples/python/django): Deploy Django applications on Coolify with gunicorn, automatic builds, environment variables, and Python package management.\n  - PHP\n    - [Laravel](/applications/framework-examples/php/laravel): Deploy Laravel PHP applications on Coolify with Nixpacks, queue workers, scheduler, supervisor, database, and Redis integration.\n    - [Symfony](/applications/framework-examples/php/symfony): Deploy Symfony PHP applications on Coolify with Nixpacks, Doctrine migrations, database connections, and trusted proxy configuration.\n  - Ruby\n    - [Ruby on Rails](/applications/framework-examples/ruby/rails): Deploy Ruby on Rails applications on Coolify with database migrations, MVC pattern support, and automated deployment workflows.\n    - [Jekyll](/applications/framework-examples/ruby/jekyll): Deploy Jekyll static sites on Coolify using Nixpacks or Dockerfile with Ruby, Nginx, and automated build processes.\n  - Elixir\n    - [Phoenix](/applications/framework-examples/elixir/phoenix): Deploy Phoenix framework applications on Coolify with Elixir/Erlang, Nixpacks, environment variables, and database integration.\n- Services\n  - [Services](/services)\n\n  - **Understand Services**\n  - [What is a service](/services/what-is-a-service): Understand Docker Compose Services, one-click templates, and user-defined stacks in Coolify.\n  - [How Services Work](/services/how-services-work): Follow how Coolify turns a one-click template or Docker Compose definition into a running Service stack.\n\n  - **Configuration**\n  - [Overview](/services/configuration/overview): Find the Coolify settings used to configure a Docker Compose Service and its components.\n  - [General](/services/configuration/general): Configure a Service stack, edit its Compose definition, and manage application and database components.\n  - [Networking](/services/configuration/networking): Connect Service components to each other, the Coolify network, other Docker networks, and external clients.\n  - [Docker Compose](/services/configuration/docker-compose): Edit the Docker Compose definition stored on a Service and understand how Coolify turns it into a deployment.\n  - [Environment Variables](/services/configuration/environment-variables): Configure values referenced by a Service's Docker Compose definition.\n  - [Persistent Storage](/services/configuration/persistent-storage): Review Compose-owned volumes, directories, and file mounts used by a Service.\n\n  - **Operations**\n  - [Overview](/services/operations/overview): Deploy, update, monitor, and protect a Docker Compose Service.\n  - [Update a Service](/services/operations/update-service): Safely update image versions, Compose configuration, and environment variables for an existing Service.\n  - [Scheduled Tasks](/services/operations/scheduled-tasks): Run recurring commands inside a selected Service container and verify their execution.\n  - [Resource Operations](/services/operations/resource-operations): Clone a Service to another destination or move it between projects and environments.\n  - [Troubleshooting](/services/operations/troubleshooting): Diagnose failed deployments, degraded components, configuration differences, connection failures, and domain errors in a Service.\n  - [Danger Zone](/services/operations/danger-zone): Permanently delete a Service and choose which related Docker resources Coolify removes.\n\n  - **Service Catalog**\n  - [One-click Service catalog](/services/overview): Browse the Docker Compose templates currently included in Coolify's one-click Service catalog.\n  - [All Services](/services/all): Complete directory of one-click services in Coolify including AI, analytics, databases, CMS, monitoring, and more.\n- Databases\n\n  - **Understand Databases**\n  - [What is a database](/databases/what-is-a-database): Understand standalone databases, generated connection details, and persistent data in Coolify.\n  - [How Databases Work](/databases/how-databases-work): Follow how Coolify creates, connects, stores, checks, and backs up standalone databases.\n  - [Choose a Database](/databases/choose-a-database): Choose a supported database engine, version, and deployment method for your workload.\n\n  - **Configuration**\n  - [Overview](/databases/configuration/overview): Find the Coolify settings used to configure a standalone database after it is created.\n  - [General](/databases/configuration/general): Configure a database image, credentials, engine settings, ports, and public access.\n  - [Environment Variables](/databases/configuration/environment-variables): Configure runtime environment variables passed to a standalone database container.\n  - [Persistent Storage](/databases/configuration/persistent-storage): Configure the volume, directory, and file mounts that keep database data outside the replaceable container.\n  - [Health Checks](/databases/configuration/health-checks): Configure the Docker health check used to report whether a standalone database is healthy.\n  - [Resource Limits](/databases/configuration/resource-limits): Limit the CPU and memory available to a standalone database container.\n\n  - **Operations**\n  - [Overview](/databases/operations/overview): Monitor, maintain, and protect a running standalone database.\n  - [Backups](/databases/backups): Schedule, retain, and store PostgreSQL, MySQL, MariaDB, MongoDB, and ClickHouse database backups in Coolify.\n  - [Restore a Database](/databases/restore): Restore a PostgreSQL, MySQL, MariaDB, or MongoDB backup from a server file, upload, or S3-compatible storage.\n  - [Database SSL](/databases/ssl): Enable SSL for standalone database connections in Coolify, choose a verification mode, and mount the Coolify CA certificate when required.\n  - [Resource Operations](/databases/operations/resource-operations): Clone a standalone database to another destination or move it between projects and environments.\n  - [Danger Zone](/databases/operations/danger-zone): Permanently delete a standalone database and choose which related Docker resources Coolify removes.\n\n  - **Database engines**\n  - [PostgreSQL](/databases/postgresql): Deploy and operate PostgreSQL on Coolify with generated credentials, persistent storage, SSL, health checks, backups, and restore support.\n  - [MySQL](/databases/mysql): Deploy and operate MySQL on Coolify with generated credentials, persistent storage, SSL, health checks, backups, and restore support.\n  - [MariaDB](/databases/mariadb): Deploy and operate MariaDB on Coolify with generated credentials, persistent storage, health checks, SSL, backups, and restore support.\n  - [MongoDB](/databases/mongodb): Deploy and operate MongoDB on Coolify with generated credentials, persistent storage, SSL, health checks, and scheduled dumps.\n  - [Redis](/databases/redis): Deploy and operate Redis on Coolify with generated credentials, persistent storage, TLS, health checks, and private or public connection URLs.\n  - [Dragonfly](/databases/dragonfly): Deploy and operate Dragonfly on Coolify with Redis-compatible connections, persistent storage, TLS, and health checks.\n  - [KeyDB](/databases/keydb): Deploy and operate KeyDB on Coolify with Redis-compatible connections, persistent storage, TLS, and health checks.\n  - [ClickHouse](/databases/clickhouse): Deploy and operate ClickHouse on Coolify for analytical workloads with persistent storage, scheduled backups, and health checks.\n- Integrations\n\n  - **Networking**\n  - Cloudflare Tunnel\n    - [Overview](/integrations/networking/cloudflare/tunnels): Connect Coolify resources securely without port forwarding using Cloudflare Tunnels for all resources, single apps, SSH access, or full HTTPS setups.\n    - [All resources](/integrations/networking/cloudflare/tunnels/all-resource): Expose all Coolify resources securely through Cloudflare Tunnels without public IPs or port forwarding using wildcard domains and HTTP proxy routing.\n    - [Single resource](/integrations/networking/cloudflare/tunnels/single-resource): Securely access individual Coolify applications through Cloudflare Tunnels with port mapping, domain configuration, and multi-resource tunneling support.\n    - [Server SSH](/integrations/networking/cloudflare/tunnels/server-ssh): Enable secure SSH access to Coolify servers via Cloudflare Tunnels with automated or manual cloudflared installation hiding server IP addresses.\n    - [Full TLS](/integrations/networking/cloudflare/tunnels/full-tls): Configure end-to-end HTTPS for Coolify resources through Cloudflare Tunnels with Origin Certificates, strict TLS encryption, and proper domain setup.\n\n  - **Security**\n  - [Cloudflare DDoS Protection](/integrations/security/cloudflare/ddos-protection): Learn how to set up Cloudflare DDoS protection for applications deployed with Coolify.\n  - [CrowdSec](https://www.crowdsec.net/blog/securing-automated-app-deployment-crowdsec-and-coolify)\n- MCP\n\n  - **Understand MCP**\n  - [What is MCP?](/mcp/what-is-mcp): Understand Coolify's Model Context Protocol server and how AI clients access your Coolify resources.\n  - [How MCP works](/mcp/how-mcp-works): Understand how Coolify authenticates MCP clients, scopes data, and exposes tools, resources, and prompts.\n\n  - **Get Started**\n  - [Overview](/mcp/overview): Find the Coolify MCP setup path, supported clients, capabilities, and security guidance.\n  - [Set up MCP](/mcp/setup): Enable Coolify MCP, create a team-scoped API token, and connect an MCP-compatible AI client.\n\n  - **Clients**\n  - [Claude Code](/mcp/clients/claude-code): Configure Claude Code to connect to Coolify's Streamable HTTP MCP server.\n  - [Cursor](/mcp/clients/cursor): Configure Cursor to connect to Coolify's Streamable HTTP MCP server.\n  - [Other MCP clients](/mcp/clients/other-clients): Configure an MCP-compatible client to connect to Coolify over Streamable HTTP.\n\n  - **MCP Capabilities**\n  - [Overview](/mcp/capabilities/overview): Find Coolify MCP tools, resources, and prompts by task.\n  - [Teams](/mcp/capabilities/teams): Use Coolify MCP to inspect the authenticated team and its members.\n  - [Servers](/mcp/capabilities/servers): Use Coolify MCP to inspect servers, destinations, domains, and server resources.\n  - [Projects](/mcp/capabilities/projects): Use Coolify MCP to list projects, inspect environments, and search team resources.\n  - [Applications](/mcp/capabilities/applications): Use Coolify MCP to list and inspect applications and preview deployments.\n  - [Databases](/mcp/capabilities/databases): Use Coolify MCP to list and inspect standalone databases and their backup schedules.\n  - [Services](/mcp/capabilities/services): Use Coolify MCP to inspect one-click services and their application or database components.\n  - [Deployments](/mcp/capabilities/deployments): Use Coolify MCP to inspect, queue, control, and cancel deployments.\n  - [Logs](/mcp/capabilities/logs): Use Coolify MCP to fetch recent container logs with sensitive-data controls.\n  - [Environment and storage](/mcp/capabilities/environment-and-storage): Use Coolify MCP to inspect environment-variable names and storage mounts without returning file contents.\n  - [Integrations](/mcp/capabilities/integrations): Use Coolify MCP to inspect GitHub integrations and browse repositories and branches.\n  - [Automation](/mcp/capabilities/automation): Use Coolify MCP to inspect scheduled tasks, executions, unhealthy resources, and resource health hints.\n  - [Prompts and resources](/mcp/capabilities/prompts-and-resources): Use Coolify MCP prompts and resources for guided workflows and read-only context.\n  - [Pagination](/mcp/capabilities/pagination): Handle paginated Coolify MCP list responses and continue through large result sets.\n\n  - **Security & Troubleshooting**\n  - [MCP security](/mcp/security): Protect Coolify MCP connections with scoped tokens, team boundaries, and limited client access.\n  - [Troubleshoot MCP](/mcp/troubleshooting): Fix common Coolify MCP connection, authentication, permission, and resource-scope problems.\n- Knowledge Base\n\n  - **Scaling**\n  - [Node.js Multi-Core Scaling](/knowledge-base/nodejs-multi-core-scaling): Scale a Node.js, Bun, or Deno application across all available CPU cores using PM2 cluster mode or SO_REUSEPORT, with Dockerfile and Nixpacks examples for Coolify.\n  - [Load Balancing on Hetzner](/knowledge-base/hetzner-loadbalancing): Deploy scalable load-balanced applications on Hetzner Cloud with Coolify including TLS termination, health checks, database setup, and firewall configuration.\n\n  - **How-To Guides**\n  - [macOS using Colima Setup Guide](/knowledge-base/how-to/macos-colima): Install Coolify on macOS using a Colima virtual machine with Docker, covering VM creation, networking, and SSH configuration.\n  - [Deploy Webstudio Projects to Hetzner with Coolify](/knowledge-base/how-to/webstudio-with-hetzner): Complete guide to deploying Webstudio projects with Coolify on Hetzner servers using Docker, GitHub integration, and automated deployment.\n- CLI\n\n  - **Overview**\n  - [What is the Coolify CLI?](/cli/what-is-the-coolify-cli): Install and configure the Coolify CLI to manage Coolify resources from a terminal or automation workflow.\n  - [How the CLI works](/cli/how-cli-works): Understand how the Coolify CLI selects a context, authenticates requests, calls the Coolify API, retries failures, and formats responses.\n\n  - **Get started**\n  - [Installation](/cli/installation): Install and verify the Coolify CLI on Linux, macOS, or Windows.\n  - [Authentication](/cli/authentication): Authenticate the Coolify CLI with a scoped API token for Coolify Cloud or a self-hosted instance.\n  - [Contexts](/cli/contexts): Save, select, update, and remove Coolify CLI connections for Cloud and self-hosted instances.\n\n  - **Workflows**\n  - [Deploy Applications](/cli/deploy-applications): Create, configure, deploy, and monitor an application with the Coolify CLI.\n  - [Automate with the CLI](/cli/automate-with-cli): Use Coolify CLI contexts, JSON output, batch deployments, and exit statuses in scripts and CI jobs.\n  - [Manage Database Backups](/cli/database-backups): Configure, run, and verify scheduled database backups with the Coolify CLI.\n\n  - **Maintain the CLI**\n  - [Update](/cli/update): Update the Coolify CLI with its built-in command or the package method used for installation.\n  - [Uninstall](/cli/uninstallation): Remove the Coolify CLI binary and optionally delete its saved contexts and API tokens.\n\n  - **Commands**\n  - [Global options](/cli/command-reference/commands/global-options): Coolify CLI\n  - Context\n    - [Add](/cli/command-reference/commands/context/add): Add a new context\n    - [Delete](/cli/command-reference/commands/context/delete): Delete a context\n    - [Get](/cli/command-reference/commands/context/get): Get details of a specific context\n    - [List](/cli/command-reference/commands/context/list): List all configured contexts\n    - [Set default](/cli/command-reference/commands/context/set-default): Set a context as the default\n    - [Set token](/cli/command-reference/commands/context/set-token): Update the API token for a context\n    - [Update](/cli/command-reference/commands/context/update): Update a context's properties (name, URL, token)\n    - [Use](/cli/command-reference/commands/context/use): Switch to a different context (set as default)\n    - [Verify](/cli/command-reference/commands/context/verify): Verify current context connection and authentication\n    - [Version](/cli/command-reference/commands/context/version): Get current context's Coolify version\n  - App\n    - [Clone](/cli/command-reference/commands/app/clone): Clone an application to a destination\n    - [Create deploy key](/cli/command-reference/commands/app/create-deploy-key): Create an application from a private repository using SSH deploy key\n    - [Create dockerfile](/cli/command-reference/commands/app/create-dockerfile): Create an application from a custom Dockerfile\n    - [Create dockerimage](/cli/command-reference/commands/app/create-dockerimage): Create an application from a pre-built Docker image\n    - [Create github](/cli/command-reference/commands/app/create-github): Create an application from a private repository using GitHub App\n    - [Create public](/cli/command-reference/commands/app/create-public): Create an application from a public git repository\n    - [Delete](/cli/command-reference/commands/app/delete): Delete an application. This action cannot be undone.\n    - [Deployments list](/cli/command-reference/commands/app/deployments-list): Retrieve a list of all deployments for a specific application.\n    - [Deployments logs](/cli/command-reference/commands/app/deployments-logs): Get deployment logs for an application\n    - [Destinations add](/cli/command-reference/commands/app/destinations-add): Attach a destination\n    - [Destinations list](/cli/command-reference/commands/app/destinations-list): List application destinations\n    - [Destinations remove](/cli/command-reference/commands/app/destinations-remove): Detach a destination\n    - [Env create](/cli/command-reference/commands/app/env-create): Create a new environment variable for a specific application. Use --key and --value flags to specify the variable.\n    - [Env delete](/cli/command-reference/commands/app/env-delete): Delete an environment variable from an application. First UUID is the application, second is the specific environment variable to delete.\n    - [Env get](/cli/command-reference/commands/app/env-get): Get detailed information about a specific environment variable by UUID or key name.\n    - [Env list](/cli/command-reference/commands/app/env-list): List all environment variables for an application\n    - [Env sync](/cli/command-reference/commands/app/env-sync): Sync environment variables from a .env file\n    - [Env update](/cli/command-reference/commands/app/env-update): Update an existing environment variable. Identify it by UUID or key name.\n    - [Execute task](/cli/command-reference/commands/app/execute-task): Execute a scheduled task now\n    - [Get](/cli/command-reference/commands/app/get): Retrieve detailed information about a specific application.\n    - [List](/cli/command-reference/commands/app/list): List all applications in Coolify.\n    - [Logs](/cli/command-reference/commands/app/logs): Get application logs\n    - [Move](/cli/command-reference/commands/app/move): Move an application to another environment\n    - [Previews delete](/cli/command-reference/commands/app/previews-delete): Delete a preview deployment for an application. First argument is the application UUID, second is the pull request ID.\n    - [Restart](/cli/command-reference/commands/app/restart): Restart a running application.\n    - [Rollback images](/cli/command-reference/commands/app/rollback-images): List rollback images\n    - [Rollback run](/cli/command-reference/commands/app/rollback-run): Rollback application to a commit\n    - [Run storage backup](/cli/command-reference/commands/app/run-storage-backup): Run volume backup schedule now\n    - [Start](/cli/command-reference/commands/app/start): Start an application (initiates a deployment).\n    - [Stop](/cli/command-reference/commands/app/stop): Stop a running application.\n    - [Storage create](/cli/command-reference/commands/app/storage-create): Create a storage for an application\n    - [Storage delete](/cli/command-reference/commands/app/storage-delete): Delete a storage from an application\n    - [Storage delete backup](/cli/command-reference/commands/app/storage-delete-backup): Delete storage volume backup schedule\n    - [Storage list](/cli/command-reference/commands/app/storage-list): List all persistent volumes and file storages for a specific application.\n    - [Storage run backup](/cli/command-reference/commands/app/storage-run-backup): Run storage volume backup now\n    - [Storage set backup](/cli/command-reference/commands/app/storage-set-backup): Create or replace storage volume backup schedule\n    - [Storage update](/cli/command-reference/commands/app/storage-update): Update a storage for an application\n    - [Tag add](/cli/command-reference/commands/app/tag-add): Add an application tag\n    - [Tag list](/cli/command-reference/commands/app/tag-list): List application tags\n    - [Tag remove](/cli/command-reference/commands/app/tag-remove): Remove an application tag\n    - [Task create](/cli/command-reference/commands/app/task-create): Create a scheduled task for an application\n    - [Task delete](/cli/command-reference/commands/app/task-delete): Delete an application scheduled task\n    - [Task execute](/cli/command-reference/commands/app/task-execute): Execute an application scheduled task now\n    - [Task executions](/cli/command-reference/commands/app/task-executions): List executions for an application scheduled task\n    - [Task list](/cli/command-reference/commands/app/task-list): List scheduled tasks for an application\n    - [Task update](/cli/command-reference/commands/app/task-update): Update an application scheduled task\n    - [Update](/cli/command-reference/commands/app/update): Update application configuration\n  - Database\n    - [Backup create](/cli/command-reference/commands/database/backup-create): Create a new scheduled backup configuration\n    - [Backup delete](/cli/command-reference/commands/database/backup-delete): Delete a backup configuration and optionally all its executions from S3. First UUID is the database, second is the specific backup configuration.\n    - [Backup delete execution](/cli/command-reference/commands/database/backup-delete-execution): Delete a specific backup execution and optionally from S3. First UUID is the database, second is the backup configuration, third is the specific execution.\n    - [Backup executions](/cli/command-reference/commands/database/backup-executions): List all executions for a backup configuration. First UUID is the database, second is the specific backup configuration.\n    - [Backup list](/cli/command-reference/commands/database/backup-list): List all backup configurations for a specific database.\n    - [Backup trigger](/cli/command-reference/commands/database/backup-trigger): Trigger an immediate backup for a specific backup configuration. First UUID is the database, second is the specific backup configuration to trigger.\n    - [Backup update](/cli/command-reference/commands/database/backup-update): Update a backup configuration settings (frequency, retention, S3, etc.). First UUID is the database, second is the specific backup configuration.\n    - [Clone](/cli/command-reference/commands/database/clone): Clone a database to a destination\n    - [Create](/cli/command-reference/commands/database/create): Create a new database\n    - [Delete](/cli/command-reference/commands/database/delete): Delete a database and optionally clean up its configurations, volumes, and networks.\n    - [Env create](/cli/command-reference/commands/database/env-create): Create a new environment variable for a specific database. Use --key and --value flags to specify the variable.\n    - [Env delete](/cli/command-reference/commands/database/env-delete): Delete an environment variable from a database. First UUID is the database, second is the specific environment variable to delete.\n    - [Env get](/cli/command-reference/commands/database/env-get): Get detailed information about a specific environment variable. First UUID is the database, second is the environment variable UUID or key name.\n    - [Env list](/cli/command-reference/commands/database/env-list): List all environment variables for a specific database.\n    - [Env sync](/cli/command-reference/commands/database/env-sync): Sync environment variables from a .env file\n    - [Env update](/cli/command-reference/commands/database/env-update): Update an existing environment variable. Identify it by UUID or key name.\n    - [Get](/cli/command-reference/commands/database/get): Get detailed information about a specific database by UUID.\n    - [List](/cli/command-reference/commands/database/list): List all databases in Coolify.\n    - [Logs](/cli/command-reference/commands/database/logs): Get database logs\n    - [Move](/cli/command-reference/commands/database/move): Move a database to another environment\n    - [Restart](/cli/command-reference/commands/database/restart): Restart a database by UUID.\n    - [Run storage backup](/cli/command-reference/commands/database/run-storage-backup): Run a volume backup schedule now\n    - [Start](/cli/command-reference/commands/database/start): Start a database by UUID.\n    - [Stop](/cli/command-reference/commands/database/stop): Stop a database by UUID.\n    - [Storage create](/cli/command-reference/commands/database/storage-create): Create a storage for a database\n    - [Storage delete](/cli/command-reference/commands/database/storage-delete): Delete a storage from a database\n    - [Storage delete backup](/cli/command-reference/commands/database/storage-delete-backup): Delete database storage volume backup schedule\n    - [Storage list](/cli/command-reference/commands/database/storage-list): List all persistent volumes and file storages for a specific database.\n    - [Storage run backup](/cli/command-reference/commands/database/storage-run-backup): Run database storage volume backup now\n    - [Storage set backup](/cli/command-reference/commands/database/storage-set-backup): Create or replace database storage volume backup schedule\n    - [Storage update](/cli/command-reference/commands/database/storage-update): Update a storage for a database\n    - [Tag add](/cli/command-reference/commands/database/tag-add): Add a database tag\n    - [Tag list](/cli/command-reference/commands/database/tag-list): List database tags\n    - [Tag remove](/cli/command-reference/commands/database/tag-remove): Remove a database tag\n    - [Update](/cli/command-reference/commands/database/update): Update a database's configuration by UUID.\n  - Service\n    - [Application get](/cli/command-reference/commands/service/application-get): Get an application in a service\n    - [Application list](/cli/command-reference/commands/service/application-list): List applications in a service\n    - [Application logs](/cli/command-reference/commands/service/application-logs): Get logs for an application in a service\n    - [Application restart](/cli/command-reference/commands/service/application-restart): Restart an application in a service\n    - [Application start](/cli/command-reference/commands/service/application-start): Start or redeploy an application in a service\n    - [Application stop](/cli/command-reference/commands/service/application-stop): Stop an application in a service\n    - [Application update](/cli/command-reference/commands/service/application-update): Update an application in a service\n    - [Clone](/cli/command-reference/commands/service/clone): Clone a service to a destination\n    - [Create](/cli/command-reference/commands/service/create): Create a new one-click service\n    - [Database get](/cli/command-reference/commands/service/database-get): Get a database in a service\n    - [Database list](/cli/command-reference/commands/service/database-list): List databases in a service\n    - [Database logs](/cli/command-reference/commands/service/database-logs): Get logs for a database in a service\n    - [Database restart](/cli/command-reference/commands/service/database-restart): Restart a database in a service\n    - [Database start](/cli/command-reference/commands/service/database-start): Start or redeploy a database in a service\n    - [Database stop](/cli/command-reference/commands/service/database-stop): Stop a database in a service\n    - [Database update](/cli/command-reference/commands/service/database-update): Update a database in a service\n    - [Delete](/cli/command-reference/commands/service/delete): Delete a service and optionally clean up its configurations, volumes, and networks.\n    - [Env create](/cli/command-reference/commands/service/env-create): Create a new environment variable for a specific service. Use --key and --value flags to specify the variable.\n    - [Env delete](/cli/command-reference/commands/service/env-delete): Delete an environment variable from a service. First UUID is the service, second is the specific environment variable to delete.\n    - [Env get](/cli/command-reference/commands/service/env-get): Get detailed information about a specific environment variable. First UUID is the service, second is the environment variable UUID or key name.\n    - [Env list](/cli/command-reference/commands/service/env-list): List all environment variables for a specific service.\n    - [Env sync](/cli/command-reference/commands/service/env-sync): Sync environment variables from a .env file\n    - [Env update](/cli/command-reference/commands/service/env-update): Update an existing environment variable. Identify it by UUID or key name.\n    - [Execute task](/cli/command-reference/commands/service/execute-task): Execute a service scheduled task now\n    - [Get](/cli/command-reference/commands/service/get): Get detailed information about a specific service.\n    - [List](/cli/command-reference/commands/service/list): List all services in Coolify.\n    - [Logs](/cli/command-reference/commands/service/logs): Get logs for a service sub-resource\n    - [Move](/cli/command-reference/commands/service/move): Move a service to another environment\n    - [Restart](/cli/command-reference/commands/service/restart): Restart a service (restart all containers).\n    - [Run storage backup](/cli/command-reference/commands/service/run-storage-backup): Run a service volume backup schedule now\n    - [Start](/cli/command-reference/commands/service/start): Start a service (deploy all containers).\n    - [Stop](/cli/command-reference/commands/service/stop): Stop a service (stop all containers).\n    - [Storage create](/cli/command-reference/commands/service/storage-create): Create a storage for a service\n    - [Storage delete](/cli/command-reference/commands/service/storage-delete): Delete a storage from a service\n    - [Storage delete backup](/cli/command-reference/commands/service/storage-delete-backup): Delete service storage volume backup schedule\n    - [Storage list](/cli/command-reference/commands/service/storage-list): List all persistent volumes and file storages for a specific service.\n    - [Storage run backup](/cli/command-reference/commands/service/storage-run-backup): Run service storage volume backup now\n    - [Storage set backup](/cli/command-reference/commands/service/storage-set-backup): Create or replace service storage volume backup schedule\n    - [Storage update](/cli/command-reference/commands/service/storage-update): Update a storage for a service\n    - [Tag add](/cli/command-reference/commands/service/tag-add): Add a service tag\n    - [Tag list](/cli/command-reference/commands/service/tag-list): List service tags\n    - [Tag remove](/cli/command-reference/commands/service/tag-remove): Remove a service tag\n    - [Task create](/cli/command-reference/commands/service/task-create): Create a scheduled task for a service\n    - [Task delete](/cli/command-reference/commands/service/task-delete): Delete a service scheduled task\n    - [Task execute](/cli/command-reference/commands/service/task-execute): Execute a service scheduled task now\n    - [Task executions](/cli/command-reference/commands/service/task-executions): List executions for a service scheduled task\n    - [Task list](/cli/command-reference/commands/service/task-list): List scheduled tasks for a service\n    - [Task update](/cli/command-reference/commands/service/task-update): Update a service scheduled task\n  - Deploy\n    - [Batch](/cli/command-reference/commands/deploy/batch): Deploy multiple resources by name\n    - [Cancel](/cli/command-reference/commands/deploy/cancel): Cancel an in-progress deployment. This will stop the deployment process and clean up any temporary resources.\n    - [Get](/cli/command-reference/commands/deploy/get): Get detailed information about a specific deployment by its UUID.\n    - [List](/cli/command-reference/commands/deploy/list): List all currently running deployments across all resources.\n    - [Name](/cli/command-reference/commands/deploy/name): Deploy by resource name\n    - [Uuid](/cli/command-reference/commands/deploy/uuid): Deploy by uuid\n  - Project\n    - [Create](/cli/command-reference/commands/project/create): Create a new project\n    - [Delete](/cli/command-reference/commands/project/delete): Delete a project\n    - [Environments create](/cli/command-reference/commands/project/environments-create): Create an environment in a project\n    - [Environments delete](/cli/command-reference/commands/project/environments-delete): Delete a project environment\n    - [Environments list](/cli/command-reference/commands/project/environments-list): List environments in a project\n    - [Environments update](/cli/command-reference/commands/project/environments-update): Update a project environment\n    - [Get](/cli/command-reference/commands/project/get): Get a project by uuid\n    - [List](/cli/command-reference/commands/project/list): List all projects\n    - [Update](/cli/command-reference/commands/project/update): Update a project\n    - [Update environment](/cli/command-reference/commands/project/update-environment): Update a project environment. Prefer: coolify project environments update\n  - [List resources](/cli/command-reference/commands/resources): List all resources\n  - Server\n    - [Add](/cli/command-reference/commands/server/add): Add a server\n    - [Cloudflare tunnel disable](/cli/command-reference/commands/server/cloudflare-tunnel-disable): Disable Cloudflare tunnel flag\n    - [Cloudflare tunnel enable](/cli/command-reference/commands/server/cloudflare-tunnel-enable): Enable Cloudflare tunnel flag\n    - [Cloudflare tunnel get](/cli/command-reference/commands/server/cloudflare-tunnel-get): Get Cloudflare tunnel state\n    - [Cloudflare tunnel update](/cli/command-reference/commands/server/cloudflare-tunnel-update): Set Cloudflare tunnel enabled state\n    - [Destinations create](/cli/command-reference/commands/server/destinations-create): Create a server destination\n    - [Destinations list](/cli/command-reference/commands/server/destinations-list): List server destinations\n    - [Digitalocean create](/cli/command-reference/commands/server/digitalocean-create): Create a DigitalOcean server\n    - [Digitalocean images](/cli/command-reference/commands/server/digitalocean-images): List DigitalOcean images\n    - [Digitalocean regions](/cli/command-reference/commands/server/digitalocean-regions): List DigitalOcean regions\n    - [Digitalocean sizes](/cli/command-reference/commands/server/digitalocean-sizes): List DigitalOcean sizes\n    - [Digitalocean ssh keys](/cli/command-reference/commands/server/digitalocean-ssh-keys): List DigitalOcean SSH keys\n    - [Docker cleanup executions](/cli/command-reference/commands/server/docker-cleanup-executions): List docker cleanup executions\n    - [Docker cleanup get](/cli/command-reference/commands/server/docker-cleanup-get): Get docker cleanup settings\n    - [Docker cleanup run](/cli/command-reference/commands/server/docker-cleanup-run): Run docker cleanup now\n    - [Docker cleanup update](/cli/command-reference/commands/server/docker-cleanup-update): Update docker cleanup settings\n    - [Domains](/cli/command-reference/commands/server/domains): Get server domains by uuid\n    - [Get](/cli/command-reference/commands/server/get): Get server details by uuid\n    - [Hetzner create](/cli/command-reference/commands/server/hetzner-create): Create a Hetzner server\n    - [Hetzner firewalls](/cli/command-reference/commands/server/hetzner-firewalls): List Hetzner firewalls\n    - [Hetzner images](/cli/command-reference/commands/server/hetzner-images): List Hetzner images\n    - [Hetzner locations](/cli/command-reference/commands/server/hetzner-locations): List Hetzner locations\n    - [Hetzner networks](/cli/command-reference/commands/server/hetzner-networks): List Hetzner networks\n    - [Hetzner server types](/cli/command-reference/commands/server/hetzner-server-types): List Hetzner server types\n    - [Hetzner ssh keys](/cli/command-reference/commands/server/hetzner-ssh-keys): List Hetzner SSH keys\n    - [List](/cli/command-reference/commands/server/list): List all servers\n    - [Log drains get](/cli/command-reference/commands/server/log-drains-get): Get log drain settings\n    - [Log drains update](/cli/command-reference/commands/server/log-drains-update): Update log drain settings via JSON\n    - [Proxy get](/cli/command-reference/commands/server/proxy-get): Get proxy settings\n    - [Proxy restart](/cli/command-reference/commands/server/proxy-restart): Restart proxy\n    - [Proxy set config](/cli/command-reference/commands/server/proxy-set-config): Save raw proxy configuration\n    - [Proxy update](/cli/command-reference/commands/server/proxy-update): Update proxy settings\n    - [Remove](/cli/command-reference/commands/server/remove): Remove a server\n    - [Sentinel get](/cli/command-reference/commands/server/sentinel-get): Get Sentinel settings\n    - [Sentinel update](/cli/command-reference/commands/server/sentinel-update): Update Sentinel settings via JSON\n    - [Update](/cli/command-reference/commands/server/update): Update a server\n    - [Validate](/cli/command-reference/commands/server/validate): Validate a server\n    - [Vultr create](/cli/command-reference/commands/server/vultr-create): Create a Vultr server\n    - [Vultr os](/cli/command-reference/commands/server/vultr-os): List Vultr operating systems\n    - [Vultr plans](/cli/command-reference/commands/server/vultr-plans): List Vultr plans\n    - [Vultr regions](/cli/command-reference/commands/server/vultr-regions): List Vultr regions\n    - [Vultr ssh keys](/cli/command-reference/commands/server/vultr-ssh-keys): List Vultr SSH keys\n  - Destination\n    - [Create](/cli/command-reference/commands/destination/create): Create a destination for a server\n    - [Delete](/cli/command-reference/commands/destination/delete): Delete an unused destination\n    - [Get](/cli/command-reference/commands/destination/get): Get a destination\n    - [List](/cli/command-reference/commands/destination/list): List destinations\n    - [Update](/cli/command-reference/commands/destination/update): Rename a destination\n  - Cloud Token\n    - [Create](/cli/command-reference/commands/cloud-token/create): Create a cloud provider token\n    - [Delete](/cli/command-reference/commands/cloud-token/delete): Delete a cloud provider token\n    - [Get](/cli/command-reference/commands/cloud-token/get): Show a cloud provider token\n    - [List](/cli/command-reference/commands/cloud-token/list): List cloud provider tokens\n    - [Update](/cli/command-reference/commands/cloud-token/update): Rename a cloud provider token\n    - [Validate](/cli/command-reference/commands/cloud-token/validate): Validate a cloud provider token\n  - Cloud Init\n    - [Create](/cli/command-reference/commands/cloud-init/create): Create a cloud-init script\n    - [Delete](/cli/command-reference/commands/cloud-init/delete): Delete a cloud-init script\n    - [Get](/cli/command-reference/commands/cloud-init/get): Get a cloud-init script\n    - [List](/cli/command-reference/commands/cloud-init/list): List cloud-init scripts\n    - [Update](/cli/command-reference/commands/cloud-init/update): Update a cloud-init script\n  - S3\n    - [Create](/cli/command-reference/commands/s3/create): Create an S3 storage\n    - [Delete](/cli/command-reference/commands/s3/delete): Delete an S3 storage\n    - [Get](/cli/command-reference/commands/s3/get): Get an S3 storage\n    - [List](/cli/command-reference/commands/s3/list): List S3 storages\n    - [Update](/cli/command-reference/commands/s3/update): Update an S3 storage\n    - [Validate](/cli/command-reference/commands/s3/validate): Validate S3 connection\n  - Github\n    - [Branches](/cli/command-reference/commands/github/branches): List branches for a repository\n    - [Create](/cli/command-reference/commands/github/create): Create a GitHub App integration\n    - [Delete](/cli/command-reference/commands/github/delete): Delete a GitHub App integration. The app must not be used by any applications.\n    - [Get](/cli/command-reference/commands/github/get): Get detailed information about a specific GitHub App integration.\n    - [List](/cli/command-reference/commands/github/list): List all GitHub App integrations configured in Coolify.\n    - [Repos](/cli/command-reference/commands/github/repos): List all repositories that are accessible by the specified GitHub App.\n    - [Update](/cli/command-reference/commands/github/update): Update an existing GitHub App integration. Provide the app UUID and the fields you want to update.\n  - Gitlab\n    - [Create](/cli/command-reference/commands/gitlab/create): Create a GitLab App integration\n    - [Delete](/cli/command-reference/commands/gitlab/delete): Delete a GitLab App integration. The app must not be used by any applications.\n    - [Get](/cli/command-reference/commands/gitlab/get): Get detailed information about a specific GitLab App integration.\n    - [List](/cli/command-reference/commands/gitlab/list): List all GitLab App integrations configured in Coolify for the current team (includes system-wide sources).\n    - [Update](/cli/command-reference/commands/gitlab/update): Update an existing GitLab App integration. Provide the app ID or UUID and the fields you want to update.\n  - Notification\n    - [Get](/cli/command-reference/commands/notification/get): Channels: email, discord, slack, telegram, pushover, webhook\n    - [Update](/cli/command-reference/commands/notification/update): Pass settings as JSON via --json. Example: coolify notification update webhook --json '{\"webhook_enabled\":true}'\n  - Shared Env\n    - [Environment create](/cli/command-reference/commands/shared-env/environment-create): Create environment shared env\n    - [Environment delete](/cli/command-reference/commands/shared-env/environment-delete): Delete environment shared env\n    - [Environment list](/cli/command-reference/commands/shared-env/environment-list): List environment shared envs\n    - [Environment update](/cli/command-reference/commands/shared-env/environment-update): Update environment shared env\n    - [Project create](/cli/command-reference/commands/shared-env/project-create): Create project shared env\n    - [Project delete](/cli/command-reference/commands/shared-env/project-delete): Delete project shared env\n    - [Project list](/cli/command-reference/commands/shared-env/project-list): List project shared envs\n    - [Project update](/cli/command-reference/commands/shared-env/project-update): Update project shared env\n    - [Server create](/cli/command-reference/commands/shared-env/server-create): Create server shared env\n    - [Server delete](/cli/command-reference/commands/shared-env/server-delete): Delete server shared env\n    - [Server list](/cli/command-reference/commands/shared-env/server-list): List server shared envs\n    - [Server update](/cli/command-reference/commands/shared-env/server-update): Update server shared env\n    - [Team create](/cli/command-reference/commands/shared-env/team-create): Create team shared env\n    - [Team delete](/cli/command-reference/commands/shared-env/team-delete): Delete team shared env\n    - [Team list](/cli/command-reference/commands/shared-env/team-list): List team shared envs\n    - [Team update](/cli/command-reference/commands/shared-env/team-update): Update team shared env\n  - Teams\n    - [Current](/cli/command-reference/commands/teams/current): Get details of the team associated with the authentication token (API: GET /team).\n    - [Get](/cli/command-reference/commands/teams/get): Get detailed information about a specific team by its ID.\n    - [List](/cli/command-reference/commands/teams/list): List all teams you have access to.\n    - [Members list](/cli/command-reference/commands/teams/members-list): List members of a specific team by ID, or list members of the current team if no ID is provided.\n  - Private Key\n    - [Add](/cli/command-reference/commands/private-key/add): Add a private key\n    - [Get](/cli/command-reference/commands/private-key/get): Get a private key by UUID\n    - [List](/cli/command-reference/commands/private-key/list): List all private keys\n    - [Remove](/cli/command-reference/commands/private-key/remove): Remove a private key\n    - [Update](/cli/command-reference/commands/private-key/update): Update a private key\n  - Tag\n    - [Create](/cli/command-reference/commands/tag/create): Create a team tag\n    - [Delete](/cli/command-reference/commands/tag/delete): Delete a team tag\n    - [List](/cli/command-reference/commands/tag/list): List all team tags\n    - [Update](/cli/command-reference/commands/tag/update): Rename a team tag\n  - Mcp\n    - [Disable](/cli/command-reference/commands/mcp/disable): Disable the Coolify MCP server (API: POST /mcp/disable). Requires a root team API token.\n    - [Enable](/cli/command-reference/commands/mcp/enable): Enable the Coolify MCP server (API: POST /mcp/enable). Requires a root team API token.\n  - [Completion](/cli/command-reference/commands/completion): Output shell completion code for the specified shell\n  - [Config](/cli/command-reference/commands/config): Display the path to the Coolify CLI configuration file\n  - [Version](/cli/command-reference/commands/version): Current Coolify CLI version\n  - [Update](/cli/command-reference/commands/update): Update Coolify CLI\n  - Settings\n    - [Email get](/cli/command-reference/commands/settings/email-get): Get instance email settings\n    - [Email update](/cli/command-reference/commands/settings/email-update): Pass settings as JSON via --json. Requires write:sensitive. Example: coolify settings email update --json '{\"smtp_ehlo_domain\":\"coolify.example.com\"}'\n- API Reference\n\n  - **Get Started**\n  - [Overview](/api/overview): Find the Coolify API base URL and the documentation for authentication, access controls, limits, errors, and endpoints.\n  - [Making Requests](/api/making-requests): Build Coolify API URLs, send headers and JSON bodies, and handle API responses.\n\n  - **Access & Security**\n  - [Authorization](/api/authorization): Authenticate Coolify API requests with a Bearer token and understand the access checks applied to each request.\n  - [Permissions](/api/permissions): Choose Coolify API token permissions and understand team, role, and sensitive-data restrictions.\n  - [IP Allowlist](/api/ip-allowlist): Enable the API on a self-hosted Coolify instance and restrict authenticated requests by source IP address or network.\n\n  - **Requests & Responses**\n  - [Rate Limits](/api/rate-limits): Understand Coolify API request limits, response headers, reset times, and safe retry behavior.\n  - [Errors](/api/errors): Interpret Coolify API status codes and diagnose authentication, authorization, validation, and rate-limit failures.\n\n  - **Endpoints**\n  - Applications\n    - [Add Destination](/api/endpoints/applications/add-application-destination): Attach an additional standalone Docker destination to an application.\n    - [Clone](/api/endpoints/applications/clone-application-by-uuid): Clone an application to a destination owned by the authenticated team.\n    - [Create (Dockerfile without git)](/api/endpoints/applications/create-dockerfile-application): Create new application based on a simple Dockerfile (without git).\n    - [Create (Docker Image without git)](/api/endpoints/applications/create-dockerimage-application): Create new application based on a prebuilt docker image (without git).\n    - [Create Env](/api/endpoints/applications/create-env-by-application-uuid): Create env by application UUID.\n    - [Create (Private - Deploy Key)](/api/endpoints/applications/create-private-deploy-key-application): Create new application based on a private repository through a Deploy Key.\n    - [Create (Private - GH App)](/api/endpoints/applications/create-private-github-app-application): Create new application based on a private repository through a Github App.\n    - [Create (Public)](/api/endpoints/applications/create-public-application): Create new application based on a public git repository.\n    - [Create Storage](/api/endpoints/applications/create-storage-by-application-uuid): Create a persistent storage or file storage for an application.\n    - [Create Tag](/api/endpoints/applications/create-tag-by-application-uuid): Add tag(s) to an application by UUID.\n    - [Delete](/api/endpoints/applications/delete-application-by-uuid): Delete application by UUID.\n    - [Delete application storage backup schedule](/api/endpoints/applications/delete-application-storage-backup-schedule): Delete the backup schedule and its local and S3 archives for an application storage.\n    - [Delete Env](/api/endpoints/applications/delete-env-by-application-uuid): Delete env by UUID.\n    - [Delete Preview Deployment](/api/endpoints/applications/delete-preview-deployment-by-pull-request-id): Delete a preview deployment for a pull request. Cancels active deployments, stops containers, removes volumes/networks, and deletes the preview record.\n    - [Delete Storage](/api/endpoints/applications/delete-storage-by-application-uuid): Delete a persistent storage or file storage by application UUID.\n    - [Delete Tag](/api/endpoints/applications/delete-tag-by-application-uuid): Remove a tag from an application by UUID.\n    - [Get](/api/endpoints/applications/get-application-by-uuid): Get application by UUID.\n    - [Get application logs.](/api/endpoints/applications/get-application-logs-by-uuid): Get application logs by UUID.\n    - [List Destinations](/api/endpoints/applications/list-application-destinations): List primary and additional destinations for a standalone application.\n    - [List Rollback Images](/api/endpoints/applications/list-application-rollback-images): List available Docker images for rolling back an application. Returns an empty list when the server is unavailable or remote inspection is not possible.\n    - [List](/api/endpoints/applications/list-applications): List all applications.\n    - [List Envs](/api/endpoints/applications/list-envs-by-application-uuid): List all envs by application UUID.\n    - [List Storages](/api/endpoints/applications/list-storages-by-application-uuid): List all persistent storages and file storages by application UUID.\n    - [List Tags](/api/endpoints/applications/list-tags-by-application-uuid): List tags for an application by UUID.\n    - [Migrate to Server](/api/endpoints/applications/migrate-application-by-uuid): Migrate an application to another destination/server owned by the authenticated team. Stops the application, optionally transfers persistent volume data when both servers are managed by Coolify, and updates database records. Redeploy after migration completes.\n    - [Move](/api/endpoints/applications/move-application-by-uuid): Move application to another project/environment. This is a purely organizational change — running containers are not affected. Note: after moving, the application will pick up shared environment variables from the new environment on the next deployment.\n    - [Remove Destination](/api/endpoints/applications/remove-application-destination): Detach an additional destination from an application.\n    - [Restart](/api/endpoints/applications/restart-application-by-uuid): Restart application.\n    - [Rollback](/api/endpoints/applications/rollback-application-by-uuid): Queue a rollback deployment for an application to a previous image commit/tag.\n    - [Run application storage backup](/api/endpoints/applications/run-application-storage-backup): Queue an immediate volume backup for an application storage that has a schedule.\n    - [Set application storage backup schedule](/api/endpoints/applications/set-application-storage-backup-schedule): Create or replace the backup schedule for an application persistent volume or directory storage.\n    - [Start](/api/endpoints/applications/start-application-by-uuid): Start application.\n    - [Stop](/api/endpoints/applications/stop-application-by-uuid): Stop application.\n    - [Update](/api/endpoints/applications/update-application-by-uuid): Update application by UUID.\n    - [Update Env](/api/endpoints/applications/update-env-by-application-uuid): Update env by application UUID.\n    - [Update Envs (Bulk)](/api/endpoints/applications/update-envs-by-application-uuid): Update multiple envs by application UUID.\n    - [Update Storage](/api/endpoints/applications/update-storage-by-application-uuid): Update a persistent storage or file storage by application UUID.\n  - Cloud init scripts\n    - [Create Cloud-init Script](/api/endpoints/cloud-init-scripts/create-cloud-init-script): Create a new cloud-init script for the authenticated team.\n    - [Delete Cloud-init Script](/api/endpoints/cloud-init-scripts/delete-cloud-init-script-by-uuid): Delete a cloud-init script by UUID.\n    - [Get Cloud-init Script](/api/endpoints/cloud-init-scripts/get-cloud-init-script-by-uuid): Get a cloud-init script by UUID.\n    - [List Cloud-init Scripts](/api/endpoints/cloud-init-scripts/list-cloud-init-scripts): List all cloud-init scripts for the authenticated team.\n    - [Update Cloud-init Script](/api/endpoints/cloud-init-scripts/update-cloud-init-script-by-uuid): Update a cloud-init script by UUID.\n  - Cloud tokens\n    - [Create Cloud Provider Token](/api/endpoints/cloud-tokens/create-cloud-token): Create a new cloud provider token. The token will be validated before being stored.\n    - [Delete Cloud Provider Token](/api/endpoints/cloud-tokens/delete-cloud-token-by-uuid): Delete cloud provider token by UUID. Cannot delete if token is used by any servers.\n    - [Get Cloud Provider Token](/api/endpoints/cloud-tokens/get-cloud-token-by-uuid): Get cloud provider token by UUID.\n    - [List Cloud Provider Tokens](/api/endpoints/cloud-tokens/list-cloud-tokens): List all cloud provider tokens for the authenticated team.\n    - [Update Cloud Provider Token](/api/endpoints/cloud-tokens/update-cloud-token-by-uuid): Update cloud provider token name.\n    - [Validate Cloud Provider Token](/api/endpoints/cloud-tokens/validate-cloud-token-by-uuid): Validate a cloud provider token against the provider API.\n  - Databases\n    - [Clone](/api/endpoints/databases/clone-database-by-uuid): Clone a database to a destination owned by the authenticated team.\n    - [Create Backup](/api/endpoints/databases/create-database-backup): Create a new scheduled backup configuration for a database\n    - [Create (Clickhouse)](/api/endpoints/databases/create-database-clickhouse): Create a new Clickhouse database.\n    - [Create (DragonFly)](/api/endpoints/databases/create-database-dragonfly): Create a new DragonFly database.\n    - [Create (KeyDB)](/api/endpoints/databases/create-database-keydb): Create a new KeyDB database.\n    - [Create (MariaDB)](/api/endpoints/databases/create-database-mariadb): Create a new MariaDB database.\n    - [Create (MongoDB)](/api/endpoints/databases/create-database-mongodb): Create a new MongoDB database.\n    - [Create (MySQL)](/api/endpoints/databases/create-database-mysql): Create a new MySQL database.\n    - [Create (PostgreSQL)](/api/endpoints/databases/create-database-postgresql): Create a new PostgreSQL database.\n    - [Create (Redis)](/api/endpoints/databases/create-database-redis): Create a new Redis database.\n    - [Create Env](/api/endpoints/databases/create-env-by-database-uuid): Create env by database UUID.\n    - [Create Storage](/api/endpoints/databases/create-storage-by-database-uuid): Create a persistent storage or file storage for a database.\n    - [Create Tag](/api/endpoints/databases/create-tag-by-database-uuid): Add tag(s) to a database by UUID.\n    - [Delete backup configuration](/api/endpoints/databases/delete-backup-configuration-by-uuid): Deletes a backup configuration and all its executions.\n    - [Delete backup execution](/api/endpoints/databases/delete-backup-execution-by-uuid): Deletes a specific backup execution.\n    - [Delete](/api/endpoints/databases/delete-database-by-uuid): Delete database by UUID.\n    - [Delete database storage backup schedule](/api/endpoints/databases/delete-database-storage-backup-schedule): Delete the backup schedule and its local and S3 archives for a database storage.\n    - [Delete Env](/api/endpoints/databases/delete-env-by-database-uuid): Delete env by UUID.\n    - [Delete Storage](/api/endpoints/databases/delete-storage-by-database-uuid): Delete a persistent storage or file storage by database UUID.\n    - [Delete Tag](/api/endpoints/databases/delete-tag-by-database-uuid): Remove a tag from a database by UUID.\n    - [Database backups](/api/endpoints/databases/get-database-backups-by-uuid): Get backups details by database UUID.\n    - [Database](/api/endpoints/databases/get-database-by-uuid): Get database by UUID.\n    - [Get database logs.](/api/endpoints/databases/get-database-logs-by-uuid): Get database logs by UUID.\n    - [List backup executions](/api/endpoints/databases/list-backup-executions): Get all executions for a specific backup configuration.\n    - [List](/api/endpoints/databases/list-databases): List all databases.\n    - [List Envs](/api/endpoints/databases/list-envs-by-database-uuid): List all envs by database UUID.\n    - [List Storages](/api/endpoints/databases/list-storages-by-database-uuid): List all persistent storages and file storages by database UUID.\n    - [List Tags](/api/endpoints/databases/list-tags-by-database-uuid): List tags for a database by UUID.\n    - [Migrate to Server](/api/endpoints/databases/migrate-database-by-uuid): Migrate a database to another destination/server owned by the authenticated team. Stops the database, optionally transfers persistent volume data when both servers are managed by Coolify, and updates database records. Redeploy after migration completes.\n    - [Move](/api/endpoints/databases/move-database-by-uuid): Move database to another project/environment. This is a purely organizational change — running containers are not affected. Note: after moving, the database will pick up shared environment variables from the new environment on the next deployment.\n    - [Restart](/api/endpoints/databases/restart-database-by-uuid): Restart database.\n    - [Run database storage backup](/api/endpoints/databases/run-database-storage-backup): Queue an immediate volume backup for a database storage that has a schedule.\n    - [Set database storage backup schedule](/api/endpoints/databases/set-database-storage-backup-schedule): Create or replace the backup schedule for a database persistent volume or directory storage.\n    - [Start](/api/endpoints/databases/start-database-by-uuid): Start database.\n    - [Stop](/api/endpoints/databases/stop-database-by-uuid): Stop database.\n    - [Database backup](/api/endpoints/databases/update-database-backup): Update a specific backup configuration for a given database, identified by its UUID and the backup ID\n    - [Database](/api/endpoints/databases/update-database-by-uuid): Update database by UUID.\n    - [Update Env](/api/endpoints/databases/update-env-by-database-uuid): Update env by database UUID.\n    - [Update Envs (Bulk)](/api/endpoints/databases/update-envs-by-database-uuid): Update multiple envs by database UUID.\n    - [Update Storage](/api/endpoints/databases/update-storage-by-database-uuid): Update a persistent storage or file storage by database UUID.\n  - Deployments\n    - [Cancel](/api/endpoints/deployments/cancel-deployment-by-uuid): Cancel a deployment by UUID.\n    - [Deploy](/api/endpoints/deployments/deploy-by-tag-or-uuid): Deploy by tag or UUID using query parameters or a JSON body.\n    - [Get](/api/endpoints/deployments/get-deployment-by-uuid): Get deployment by UUID.\n    - [List application deployments](/api/endpoints/deployments/list-deployments-by-app-uuid): List application deployments by using the app uuid\n    - [List](/api/endpoints/deployments/list-deployments): List currently running deployments\n  - Destinations\n    - [Create destination](/api/endpoints/destinations/create-server-destination): Create a Docker network destination on a server owned by the authenticated team.\n    - [Delete destination](/api/endpoints/destinations/delete-destination-by-uuid): Delete an unused Docker network destination.\n    - [Get destination](/api/endpoints/destinations/get-destination-by-uuid): Get a Docker network destination by UUID.\n    - [List destinations](/api/endpoints/destinations/list-destinations): List all Docker network destinations for the authenticated team.\n    - [List destinations by server](/api/endpoints/destinations/list-server-destinations): List Docker network destinations attached to a server owned by the authenticated team.\n    - [Update destination](/api/endpoints/destinations/update-destination-by-uuid): Update a Docker network destination name. Network cannot be changed via the API.\n  - Digitalocean\n    - [Create a server on DigitalOcean](/api/endpoints/digitalocean/create-digitalocean-server)\n    - [Get DigitalOcean images](/api/endpoints/digitalocean/get-digitalocean-images)\n    - [Get DigitalOcean regions](/api/endpoints/digitalocean/get-digitalocean-regions)\n    - [Get DigitalOcean sizes](/api/endpoints/digitalocean/get-digitalocean-sizes)\n    - [Get DigitalOcean SSH keys](/api/endpoints/digitalocean/get-digitalocean-ssh-keys)\n  - Github apps\n    - [Create GitHub App](/api/endpoints/github-apps/create-github-app): Create a new GitHub app.\n    - [Delete GitHub App](/api/endpoints/github-apps/deleteGithubApp): Delete a GitHub app if it's not being used by any applications.\n    - [List](/api/endpoints/github-apps/list-github-apps): List all GitHub apps.\n    - [Load Branches for a GitHub Repository](/api/endpoints/github-apps/load-branches): Fetch branches from GitHub for a given repository.\n    - [Load Repositories for a GitHub App](/api/endpoints/github-apps/load-repositories): Fetch repositories from GitHub for a given GitHub app.\n    - [Update GitHub App](/api/endpoints/github-apps/updateGithubApp): Update an existing GitHub app.\n  - Gitlab apps\n    - [Create GitLab App](/api/endpoints/gitlab-apps/create-gitlab-app): Create a new GitLab app (OAuth source). Credentials may be supplied later via the UI or update endpoint.\n    - [Delete GitLab App](/api/endpoints/gitlab-apps/deleteGitlabApp): Delete a GitLab app if it is not being used by any applications.\n    - [List](/api/endpoints/gitlab-apps/list-gitlab-apps): List all GitLab apps for the current team (and system-wide sources).\n    - [Update GitLab App](/api/endpoints/gitlab-apps/updateGitlabApp): Update an existing GitLab app.\n  - Hetzner\n    - [Create Hetzner Server](/api/endpoints/hetzner/create-hetzner-server): Create a new server on Hetzner and register it in Coolify.\n    - [Get Hetzner Firewalls](/api/endpoints/hetzner/get-hetzner-firewalls): Get all existing Hetzner firewalls for the current project.\n    - [Get Hetzner Images](/api/endpoints/hetzner/get-hetzner-images): Get all available Hetzner system images (operating systems).\n    - [Get Hetzner Locations](/api/endpoints/hetzner/get-hetzner-locations): Get all available Hetzner datacenter locations.\n    - [Get Hetzner Networks](/api/endpoints/hetzner/get-hetzner-networks): Get all existing Hetzner private networks for the current project.\n    - [Get Hetzner Server Types](/api/endpoints/hetzner/get-hetzner-server-types): Get all available Hetzner server types (instance sizes).\n    - [Get Hetzner SSH Keys](/api/endpoints/hetzner/get-hetzner-ssh-keys): Get all SSH keys stored in the Hetzner account.\n  - Notifications\n    - [Get Discord notification settings](/api/endpoints/notifications/get-current-team-discord-notifications): Get the current team Discord notification settings. Encrypted secrets are only returned when the token has `read:sensitive` (or `root`) and the user is a team admin/owner.\n    - [Get email notification settings](/api/endpoints/notifications/get-current-team-email-notifications): Get the current team email notification settings. Encrypted secrets are only returned when the token has `read:sensitive` (or `root`) and the user is a team admin/owner.\n    - [Get Pushover notification settings](/api/endpoints/notifications/get-current-team-pushover-notifications): Get the current team Pushover notification settings. Encrypted secrets are only returned when the token has `read:sensitive` (or `root`) and the user is a team admin/owner.\n    - [Get Slack notification settings](/api/endpoints/notifications/get-current-team-slack-notifications): Get the current team Slack notification settings. Encrypted secrets are only returned when the token has `read:sensitive` (or `root`) and the user is a team admin/owner.\n    - [Get Telegram notification settings](/api/endpoints/notifications/get-current-team-telegram-notifications): Get the current team Telegram notification settings. Encrypted secrets are only returned when the token has `read:sensitive` (or `root`) and the user is a team admin/owner.\n    - [Get webhook notification settings](/api/endpoints/notifications/get-current-team-webhook-notifications): Get the current team webhook notification settings. Encrypted secrets are only returned when the token has `read:sensitive` (or `root`) and the user is a team admin/owner.\n    - [Update Discord notification settings](/api/endpoints/notifications/update-current-team-discord-notifications): Update the current team Discord notification settings.\n    - [Update email notification settings](/api/endpoints/notifications/update-current-team-email-notifications): Update the current team email notification settings.\n    - [Update Pushover notification settings](/api/endpoints/notifications/update-current-team-pushover-notifications): Update the current team Pushover notification settings.\n    - [Update Slack notification settings](/api/endpoints/notifications/update-current-team-slack-notifications): Update the current team Slack notification settings.\n    - [Update Telegram notification settings](/api/endpoints/notifications/update-current-team-telegram-notifications): Update the current team Telegram notification settings.\n    - [Update webhook notification settings](/api/endpoints/notifications/update-current-team-webhook-notifications): Update the current team webhook notification settings.\n  - Private keys\n    - [Create](/api/endpoints/private-keys/create-private-key): Create a new private key.\n    - [Delete](/api/endpoints/private-keys/delete-private-key-by-uuid): Delete a private key.\n    - [Get](/api/endpoints/private-keys/get-private-key-by-uuid): Get key by UUID.\n    - [List](/api/endpoints/private-keys/list-private-keys): List all private keys.\n    - [Update](/api/endpoints/private-keys/update-private-key): Update a private key.\n  - Projects\n    - [Create Environment](/api/endpoints/projects/create-environment): Create environment in project.\n    - [Create](/api/endpoints/projects/create-project): Create Project.\n    - [Delete Environment](/api/endpoints/projects/delete-environment): Delete environment by name or UUID. Environment must be empty.\n    - [Delete](/api/endpoints/projects/delete-project-by-uuid): Delete project by UUID.\n    - [Environment](/api/endpoints/projects/get-environment-by-name-or-uuid): Get environment by name or UUID.\n    - [List Environments](/api/endpoints/projects/get-environments): List all environments in a project.\n    - [Get](/api/endpoints/projects/get-project-by-uuid): Get project by UUID.\n    - [List](/api/endpoints/projects/list-projects): List projects.\n    - [Update Environment](/api/endpoints/projects/update-environment): Update environment by name or UUID within a project.\n    - [Update](/api/endpoints/projects/update-project-by-uuid): Update Project.\n  - Resources\n    - [List](/api/endpoints/resources/list-resources): Get all resources.\n  - S3 storages\n    - [Create S3 Storage](/api/endpoints/s3-storages/create-s3-storage): Create a new S3 storage configuration for the authenticated team.\n    - [Delete S3 Storage](/api/endpoints/s3-storages/delete-s3-storage-by-uuid): Delete S3 storage by UUID.\n    - [Get S3 Storage](/api/endpoints/s3-storages/get-s3-storage-by-uuid): Get S3 storage by UUID.\n    - [List S3 Storages](/api/endpoints/s3-storages/list-s3-storages): List all S3 storages for the authenticated team.\n    - [Update S3 Storage](/api/endpoints/s3-storages/update-s3-storage-by-uuid): Update S3 storage by UUID.\n    - [Validate S3 Storage](/api/endpoints/s3-storages/validate-s3-storage-by-uuid): Validate an S3 storage connection using ListObjectsV2.\n  - Scheduled tasks\n    - [Create scheduled task](/api/endpoints/scheduled-tasks/create-scheduled-task-by-application-uuid): Create a new scheduled task for an application.\n    - [Create scheduled task](/api/endpoints/scheduled-tasks/create-scheduled-task-by-service-uuid): Create a new scheduled task for a service.\n    - [Scheduled task](/api/endpoints/scheduled-tasks/delete-scheduled-task-by-application-uuid): Delete a scheduled task for an application.\n    - [Scheduled task](/api/endpoints/scheduled-tasks/delete-scheduled-task-by-service-uuid): Delete a scheduled task for a service.\n    - [Execute scheduled task](/api/endpoints/scheduled-tasks/execute-scheduled-task-by-application-uuid): Queue immediate execution of a scheduled task for an application.\n    - [Execute scheduled task](/api/endpoints/scheduled-tasks/execute-scheduled-task-by-service-uuid): Queue immediate execution of a scheduled task for a service.\n    - [List scheduled task executions](/api/endpoints/scheduled-tasks/list-scheduled-task-executions-by-application-uuid): List all executions for a scheduled task on an application.\n    - [List scheduled task executions](/api/endpoints/scheduled-tasks/list-scheduled-task-executions-by-service-uuid): List all executions for a scheduled task on a service.\n    - [List scheduled tasks](/api/endpoints/scheduled-tasks/list-scheduled-tasks-by-application-uuid): List all scheduled tasks for an application.\n    - [List scheduled tasks](/api/endpoints/scheduled-tasks/list-scheduled-tasks-by-service-uuid): List all scheduled tasks for a service.\n    - [Scheduled task](/api/endpoints/scheduled-tasks/update-scheduled-task-by-application-uuid): Update a scheduled task for an application.\n    - [Scheduled task](/api/endpoints/scheduled-tasks/update-scheduled-task-by-service-uuid): Update a scheduled task for a service.\n  - Servers\n    - [Claim imported server](/api/endpoints/servers/claim-server): Claim a managed host for this instance: write ownership file and rebind Sentinel.\n    - [Mark server transferred](/api/endpoints/servers/complete-server-transfer): Source-instance step: disable automations after a successful export/import handoff.\n    - [Create](/api/endpoints/servers/create-server): Create Server.\n    - [Delete](/api/endpoints/servers/delete-server-by-uuid): Delete server by UUID.\n    - [Disable Cloudflare Tunnel](/api/endpoints/servers/disable-server-cloudflare-tunnel): Mark Cloudflare Tunnel as disabled and restore ip_previous when available. Does not remove the remote cloudflared container.\n    - [Enable Cloudflare Tunnel (manual)](/api/endpoints/servers/enable-server-cloudflare-tunnel): Manually mark Cloudflare Tunnel as enabled for a server (matches UI manual enable). Does not deploy cloudflared remotely.\n    - [Export server transfer bundle](/api/endpoints/servers/export-server-transfer-bundle): Export a server and all resources hosted on it as a versioned transfer bundle for moving between Coolify instances. Requires read:sensitive.\n    - [Write transfer bundle to server mailbox](/api/endpoints/servers/export-server-transfer-mailbox): Write an export bundle to /data/coolify/exports on the managed host for air-gapped import.\n    - [Domains](/api/endpoints/servers/get-domains-by-server-uuid): Get domains by server.\n    - [Resources](/api/endpoints/servers/get-resources-by-server-uuid): Get resources by server.\n    - [Get](/api/endpoints/servers/get-server-by-uuid): Get server by UUID.\n    - [Get Cloudflare Tunnel settings](/api/endpoints/servers/get-server-cloudflare-tunnel): Get Cloudflare Tunnel settings for a server owned by the authenticated team.\n    - [Get Docker cleanup settings](/api/endpoints/servers/get-server-docker-cleanup): Get Docker cleanup settings for a server owned by the authenticated team.\n    - [Get log drain settings](/api/endpoints/servers/get-server-log-drains): Get log drain settings for a server owned by the authenticated team. Sensitive fields require the read:sensitive or root token ability.\n    - [Get server proxy](/api/endpoints/servers/get-server-proxy): Get proxy settings for a server owned by the authenticated team. The raw proxy configuration is only returned when the token has `read:sensitive` (or `root`) and the user is a team admin/owner, and only when already stored in the database (no remote fetch).\n    - [Get Sentinel settings](/api/endpoints/servers/get-server-sentinel): Get Sentinel settings for a server owned by the authenticated team. sentinel_token and sentinel_custom_url require the read:sensitive or root token ability.\n    - [Import server transfer bundle](/api/endpoints/servers/import-server-transfer-bundle): Import a server transfer bundle into this Coolify instance (adopt mode by default).\n    - [List Docker cleanup executions](/api/endpoints/servers/list-server-docker-cleanup-executions): List recent Docker cleanup execution logs for a server owned by the authenticated team.\n    - [List](/api/endpoints/servers/list-servers): List all servers.\n    - [Migrate server to another Coolify instance](/api/endpoints/servers/migrate-server-between-instances): One-shot handoff: export this server, import+claim on the target instance (using the provided token), then disable automations here. Requires read:sensitive and write.\n    - [Restart server proxy](/api/endpoints/servers/restart-server-proxy): Queue a proxy restart for a team-owned server.\n    - [Run Docker cleanup](/api/endpoints/servers/run-server-docker-cleanup): Dispatch a manual Docker cleanup job for a server owned by the authenticated team.\n    - [Save server proxy configuration](/api/endpoints/servers/save-server-proxy-configuration): Save the raw proxy Docker Compose configuration for a team-owned server. Multi-line configuration must be base64 encoded (same pattern as other compose payloads).\n    - [Update](/api/endpoints/servers/update-server-by-uuid): Update Server.\n    - [Update Cloudflare Tunnel settings](/api/endpoints/servers/update-server-cloudflare-tunnel): Update stored Cloudflare Tunnel settings for a server. Does not run remote cloudflared configuration; use enable/disable for the manual UI actions.\n    - [Update Docker cleanup settings](/api/endpoints/servers/update-server-docker-cleanup): Update Docker cleanup settings for a server owned by the authenticated team.\n    - [Update log drain settings](/api/endpoints/servers/update-server-log-drains): Update New Relic, Axiom, or custom log drain settings for a server owned by the authenticated team.\n    - [Update server proxy](/api/endpoints/servers/update-server-proxy): Update proxy redirect settings, exact labels generation, and optionally the proxy type for a team-owned server.\n    - [Update Sentinel settings](/api/endpoints/servers/update-server-sentinel): Update Sentinel settings for a server owned by the authenticated team. Changing token/metrics timing fields may restart Sentinel.\n    - [Validate](/api/endpoints/servers/validate-server-by-uuid): Validate server by UUID.\n  - Service applications\n    - [Get service application](/api/endpoints/service-applications/get-service-application-by-service-and-app-uuid): Get a single compose service application by service UUID and application UUID.\n    - [Service application logs](/api/endpoints/service-applications/get-service-application-logs-by-service-and-app-uuid): Get Docker logs for a single compose service container.\n    - [List service applications](/api/endpoints/service-applications/list-service-applications-by-service-uuid): List compose service applications (containers) for a single service.\n    - [Update service application](/api/endpoints/service-applications/patch-service-application-by-service-and-app-uuid): Update fields for a compose service application. Use `url` for comma-separated public URLs (same rules as `urls[].url` on PATCH /services/{uuid}).\n    - [Restart service application container](/api/endpoints/service-applications/post-restart-service-application-by-service-and-app-uuid): Restarts a single compose service container.\n    - [Service application logs](/api/endpoints/service-applications/post-service-application-logs-by-service-and-app-uuid): Get Docker logs for a single compose service container.\n    - [Start or redeploy service application container](/api/endpoints/service-applications/post-start-service-application-by-service-and-app-uuid): Runs docker compose up for a single compose service (no-deps), optionally pulling the image and rebuilding.\n    - [Stop service application container](/api/endpoints/service-applications/post-stop-service-application-by-service-and-app-uuid): Stops a single compose service container.\n  - Service databases\n    - [Get service database](/api/endpoints/service-databases/get-service-database-by-service-and-database-uuid): Get a compose database by service UUID and database UUID.\n    - [Get service database logs](/api/endpoints/service-databases/get-service-database-logs-by-service-and-database-uuid): Get Docker logs for a compose database container.\n    - [List service databases](/api/endpoints/service-databases/list-service-databases-by-service-uuid): List compose databases for a single service.\n    - [Update service database](/api/endpoints/service-databases/patch-service-database-by-service-and-database-uuid): Update mutable fields for a compose service database.\n    - [Restart service database container](/api/endpoints/service-databases/restart-service-database-by-service-and-database-uuid): Restart a compose database container.\n    - [Start or redeploy service database container](/api/endpoints/service-databases/start-service-database-by-service-and-database-uuid): Run docker compose up for a single compose database.\n    - [Stop service database container](/api/endpoints/service-databases/stop-service-database-by-service-and-database-uuid): Stop a compose database container.\n  - Services\n    - [Clone](/api/endpoints/services/clone-service-by-uuid): Clone a service to a destination owned by the authenticated team.\n    - [Create Env](/api/endpoints/services/create-env-by-service-uuid): Create env by service UUID.\n    - [Create service](/api/endpoints/services/create-service): Create a one-click / custom service\n    - [Create Storage](/api/endpoints/services/create-storage-by-service-uuid): Create a persistent storage or file storage for a service sub-resource.\n    - [Create Tag](/api/endpoints/services/create-tag-by-service-uuid): Add tag(s) to a service by UUID.\n    - [Delete Env](/api/endpoints/services/delete-env-by-service-uuid): Delete env by UUID.\n    - [Delete](/api/endpoints/services/delete-service-by-uuid): Delete service by UUID.\n    - [Delete service storage backup schedule](/api/endpoints/services/delete-service-storage-backup-schedule): Delete the backup schedule and its local and S3 archives for a service storage.\n    - [Delete Storage](/api/endpoints/services/delete-storage-by-service-uuid): Delete a persistent storage or file storage by service UUID.\n    - [Delete Tag](/api/endpoints/services/delete-tag-by-service-uuid): Remove a tag from a service by UUID.\n    - [Get](/api/endpoints/services/get-service-by-uuid): Get service by UUID.\n    - [Get service logs.](/api/endpoints/services/get-service-logs-by-uuid): Get logs for a specific service sub-resource by service UUID. The `sub_service_name` query parameter must match the `name` field of one of the service applications or databases returned by `GET /services/{uuid}`.\n    - [List Envs](/api/endpoints/services/list-envs-by-service-uuid): List all envs by service UUID.\n    - [List](/api/endpoints/services/list-services): List all services.\n    - [List Storages](/api/endpoints/services/list-storages-by-service-uuid): List all persistent storages and file storages by service UUID.\n    - [List Tags](/api/endpoints/services/list-tags-by-service-uuid): List tags for a service by UUID.\n    - [Migrate to Server](/api/endpoints/services/migrate-service-by-uuid): Migrate a service to another destination/server owned by the authenticated team. Stops the service, optionally transfers persistent volume data when both servers are managed by Coolify, and updates database records. Redeploy after migration completes.\n    - [Move](/api/endpoints/services/move-service-by-uuid): Move service to another project/environment. This is a purely organizational change — running containers are not affected. Note: after moving, the service will pick up shared environment variables from the new environment on the next deployment.\n    - [Restart](/api/endpoints/services/restart-service-by-uuid): Restart service.\n    - [Run service storage backup](/api/endpoints/services/run-service-storage-backup): Queue an immediate volume backup for a service storage that has a schedule.\n    - [Set service storage backup schedule](/api/endpoints/services/set-service-storage-backup-schedule): Create or replace the backup schedule for a service persistent volume or directory storage.\n    - [Start](/api/endpoints/services/start-service-by-uuid): Start service.\n    - [Stop](/api/endpoints/services/stop-service-by-uuid): Stop service.\n    - [Update Env](/api/endpoints/services/update-env-by-service-uuid): Update env by service UUID.\n    - [Update Envs (Bulk)](/api/endpoints/services/update-envs-by-service-uuid): Update multiple envs by service UUID.\n    - [Update](/api/endpoints/services/update-service-by-uuid): Update service by UUID.\n    - [Update Storage](/api/endpoints/services/update-storage-by-service-uuid): Update a persistent storage or file storage by service UUID.\n  - Shared environment variables\n    - [Create Environment Shared Env](/api/endpoints/shared-environment-variables/create-environment-shared-env): Create a shared environment variable for a project environment (type=environment).\n    - [Create Project Shared Env](/api/endpoints/shared-environment-variables/create-project-shared-env): Create a shared environment variable for a project (type=project).\n    - [Create Server Shared Env](/api/endpoints/shared-environment-variables/create-server-shared-env): Create a shared environment variable for a server (type=server).\n    - [Create Team Shared Env](/api/endpoints/shared-environment-variables/create-team-shared-env): Create a shared environment variable for the current team (type=team).\n    - [Delete Environment Shared Env](/api/endpoints/shared-environment-variables/delete-environment-shared-env): Delete an environment shared environment variable by id.\n    - [Delete Project Shared Env](/api/endpoints/shared-environment-variables/delete-project-shared-env): Delete a project shared environment variable by id.\n    - [Delete Server Shared Env](/api/endpoints/shared-environment-variables/delete-server-shared-env): Delete a server shared environment variable by id.\n    - [Delete Team Shared Env](/api/endpoints/shared-environment-variables/delete-team-shared-env): Delete a team shared environment variable by id.\n    - [List Environment Shared Envs](/api/endpoints/shared-environment-variables/list-environment-shared-envs): List shared environment variables for a project environment (type=environment).\n    - [List Project Shared Envs](/api/endpoints/shared-environment-variables/list-project-shared-envs): List shared environment variables for a project (type=project).\n    - [List Server Shared Envs](/api/endpoints/shared-environment-variables/list-server-shared-envs): List shared environment variables for a server (type=server).\n    - [List Team Shared Envs](/api/endpoints/shared-environment-variables/list-team-shared-envs): List shared environment variables for the current team (type=team).\n    - [Update Environment Shared Env](/api/endpoints/shared-environment-variables/update-environment-shared-env): Update an environment shared environment variable by id.\n    - [Update Project Shared Env](/api/endpoints/shared-environment-variables/update-project-shared-env): Update a project shared environment variable by id.\n    - [Update Server Shared Env](/api/endpoints/shared-environment-variables/update-server-shared-env): Update a server shared environment variable by id.\n    - [Update Team Shared Env](/api/endpoints/shared-environment-variables/update-team-shared-env): Update a team shared environment variable by id.\n  - System\n    - [Disable API](/api/endpoints/system/disable-api): Disable API (only with root permissions).\n    - [Disable MCP Server](/api/endpoints/system/disable-mcp): Disable the MCP server endpoint at /mcp (only with root permissions).\n    - [Enable API](/api/endpoints/system/enable-api): Enable API (only with root permissions).\n    - [Enable MCP Server](/api/endpoints/system/enable-mcp): Enable the MCP server endpoint at /mcp (only with root permissions).\n    - [Healthcheck](/api/endpoints/system/healthcheck): Healthcheck endpoint.\n    - [Version](/api/endpoints/system/version): Get Coolify version.\n  - Tags\n    - [Create](/api/endpoints/tags/create-tag): Create a tag for the current team.\n    - [Delete](/api/endpoints/tags/delete-tag-by-uuid): Delete a tag for the current team. Detaches the tag from all resources via cascade.\n    - [List](/api/endpoints/tags/list-tags): List all tags for the current team.\n    - [Update](/api/endpoints/tags/update-tag-by-uuid): Update a tag name for the current team.\n  - Teams\n    - [Members](/api/endpoints/teams/get-members-by-team-id): Get members by TeamId.\n    - [Get](/api/endpoints/teams/get-team-by-id): Get team by TeamId.\n    - [Authenticated Team Members](/api/endpoints/teams/get-token-team-members): Get members of the team bound to the API token.\n    - [Authenticated Team](/api/endpoints/teams/get-token-team): Get the team bound to the API token.\n    - [List](/api/endpoints/teams/list-teams): Get all teams.\n  - Vultr\n    - [Create Vultr Server](/api/endpoints/vultr/create-vultr-server): Create a Vultr instance and link it as a Coolify server.\n    - [Get Vultr Operating Systems](/api/endpoints/vultr/get-vultr-operating-systems): Get all available Vultr operating systems.\n    - [Get Vultr Plans](/api/endpoints/vultr/get-vultr-plans): Get all available Vultr plans.\n    - [Get Vultr Regions](/api/endpoints/vultr/get-vultr-regions): Get all available Vultr regions.\n    - [Get Vultr SSH Keys](/api/endpoints/vultr/get-vultr-ssh-keys): Get all Vultr SSH keys available to the selected token.\n- Troubleshoot\n  - [Overview](/troubleshoot)\n  - [Overview](/troubleshoot)\n  - Installation\n    - [Coolify Install Script Failed](/troubleshoot/installation/install-script-failed): Debug and fix Coolify installation script failures with step-by-step troubleshooting for logs, Docker issues, port conflicts, and container problems.\n    - [Docker Installation Failed](/troubleshoot/installation/docker-install-failed): Fix Docker installation failures during Coolify setup by using Ubuntu LTS versions or manually installing Docker 24+ on non-LTS operating systems.\n  - Applications\n    - [Bad Gateway Error](/troubleshoot/applications/bad-gateway): Fix Bad Gateway (502) errors in Coolify by checking port configuration, host mapping, listening addresses, and container health.\n    - [No Available Server Error](/troubleshoot/applications/no-available-server): Fix No Available Server (503) errors in Coolify by diagnosing health checks, domain configuration, port mismatches, and Traefik proxy issues.\n    - [Gateway Timeout Errors](/troubleshoot/applications/gateway-timeout): Resolve Gateway Timeout (504) errors in Coolify by fixing network isolation, adjusting proxy timeouts for Traefik, Caddy, and Nginx.\n    - [Failed To Get Access Token During Deployment](/troubleshoot/applications/failed-to-get-token): Fix GitHub access token errors in Coolify deployments caused by NTP time synchronization issues affecting JWT 'iat' claim validation during authentication.\n  - Dashboard\n    - [Dashboard Inaccessible via Instance Domain](/troubleshoot/dashboard/dashboard-inaccessible): Fix Coolify dashboard access issues by checking proxy status, container health, firewall ports, and resolving domain configuration.\n    - [Slow Coolify Dashboard Performance](/troubleshoot/dashboard/dashboard-slow-performance): Resolve slow Coolify dashboard loading by disabling Cloudflare Rocket Loader, checking server location, and optimizing proxy settings for faster performance.\n  - Docker\n    - [Expired GitHub Personal Access Token (PAT)](/troubleshoot/docker/expired-github-personal-access-token): Fix GitHub Container Registry authentication errors by logging out of ghcr.io or renewing expired GitHub Personal Access Tokens for Docker deployments.\n  - Server\n    - [Connection Unstable](/troubleshoot/server/connection-issues): Fix unstable Coolify server connections by removing UFW LIMIT rules, adjusting iptables, and configuring firewall settings for port 22 SSH access.\n    - [Server Crash During Build](/troubleshoot/server/crash-during-build): Fix server crashes during Coolify builds by offloading to external build servers, using GitHub Actions, or upgrading server resources for Docker image builds.\n    - [2FA Stopped Working](/troubleshoot/server/two-factor-stopped-working): Fix two-factor authentication failures in Coolify by synchronizing server time with NTP, checking systemd-timesyncd, and configuring firewall port 123 access.\n    - [Raspberry Pi Crashes](/troubleshoot/server/raspberry-crashes): Fix Raspberry Pi crashes on Coolify by upgrading to 4GB+ RAM or limiting Docker memory usage on 2GB models with slow SD card configurations.\n    - [Server Validation Issues](/troubleshoot/server/validation-issues): Resolve Coolify server validation errors by verifying SSH private key format includes BEGIN and END OPENSSH PRIVATE KEY headers to fix libcrypto errors.\n  - DNS & Domains\n    - [Coolify not using Wildcard SSL Certificates](/troubleshoot/dns-and-domains/wildcard-ssl-certs): Fix wildcard SSL certificate issues in Coolify by verifying installation, checking proxy configuration, and clearing browser cache.\n    - [Let's Encrypt Not Generating SSL Certificates on Coolify](/troubleshoot/dns-and-domains/lets-encrypt-not-working): Fix Let's Encrypt SSL failures by opening ports 80/443, checking DNS records, verifying Cloudflare settings, and troubleshooting challenges.\n    - [Certificate Resolver Not Found on Coolify Proxy](/troubleshoot/dns-and-domains/certificate-resolver-doesnt-exist): Fix Traefik 'letsencrypt cert resolver not found' errors by setting correct acme.json file permissions using chmod 600 for non-root Coolify users."
}