docs: add Dokploy self-hosting guide

.optimize-cache.json

@@ -1396,6 +1396,8 @@
   "static/images/docs/advanced/security/dpa.png": "5bfbf7c5654a27d23eeefe49ff70c79861d2734f454c62758978b1a600f1c85d",
   "static/images/docs/advanced/security/mfa-modal.png": "f56b55bcb1ca889597bf8cb803fcabe8b66deaf2f06fd4f49a100d9a507cabef",
   "static/images/docs/advanced/security/mfa.png": "903def2fe311e439851c1ed0b730bb6c88f8b8b32a8ad53152d244fb48b141e5",
+  "static/images/docs/advanced/self-hosting/dokploy/dark/deployed-service.png": "5ea12bd592dcebfa14257989174f1ecbd9cdc704cdfedd35e41ecb89dd668b4e",
+  "static/images/docs/advanced/self-hosting/dokploy/deployed-service.png": "0a4d09ed43507f05c3668723d7df06dfdbe492f9ce23eec2f5cebbb59c871feb",
   "static/images/docs/advanced/self-hosting/installation/dark/wizard-account.png": "b7082787919afe0cb0d7975361356438d798927efda8a47c7471f08b4dd8816a",
   "static/images/docs/advanced/self-hosting/installation/dark/wizard-review.png": "7d4cebea557f02e9e519390b5c16b2d552f641e8dff2c7c89db9851c8887edfa",
   "static/images/docs/advanced/self-hosting/installation/dark/wizard-secure.png": "e558268592865d2ce464e37188b92ff4e1bd54d3c59fd643ad4acac2bcb117ce",

src/routes/docs/advanced/self-hosting/+layout.svelte

@@ -43,6 +43,10 @@
                 {
                     label: 'Coolify',
                     href: '/docs/advanced/self-hosting/platforms/coolify'
+                },
+                {
+                    label: 'Dokploy',
+                    href: '/docs/advanced/self-hosting/platforms/dokploy'
                 }
             ]
         },

src/routes/docs/advanced/self-hosting/+page.markdoc

@@ -111,6 +111,9 @@ Deploy Appwrite on modern PaaS platforms for simplified management:
 {% cards_item href="/docs/advanced/self-hosting/platforms/coolify" title="Coolify" %}
 Open-source platform for easy self-hosting with one-click deployments.
 {% /cards_item %}
+{% cards_item href="/docs/advanced/self-hosting/platforms/dokploy" title="Dokploy" %}
+Open-source deployment platform with one-click Appwrite template deployment.
+{% /cards_item %}
 {% /cards %}
 
 # Configuration {% #configuration %}
@@ -170,4 +173,4 @@ Ready to self-host Appwrite? Choose your preferred path:
 
 **Cloud Platform** - [Choose a cloud platform](#cloud-platforms) for production hosting with custom configuration
 
-**Platform-as-a-Service** - Deploy on [Coolify](/docs/advanced/self-hosting/platforms/coolify) or similar platforms for simplified management
+**Platform-as-a-Service** - Deploy on [Coolify](/docs/advanced/self-hosting/platforms/coolify) or [Dokploy](/docs/advanced/self-hosting/platforms/dokploy) for simplified management

src/routes/docs/advanced/self-hosting/platforms/coolify/+page.markdoc

@@ -56,12 +56,12 @@ To enable email notifications, configure these environment variables:
 _APP_SMTP_HOST=smtp.example.com
 _APP_SMTP_PASSWORD=password
 _APP_SMTP_PORT=587
-_APP_SMTP_SECURE=true
+_APP_SMTP_SECURE=tls
 _APP_SMTP_USERNAME=username
 ```
 
 **GitHub Integration**
-To enable GitHub authentication for your Appwrite console, set these environment variables:
+To connect a GitHub App so Appwrite can build and deploy functions and sites from your GitHub repositories, set these environment variables:
 
 ```bash
 _APP_VCS_GITHUB_APP_ID

src/routes/docs/advanced/self-hosting/platforms/dokploy/+page.markdoc

@@ -0,0 +1,123 @@
+---
+layout: article
+title: Dokploy
+description: Learn how to self-host Appwrite on your infrastructure with Dokploy.
+---
+
+Dokploy is an open-source, self-hosted deployment platform that simplifies application management through an intuitive dashboard and one-click template deployments. Appwrite is available as a template in Dokploy's template catalog, letting you deploy the complete Appwrite stack, including the database, workers, and function executor, in a few clicks. This guide walks you through setting up Appwrite on your Dokploy instance and provides necessary configuration and troubleshooting tips.
+
+# Prerequisites {% #prerequisites %}
+
+Before starting, ensure your server meets the [minimum requirements](/docs/advanced/self-hosting#system-requirements) for hosting Appwrite with Dokploy.
+
+# Installation {% #installation %}
+
+Install Dokploy on your server using the command below:
+
+```bash
+curl -sSL https://dokploy.com/install.sh | sh
+```
+
+Once the installation is complete, open the Dokploy dashboard in your web browser at `http://your-server-ip:3000`.
+
+1. Sign up for a new account.
+2. Click the **Create Project** button to start a new project.
+3. Inside the project, click **Create Service** and select **Template**.
+4. Search for and select **Appwrite** from the template catalog.
+5. Click **Create**, then open the new service and click **Deploy**.
+
+Once the deployment finishes, the **Containers** tab lists every Appwrite service running on your server.
+
+{% only_dark %}
+![Appwrite services running in Dokploy](/images/docs/advanced/self-hosting/dokploy/dark/deployed-service.avif)
+{% /only_dark %}
+{% only_light %}
+![Appwrite services running in Dokploy](/images/docs/advanced/self-hosting/dokploy/deployed-service.avif)
+{% /only_light %}
+
+The template generates secure random secrets and pre-fills the recommended settings, but you can customize them in the **Environment** tab. After deployment completes, access your Appwrite console by opening the main domain from the **Domains** tab and navigating to `/console`.
+
+# Domains and HTTPS {% #domains-https %}
+
+The template configures three domains for your Appwrite instance: the main API/console domain, a `sites.` subdomain, and a `functions.` subdomain. To use your own domain:
+
+1. Point DNS `A` records for your domain and the `sites.` and `functions.` subdomains to your server.
+2. Add wildcard `A` records for `*.sites.your-domain` and `*.functions.your-domain`, which Appwrite uses for site previews and function execution URLs.
+3. Update the hosts in the service's **Domains** tab and the `_APP_DOMAIN`, `_APP_CONSOLE_DOMAIN`, `_APP_DOMAIN_SITES`, and `_APP_DOMAIN_FUNCTIONS` environment variables to match.
+4. For the main domain entries (API, console, and realtime), enable **HTTPS** with the **Let's Encrypt** certificate provider, then redeploy. These are single hosts, so Dokploy issues certificates for them automatically.
+5. The two wildcard domains (`*.sites.your-domain` and `*.functions.your-domain`) need a wildcard certificate you provide — see below.
+
+**Wildcard certificates**
+Dokploy's built-in Let's Encrypt uses the HTTP-01 challenge, which cannot issue wildcard certificates, so the `*.sites` and `*.functions` domains (used for site previews and function execution URLs) need a certificate you supply:
+
+1. Issue a wildcard certificate for `*.sites.your-domain` and `*.functions.your-domain` with a **DNS-01** client such as [lego](https://go-acme.github.io/lego/), acme.sh, or certbot, using your DNS provider's API token. DNS-01 is required — HTTP-01 cannot validate wildcards.
+2. Add the certificate under **Dokploy → Settings → Certificates**.
+3. In the **Domains** tab, set each wildcard domain's certificate provider to **None** (keep HTTPS enabled). This is the step most people miss: if it stays on **Let's Encrypt**, Traefik keeps retrying an impossible wildcard issuance and never serves the certificate you uploaded.
+
+Traefik then serves your uploaded certificate for matching subdomains via SNI.
+
+**Simpler alternative: per-domain certificates**
+If you only need HTTPS on a handful of specific site or function domains — for example a production site on `app.sites.your-domain` or a custom domain — you can skip the wildcard certificate entirely. HTTP-01 can issue a certificate for a specific hostname (just not a wildcard), so:
+
+1. In the service's **Domains** tab, add the exact domain (not a wildcard) with **Port 80**, **HTTPS** enabled, and the **Let's Encrypt** certificate provider.
+2. Redeploy. Dokploy issues a standard certificate for that host, the same way it does for your main domain.
+
+The domain must resolve to your server (the wildcard `A` record already handles this) and be publicly reachable on port 80 for the challenge. This is easier than managing a wildcard certificate, but you repeat it for each domain and it does not cover Appwrite's auto-generated preview subdomains — use the wildcard certificate above if you need every subdomain covered automatically.
+
+{% info title="Using Cloudflare" %}
+Cloudflare's free Universal SSL only covers your apex and first-level wildcard (`*.your-domain`), not second-level wildcards like `*.sites.your-domain`. If these subdomains are proxied (orange cloud), a matching edge certificate requires Cloudflare Advanced Certificate Manager. To avoid that cost, set the `*.sites` and `*.functions` records to **DNS only** (grey cloud) and rely on the Let's Encrypt wildcard certificate above. A Cloudflare **Origin** certificate will not work here — it is only trusted behind Cloudflare's proxy, never by browsers directly.
+{% /info %}
+
+# Configuration {% #configuration %}
+
+Dokploy stores the template's environment variables in the service's **Environment** tab. You can modify these variables and redeploy the service to apply the changes. To enable additional features, you may need to configure some environment variables manually.
+
+**Assistant**
+To enable the assistant, which allows you to generate code snippets and assist with documentation for your Appwrite project, set your OpenAI API key:
+
+```bash
+_APP_ASSISTANT_OPENAI_API_KEY=sk-1234567890
+```
+
+**SMS Notifications**
+To enable SMS-based OTP authentication, configure the following environment variables:
+
+```bash
+_APP_SMS_FROM=123456789
+_APP_SMS_PROVIDER=sms://username:password@mock
+```
+
+**Email Notifications**
+To enable email notifications, configure these environment variables:
+
+```bash
+_APP_SMTP_HOST=smtp.example.com
+_APP_SMTP_PASSWORD=password
+_APP_SMTP_PORT=587
+_APP_SMTP_SECURE=tls
+_APP_SMTP_USERNAME=username
+```
+
+**GitHub Integration**
+To connect a GitHub App so Appwrite can build and deploy functions and sites from your GitHub repositories, set these environment variables:
+
+```bash
+_APP_VCS_GITHUB_APP_ID
+_APP_VCS_GITHUB_APP_NAME
+_APP_VCS_GITHUB_CLIENT_ID
+_APP_VCS_GITHUB_CLIENT_SECRET
+_APP_VCS_GITHUB_PRIVATE_KEY
+```
+
+The [Github Docs](https://docs.github.com/en/apps/creating-github-apps/about-creating-github-apps/about-creating-github-apps) provide more information on configuring your Github app.
+
+# Troubleshooting {% #troubleshooting %}
+
+1. **Sites or function domains return 404**
+   Requests to `<id>.sites.your-domain` require wildcard DNS records (`*.sites.your-domain` and `*.functions.your-domain`) pointing to your server. Verify the records exist and that the `_APP_DOMAIN_SITES` and `_APP_DOMAIN_FUNCTIONS` environment variables match your configured domains.
+
+2. **Browser shows a certificate warning on site subdomains**
+   Generated subdomains need a wildcard certificate, which Dokploy cannot issue automatically. Follow the steps in [Domains and HTTPS](#domains-https) to add one under **Dokploy → Settings → Certificates**.
+
+3. **Only deploy one Appwrite instance per server**
+   The Appwrite template runs its function executor and runtime containers on the shared Docker network, so multiple Appwrite deployments on the same Dokploy server can conflict. Use one Appwrite service per server.