mirror/coolify-docs
1
0
Fork 0
mirror of https://github.com/coollabsio/coolify-docs.git synced 2026-06-19 07:35:55 +00:00
Code Issues Packages Projects Releases Wiki Activity

fix(docs): use accordion components

Browse Source
This commit is contained in:
ShadowArcanist
2026-05-11 07:41:53 +05:30
parent 8008d5006d
commit 96d8d3e4d1
17 changed files with 241 additions and 166 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/docs/applications/build-packs/docker-compose.mdx
+4 -3
View File
@@ -230,9 +230,9 @@ If build cache is not being preserved between deployments, ensure "Include Sourc
## Known Issues and Solutions
<Accordions type="multiple">
<details>
<summary>1. Visiting the Application Domain Shows "No Available Server"</summary>
<Accordion title="1. Visiting the Application Domain Shows &quot;No Available Server&quot;">
If you see a "No Available Server" error when visiting your website, it is likely due to the health check for your container.
@@ -240,5 +240,6 @@ Run `docker ps` on your server terminal to check if your container is unhealthy
To resolve this, fix the issue causing the container to be unhealthy or remove the health checks.
</details>
</Accordion>
</Accordions>
content/docs/applications/build-packs/dockerfile.mdx
+6 -8
View File
@@ -107,9 +107,9 @@ A plain Node.js process only uses one CPU core. To make a Node.js (or Bun) app u
## Known Issues and Solutions
<Accordions type="multiple">
<details>
<summary>1. Visiting the Application Domain Shows "No Available Server"</summary>
<Accordion title="1. Visiting the Application Domain Shows &quot;No Available Server&quot;">
If you see a "No Available Server" error when visiting your website, it is likely due to the health check for your container.
@@ -117,12 +117,9 @@ Run `docker ps` on your server terminal to check if your container is unhealthy
To resolve this, fix the issue causing the container to be unhealthy or remove the health checks.
</details>
</Accordion>
<details>
<summary>2. App only works inside the Container</summary>
<Accordion title="2. App only works inside the Container">
If your app works when you check it with a `curl localhost` inside the container but you receive a 404 or "No Available Server" error when accessing your domain, verify the port settings.
@@ -132,5 +129,6 @@ Make sure that the port in the network settings matches the port where your appl
If needed, change it to listen on all interfaces (for example, `0.0.0.0`).
</details>
</Accordion>
</Accordions>
content/docs/get-started/cloud.mdx
+36 -63
View File
@@ -41,9 +41,9 @@ Coolify Cloud uses the same open-source codebase, so there are no locked-behind-
4. **Connect Your Servers**
<Accordions type="multiple">
<details>
<summary>Detailed Server Connection Guide</summary>
<Accordion title="Detailed Server Connection Guide">
1. **Add Private Key:** Login to your Coolify account (or create one if you’re new) and Add a new private key
<ZoomImage src="/docs/images/resources/screenshots/6.webp" alt="Coolify dashboard screenshot" />
@@ -61,8 +61,9 @@ Coolify Cloud uses the same open-source codebase, so there are no locked-behind-
4. **Check Status:** Once finished, you should see a green **Proxy Running** status indicating everything is set up.
<ZoomImage src="/docs/images/resources/screenshots/11.webp" alt="Coolify dashboard screenshot" />
</details>
</Accordion>
</Accordions>
5. **Deploy Your Applications**
@@ -95,29 +96,25 @@ The idea came to Andras (Coolify's Founder) as a way to offer a “**paid option
## Frequently Asked Questions
<Accordions type="multiple">
<details>
<summary>1. Do I get any Cloud-only features?</summary>
<Accordion title="1. Do I get any Cloud-only features?">
No. Coolify Cloud and self-hosted Coolify share the same feature set.
Cloud’s value lies in automatic backups, email notifications, scaling, and update testing handled for you.
</details>
</Accordion>
<details>
<summary>2. Does Coolify Cloud back up my application data?</summary>
<Accordion title="2. Does Coolify Cloud back up my application data?">
No, Coolify Cloud only backs up the Coolify database (e.g., dashboard settings).
You are responsible for backing up any databases or storage volumes on your servers.
</details>
</Accordion>
<details>
<summary>3. Can I import my self-hosted Coolify configurations to Coolify Cloud?</summary>
<Accordion title="3. Can I import my self-hosted Coolify configurations to Coolify Cloud?">
No.
@@ -125,27 +122,21 @@ To transfer configurations, you'll need to back up the database from your self-h
However, since you don’t have access to the database in Coolify Cloud, it’s not possible to migrate data or settings directly to the cloud version.
</details>
</Accordion>
<details>
<summary>4. How often Coolify Cloud is backed up?</summary>
<Accordion title="4. How often Coolify Cloud is backed up?">
Every 24 hours
</details>
</Accordion>
<details>
<summary>5. Is Coolify Cloud really based on the open-source version of Coolify?</summary>
<Accordion title="5. Is Coolify Cloud really based on the open-source version of Coolify?">
Yes, Coolify Cloud uses the same open-source codebase as the self-hosted version. There are no paywall features, and the Cloud service is simply a managed experience for convenience.
</details>
</Accordion>
<details>
<summary>6. What happens if I cancel my Coolify Cloud subscription?</summary>
<Accordion title="6. What happens if I cancel my Coolify Cloud subscription?">
If you cancel your subscription, you will stop being billed, and your access to Coolify Cloud will be suspended at the end of your current billing cycle.
@@ -153,11 +144,9 @@ However, your servers will remain unaffected, and all of your applications will
Since your server will still be hosting your applications with a reverse proxy handling incoming requests, there will be no interruptions.
</details>
</Accordion>
<details>
<summary>7. What happens if I forget to pay an invoice?</summary>
<Accordion title="7. What happens if I forget to pay an invoice?">
If a payment fails or an invoice is missed, your subscription and access to Coolify Cloud will be temporarily paused until the payment is successfully processed.
@@ -167,12 +156,9 @@ Once the payment is made, your Coolify Cloud access will be restored, and all yo
Your servers will also stay up and running, and your applications will continue to function normally, as everything is still hosted on your own server with a reverse proxy.
</details>
</Accordion>
<details>
<summary>8. Are there any IP addresses I need to whitelist for Coolify Cloud?</summary>
<Accordion title="8. Are there any IP addresses I need to whitelist for Coolify Cloud?">
Yes, Coolify Cloud uses specific IP addresses.
@@ -180,11 +166,9 @@ You can find the list of IPs [here](https://coolify.io/docs/knowledge-base/faq#c
The main requirement is that Coolify Cloud needs to access your server's SSH port.
</details>
</Accordion>
<details>
<summary>9. Do I need to bring my own servers to Coolify Cloud?</summary>
<Accordion title="9. Do I need to bring my own servers to Coolify Cloud?">
Yes, when using Coolify Cloud, you must provide your own servers (e.g., VPS, Raspberry Pi, EC2, etc.).
@@ -192,11 +176,9 @@ Coolify Cloud manages Coolify on our infrastructure, but we don’t provide the
This approach allows you to choose the hardware that best fits your needs.
</details>
</Accordion>
<details>
<summary>10. Why do I have to pay for Coolify Cloud if I’m bringing my own servers?</summary>
<Accordion title="10. Why do I have to pay for Coolify Cloud if I’m bringing my own servers?">
While you bring your own servers, the subscription fee for Coolify Cloud covers the managed service aspect.
@@ -204,19 +186,15 @@ This includes infrastructure management, maintenance, support, updates, and scal
We take care of the heavy lifting to ensure everything runs smoothly.
</details>
</Accordion>
<details>
<summary>11. What happens if I exceed the number of connected servers?</summary>
<Accordion title="11. What happens if I exceed the number of connected servers?">
You won’t be able to add extra servers to Coolify cloud unless your subscription is upgraded.
</details>
</Accordion>
<details>
<summary>12. Is there a trial period for Coolify Cloud?</summary>
<Accordion title="12. Is there a trial period for Coolify Cloud?">
Currently, Coolify Cloud doesn’t offer a free trial. However, the subscription is affordable—just **$5 per month** for up to two connected servers.
@@ -224,19 +202,15 @@ If you want to explore all the features, you can run Coolify on a small Linux se
Since both cloud and self-hosted versions use the same codebase, you’ll be able to test all the features without any limitations.
</details>
</Accordion>
<details>
<summary>13. Can I get any discounts?</summary>
<Accordion title="13. Can I get any discounts?">
The current **$5/month** subscription rate is already quite affordable, so discounts are not available at the moment.
</details>
</Accordion>
<details>
<summary>14. I have to pay to use Coolify Cloud, so doesn't that mean I'm locked into a vendor?</summary>
<Accordion title="14. I have to pay to use Coolify Cloud, so doesn't that mean I'm locked into a vendor?">
**Not really.**
@@ -246,11 +220,9 @@ You can connect your own server, so you retain full control. Everything runs as
In a true vendor lock-in, your apps would stop if you stop paying, but that’s not the case with Coolify Cloud.
</details>
</Accordion>
<details>
<summary>15. Can I access the Coolify Cloud dashboard on my own domain?</summary>
<Accordion title="15. Can I access the Coolify Cloud dashboard on my own domain?">
No.
@@ -258,5 +230,6 @@ The Coolify Cloud dashboard is only available at https://app.coolify.io.
If you’d like to access the dashboard on your own domain, you’ll need to self-host Coolify.
</details>
</Accordion>
</Accordions>
content/docs/get-started/contribute/coolify.mdx
+10 -9
View File
@@ -27,8 +27,9 @@ To understand the tech stack, please refer to the [Tech Stack](https://github.co
## 1. Setup Development Environment
Follow the steps below for your operating system:
<details>
<summary><strong>Windows</strong></summary>
<Accordions type="multiple">
<Accordion title="Windows">
1. Install `docker-ce`, Docker Desktop (or similar):
- Docker CE (recommended):
@@ -42,10 +43,9 @@ Follow the steps below for your operating system:
2. Install Spin:
- Follow the instructions to install Spin on Windows from the [Spin documentation](https://serversideup.net/open-source/spin/docs/installation/install-windows#download-and-install-spin-into-wsl2?ref=coolify)
</details>
</Accordion>
<details>
<summary><strong>MacOS</strong></summary>
<Accordion title="MacOS">
1. Install Orbstack, Docker Desktop (or similar):
- Orbstack (recommended, as it is a faster and lighter alternative to Docker Desktop):
@@ -56,10 +56,9 @@ Follow the steps below for your operating system:
2. Install Spin:
- Follow the instructions to install Spin on MacOS from the [Spin documentation](https://serversideup.net/open-source/spin/docs/installation/install-macos/#download-and-install-spin?ref=coolify)
</details>
</Accordion>
<details>
<summary><strong>Linux</strong></summary>
<Accordion title="Linux">
1. Install Docker Engine, Docker Desktop (or similar):
- Docker Engine (recommended, as there is no VM overhead):
@@ -70,7 +69,9 @@ Follow the steps below for your operating system:
2. Install Spin:
- Follow the instructions to install Spin on Linux from the [Spin documentation](https://serversideup.net/open-source/spin/docs/installation/install-linux#configure-docker-permissions?ref=coolify)
</details>
</Accordion>
</Accordions>
## 2. Verify Installation (Optional)
content/docs/get-started/installation.mdx
+4 -5
View File
@@ -204,10 +204,9 @@ curl -fsSL https://cdn.coollabs.io/coolify/install.sh | sudo bash
The installation script supports several environment variables to customize your Coolify installation. These are completely optional.
<Accordions type="multiple">
<details>
<summary>Click to view all available environment variables</summary>
<Accordion title="Click to view all available environment variables">
You can set these environment variables before running the installation script to customize your Coolify setup:
@@ -272,9 +271,9 @@ DOCKER_ADDRESS_POOL_BASE=172.16.0.0/12 \
bash -c 'curl -fsSL https://cdn.coollabs.io/coolify/install.sh | bash'
```
</Accordion>
</details>
</Accordions>
#### 3. Access Coolify
content/docs/knowledge-base/s3/aws.mdx
+6 -5
View File
@@ -38,9 +38,9 @@ The following data is used as an example in this guide. Please replace it with y
---
<Accordions type="multiple">
<details>
<summary>TLDR (click to view)</summary>
<Accordion title="TLDR (click to view)">
1. Create a bucket in AWS Console
2. Create a custom policy in AWS Console with the following permissions:
@@ -80,6 +80,10 @@ The following data is used as an example in this guide. Please replace it with y
</Callout>
</Accordion>
</Accordions>
## 1. Create a S3 Bucket
To create your S3 Bucket, follow these steps:
@@ -246,6 +250,3 @@ You can see the backups stored on your S3 from the execution logs:
<ZoomImage src="/docs/images/aws-s3/25.webp" alt="Screenshot of Aws" />
Now you’re done! Your Coolify instance is set up to automatically backup and store them on your Aws S3 bucket safely.
</details>
content/docs/knowledge-base/server/patching.mdx
+6 -8
View File
@@ -71,9 +71,9 @@ If you'd like to prioritize support for a specific package manager, feel free to
## FAQ
<Accordions type="multiple">
<details>
<summary>1. Can I change how frequently Coolify checks for updates?</summary>
<Accordion title="1. Can I change how frequently Coolify checks for updates?">
No, the update check interval is currently fixed.
@@ -81,16 +81,14 @@ However, you can manually trigger a check by clicking the **Check now** button o
This feature was introduced in **v4.0.0-beta.419**, and we’re focusing on improving it based on user feedback. If you'd like to request customizable check intervals, feel free to start a discussion here: [Coolify Discussions on GitHub](https://github.com/coollabsio/coolify/discussions)
</details>
</Accordion>
<details>
<summary>2. Does Coolify install updates automatically?</summary>
<Accordion title="2. Does Coolify install updates automatically?">
**No**, Coolify does not install updates automatically.
Updates are only applied when you manually click the **Update** or **Update all packages** button on the dashboard.
</details>
</Accordion>
</Accordions>
content/docs/troubleshoot/dns-and-domains/lets-encrypt-not-working.mdx
+8 -6
View File
@@ -50,9 +50,9 @@ If the certificates stored on your server are corrupted or outdated, you can del
rm /data/coolify/proxy/acme.json
```
- Then, restart the Coolify proxy from the dashboard by clicking the Restart Proxy button.
<Accordions type="multiple">
<details>
<summary>Guide: How to Restart Proxy from Dashboard?</summary>
<Accordion title="Guide: How to Restart Proxy from Dashboard?">
1. Select your server on the Coolify Dashboard
@@ -61,8 +61,9 @@ If the certificates stored on your server are corrupted or outdated, you can del
2. Click on Restart Proxy button
<ZoomImage src="/docs/images/troubleshoot/dns-and-domains/lets-encrypt-not-working/2.webp" alt="Screenshot showing Lets Encrypt Not Working" />
</details>
</Accordion>
</Accordions>
## 7. Check Your WAF Settings
@@ -77,9 +78,9 @@ On the Coolify proxy logs check for error messages.
- In this case, wait for a while and check your domain again. Most users won't encounter this, but it can happen if you are using a shared IP address.
- If you see an error message with a 403 status code, it means that requests from Let's Encrypt are blocked by something like a Web Application Firewall (WAF).
<Accordions type="multiple">
<details>
<summary>Guide: How to check Coolify proxy logs?</summary>
<Accordion title="Guide: How to check Coolify proxy logs?">
1. Select your server on the Coolify Dashboard
@@ -88,8 +89,9 @@ On the Coolify proxy logs check for error messages.
2. Go to the proxy section and click the refresh button
<ZoomImage src="/docs/images/troubleshoot/dns-and-domains/lets-encrypt-not-working/3.webp" alt="Screenshot showing Lets Encrypt Not Working" />
</details>
</Accordion>
</Accordions>
## 9. Verify DNS Records
docs/applications/build-packs/docker-compose.md
+8 -2
View File
@@ -218,10 +218,16 @@ If build cache is not being preserved between deployments, ensure "Include Sourc
## Known Issues and Solutions
::: details 1. Visiting the Application Domain Shows "No Available Server"
<Accordions type="multiple">
<Accordion title="1. Visiting the Application Domain Shows &quot;No Available Server&quot;">
If you see a "No Available Server" error when visiting your website, it is likely due to the health check for your container.
Run `docker ps` on your server terminal to check if your container is unhealthy or still starting.
To resolve this, fix the issue causing the container to be unhealthy or remove the health checks.
:::
</Accordion>
</Accordions>
docs/applications/build-packs/dockerfile.md
+12 -4
View File
@@ -103,15 +103,20 @@ A plain Node.js process only uses one CPU core. To make a Node.js (or Bun) app u
## Known Issues and Solutions
::: details 1. Visiting the Application Domain Shows "No Available Server"
<Accordions type="multiple">
<Accordion title="1. Visiting the Application Domain Shows &quot;No Available Server&quot;">
If you see a "No Available Server" error when visiting your website, it is likely due to the health check for your container.
Run `docker ps` on your server terminal to check if your container is unhealthy or still starting.
To resolve this, fix the issue causing the container to be unhealthy or remove the health checks.
:::
::: details 2. App only works inside the Container
</Accordion>
<Accordion title="2. App only works inside the Container">
If your app works when you check it with a `curl localhost` inside the container but you receive a 404 or "No Available Server" error when accessing your domain, verify the port settings.
Make sure that the port in the network settings matches the port where your application is listening. Also, check the startup log to ensure the application is not only listening on localhost.
@@ -119,4 +124,7 @@ Make sure that the port in the network settings matches the port where your appl
<ZoomableImage src="/docs/images/builds/packs/dockerfile/9.webp" alt="Coolify dashboard screenshot" />
If needed, change it to listen on all interfaces (for example, `0.0.0.0`).
:::
</Accordion>
</Accordions>
docs/get-started/cloud.md
+85 -32
View File
@@ -41,7 +41,10 @@ Coolify Cloud uses the same open-source codebase, so there are no locked-behind-
4. **Connect Your Servers**
- ::: details Detailed Server Connection Guide
<Accordions type="multiple">
<Accordion title="Detailed Server Connection Guide">
1. **Add Private Key:** Login to your Coolify account (or create one if you’re new) and Add a new private key
<ZoomableImage src="/docs/images/resources/screenshots/6.webp" alt="Coolify dashboard screenshot" />
<br />
@@ -57,7 +60,10 @@ Coolify Cloud uses the same open-source codebase, so there are no locked-behind-
***
4. **Check Status:** Once finished, you should see a green **Proxy Running** status indicating everything is set up.
<ZoomableImage src="/docs/images/resources/screenshots/11.webp" alt="Coolify dashboard screenshot" />
:::
</Accordion>
</Accordions>
5. **Deploy Your Applications**
@@ -90,37 +96,58 @@ The idea came to Andras (Coolify's Founder) as a way to offer a “**paid option
## Frequently Asked Questions
::: details 1. Do I get any Cloud-only features?
<Accordions type="multiple">
<Accordion title="1. Do I get any Cloud-only features?">
No. Coolify Cloud and self-hosted Coolify share the same feature set.
Cloud’s value lies in automatic backups, email notifications, scaling, and update testing handled for you.
:::
::: details 2. Does Coolify Cloud back up my application data?
</Accordion>
<Accordion title="2. Does Coolify Cloud back up my application data?">
No, Coolify Cloud only backs up the Coolify database (e.g., dashboard settings).
You are responsible for backing up any databases or storage volumes on your servers.
:::
::: details 3. Can I import my self-hosted Coolify configurations to Coolify Cloud?
</Accordion>
<Accordion title="3. Can I import my self-hosted Coolify configurations to Coolify Cloud?">
No.
To transfer configurations, you'll need to back up the database from your self-hosted instance and restore it to a new Coolify instance.
However, since you don’t have access to the database in Coolify Cloud, it’s not possible to migrate data or settings directly to the cloud version.
:::
::: details 4. How often Coolify Cloud is backed up?
</Accordion>
<Accordion title="4. How often Coolify Cloud is backed up?">
Every 24 hours
:::
::: details 5. Is Coolify Cloud really based on the open-source version of Coolify?
</Accordion>
<Accordion title="5. Is Coolify Cloud really based on the open-source version of Coolify?">
Yes, Coolify Cloud uses the same open-source codebase as the self-hosted version. There are no paywall features, and the Cloud service is simply a managed experience for convenience.
:::
::: details 6. What happens if I cancel my Coolify Cloud subscription?
</Accordion>
<Accordion title="6. What happens if I cancel my Coolify Cloud subscription?">
If you cancel your subscription, you will stop being billed, and your access to Coolify Cloud will be suspended at the end of your current billing cycle.
However, your servers will remain unaffected, and all of your applications will continue running as normal.
Since your server will still be hosting your applications with a reverse proxy handling incoming requests, there will be no interruptions.
:::
::: details 7. What happens if I forget to pay an invoice?
</Accordion>
<Accordion title="7. What happens if I forget to pay an invoice?">
If a payment fails or an invoice is missed, your subscription and access to Coolify Cloud will be temporarily paused until the payment is successfully processed.
You will receive an email notification about the failed payment.
@@ -128,43 +155,63 @@ You will receive an email notification about the failed payment.
Once the payment is made, your Coolify Cloud access will be restored, and all your settings will remain intact—there’s no data loss.
Your servers will also stay up and running, and your applications will continue to function normally, as everything is still hosted on your own server with a reverse proxy.
:::
::: details 8. Are there any IP addresses I need to whitelist for Coolify Cloud?
</Accordion>
<Accordion title="8. Are there any IP addresses I need to whitelist for Coolify Cloud?">
Yes, Coolify Cloud uses specific IP addresses.
You can find the list of IPs [here](https://coolify.io/docs/knowledge-base/faq#coolify-cloud-public-ips).
The main requirement is that Coolify Cloud needs to access your server's SSH port.
:::
::: details 9. Do I need to bring my own servers to Coolify Cloud?
</Accordion>
<Accordion title="9. Do I need to bring my own servers to Coolify Cloud?">
Yes, when using Coolify Cloud, you must provide your own servers (e.g., VPS, Raspberry Pi, EC2, etc.).
Coolify Cloud manages Coolify on our infrastructure, but we don’t provide the servers themselves.
This approach allows you to choose the hardware that best fits your needs.
:::
::: details 10. Why do I have to pay for Coolify Cloud if I’m bringing my own servers?
</Accordion>
<Accordion title="10. Why do I have to pay for Coolify Cloud if I’m bringing my own servers?">
While you bring your own servers, the subscription fee for Coolify Cloud covers the managed service aspect.
This includes infrastructure management, maintenance, support, updates, and scaling, so you don’t have to worry about technical aspects like monitoring, patching, or backups for Coolify.
We take care of the heavy lifting to ensure everything runs smoothly.
:::
::: details 11. What happens if I exceed the number of connected servers?
</Accordion>
<Accordion title="11. What happens if I exceed the number of connected servers?">
You won’t be able to add extra servers to Coolify cloud unless your subscription is upgraded.
:::
::: details 12. Is there a trial period for Coolify Cloud?
</Accordion>
<Accordion title="12. Is there a trial period for Coolify Cloud?">
Currently, Coolify Cloud doesn’t offer a free trial. However, the subscription is affordable—just **$5 per month** for up to two connected servers.
If you want to explore all the features, you can run Coolify on a small Linux server or a VM on your PC by following the [self-hosted installation guide](https://coolify.io/docs/get-started/installation).
Since both cloud and self-hosted versions use the same codebase, you’ll be able to test all the features without any limitations.
:::
::: details 13. Can I get any discounts?
</Accordion>
<Accordion title="13. Can I get any discounts?">
The current **$5/month** subscription rate is already quite affordable, so discounts are not available at the moment.
:::
::: details 14. I have to pay to use Coolify Cloud, so doesn't that mean I'm locked into a vendor?
</Accordion>
<Accordion title="14. I have to pay to use Coolify Cloud, so doesn't that mean I'm locked into a vendor?">
**Not really.**
You're paying for the managed Coolify instance, but stopping the use of Coolify Cloud won't affect your applications.
@@ -172,11 +219,17 @@ You're paying for the managed Coolify instance, but stopping the use of Coolify
You can connect your own server, so you retain full control. Everything runs as a Docker container, and Coolify will install a reverse proxy on your server to ensure everything works smoothly without needing Coolify Cloud.
In a true vendor lock-in, your apps would stop if you stop paying, but that’s not the case with Coolify Cloud.
:::
::: details 15. Can I access the Coolify Cloud dashboard on my own domain?
</Accordion>
<Accordion title="15. Can I access the Coolify Cloud dashboard on my own domain?">
No.
The Coolify Cloud dashboard is only available at https://app.coolify.io.
If you’d like to access the dashboard on your own domain, you’ll need to self-host Coolify.
:::
</Accordion>
</Accordions>
docs/get-started/contribute/coolify.md
+10 -9
View File
@@ -27,8 +27,9 @@ To understand the tech stack, please refer to the [Tech Stack](https://github.co
## 1. Setup Development Environment
Follow the steps below for your operating system:
<details>
<summary><strong>Windows</strong></summary>
<Accordions type="multiple">
<Accordion title="Windows">
1. Install `docker-ce`, Docker Desktop (or similar):
- Docker CE (recommended):
@@ -42,10 +43,9 @@ Follow the steps below for your operating system:
2. Install Spin:
- Follow the instructions to install Spin on Windows from the [Spin documentation](https://serversideup.net/open-source/spin/docs/installation/install-windows#download-and-install-spin-into-wsl2?ref=coolify)
</details>
</Accordion>
<details>
<summary><strong>MacOS</strong></summary>
<Accordion title="MacOS">
1. Install Orbstack, Docker Desktop (or similar):
- Orbstack (recommended, as it is a faster and lighter alternative to Docker Desktop):
@@ -56,10 +56,9 @@ Follow the steps below for your operating system:
2. Install Spin:
- Follow the instructions to install Spin on MacOS from the [Spin documentation](https://serversideup.net/open-source/spin/docs/installation/install-macos/#download-and-install-spin?ref=coolify)
</details>
</Accordion>
<details>
<summary><strong>Linux</strong></summary>
<Accordion title="Linux">
1. Install Docker Engine, Docker Desktop (or similar):
- Docker Engine (recommended, as there is no VM overhead):
@@ -70,7 +69,9 @@ Follow the steps below for your operating system:
2. Install Spin:
- Follow the instructions to install Spin on Linux from the [Spin documentation](https://serversideup.net/open-source/spin/docs/installation/install-linux#configure-docker-permissions?ref=coolify)
</details>
</Accordion>
</Accordions>
## 2. Verify Installation (Optional)
docs/get-started/installation.md
+6 -2
View File
@@ -168,7 +168,9 @@ curl -fsSL https://cdn.coollabs.io/coolify/install.sh | sudo bash
The installation script supports several environment variables to customize your Coolify installation. These are completely optional.
:::details Click to view all available environment variables
<Accordions type="multiple">
<Accordion title="Click to view all available environment variables">
You can set these environment variables before running the installation script to customize your Coolify setup:
@@ -233,7 +235,9 @@ DOCKER_ADDRESS_POOL_BASE=172.16.0.0/12 \
bash -c 'curl -fsSL https://cdn.coollabs.io/coolify/install.sh | bash'
```
:::
</Accordion>
</Accordions>
#### 3. Access Coolify
docs/knowledge-base/s3/aws.md
+9 -2
View File
@@ -34,7 +34,10 @@ The following data is used as an example in this guide. Please replace it with y
---
::: details TLDR (click to view)
<Accordions type="multiple">
<Accordion title="TLDR (click to view)">
1. Create a bucket in AWS Console
2. Create a custom policy in AWS Console with the following permissions:
@@ -67,7 +70,11 @@ The following data is used as an example in this guide. Please replace it with y
5. Add the `Access Key` and `Secret Key` in Coolify when you create a new S3 source.
::: success Tip
You need to use the S3 HTTP endpoint without the bucket name, for example,`https://s3.eu-central-1.amazonaws.com`.
:::
:::
</Accordion>
</Accordions>
## 1. Create a S3 Bucket
docs/knowledge-base/server/patching.md
+12 -4
View File
@@ -59,16 +59,24 @@ If you'd like to prioritize support for a specific package manager, feel free to
## FAQ
::: details 1. Can I change how frequently Coolify checks for updates?
<Accordions type="multiple">
<Accordion title="1. Can I change how frequently Coolify checks for updates?">
No, the update check interval is currently fixed.
However, you can manually trigger a check by clicking the **Check now** button on the Server Patching page.
This feature was introduced in **v4.0.0-beta.419**, and we’re focusing on improving it based on user feedback. If you'd like to request customizable check intervals, feel free to start a discussion here: [Coolify Discussions on GitHub](https://github.com/coollabsio/coolify/discussions)
:::
::: details 2. Does Coolify install updates automatically?
</Accordion>
<Accordion title="2. Does Coolify install updates automatically?">
**No**, Coolify does not install updates automatically.
Updates are only applied when you manually click the **Update** or **Update all packages** button on the dashboard.
:::
</Accordion>
</Accordions>
docs/troubleshoot/dns-and-domains/lets-encrypt-not-working.md
+16 -4
View File
@@ -50,14 +50,20 @@ If the certificates stored on your server are corrupted or outdated, you can del
rm /data/coolify/proxy/acme.json
```
- Then, restart the Coolify proxy from the dashboard by clicking the Restart Proxy button.
::: details Guide: How to Restart Proxy from Dashboard?
<Accordions type="multiple">
<Accordion title="Guide: How to Restart Proxy from Dashboard?">
1. Select your server on the Coolify Dashboard
<ZoomableImage src="/docs/images/troubleshoot/dns-and-domains/lets-encrypt-not-working/1.webp" alt="Screenshot showing Lets Encrypt Not Working" />
2. Click on Restart Proxy button
<ZoomableImage src="/docs/images/troubleshoot/dns-and-domains/lets-encrypt-not-working/2.webp" alt="Screenshot showing Lets Encrypt Not Working" />
:::
</Accordion>
</Accordions>
## 7. Check Your WAF Settings
@@ -72,14 +78,20 @@ On the Coolify proxy logs check for error messages.
- In this case, wait for a while and check your domain again. Most users won't encounter this, but it can happen if you are using a shared IP address.
- If you see an error message with a 403 status code, it means that requests from Let's Encrypt are blocked by something like a Web Application Firewall (WAF).
::: details Guide: How to check Coolify proxy logs?
<Accordions type="multiple">
<Accordion title="Guide: How to check Coolify proxy logs?">
1. Select your server on the Coolify Dashboard
<ZoomableImage src="/docs/images/troubleshoot/dns-and-domains/lets-encrypt-not-working/1.webp" alt="Screenshot showing Lets Encrypt Not Working" />
2. Go to the proxy section and click the refresh button
<ZoomableImage src="/docs/images/troubleshoot/dns-and-domains/lets-encrypt-not-working/3.webp" alt="Screenshot showing Lets Encrypt Not Working" />
:::
</Accordion>
</Accordions>
## 9. Verify DNS Records
src/components/mdx.tsx
+3
View File
@@ -1,4 +1,5 @@
import defaultMdxComponents from 'fumadocs-ui/mdx';
import { Accordion, Accordions } from 'fumadocs-ui/components/accordion';
import { Callout } from 'fumadocs-ui/components/callout';
import { Card, Cards } from 'fumadocs-ui/components/card';
import { File, Files, Folder } from 'fumadocs-ui/components/files';
@@ -23,6 +24,8 @@ function Badge({ text, children }: { type?: string; text?: string; children?: Re
export function getMDXComponents(components?: MDXComponents) {
return {
...defaultMdxComponents,
Accordion,
Accordions,
Badge,
Callout,
Card,