Improve zero downtime (healthcheck) and rollback documentation

apps/docs/content/docs/core/applications/advanced.mdx

@@ -128,9 +128,9 @@ Configure persistent storage for your application to ensure data remains intact
 
 File mounts are a dokploy features, this create a file in a folder called `files` inside your project, so it recreates every single time you deploy your project.
 
-<ImageZoom src="/assets/file-mount-configuration.webp" width={800} height={630} className="rounded-lg"/>
+<ImageZoom alt="file-mount-config-image" src="/assets/file-mount-configuration.webp" width={800} height={630} className="rounded-lg"/>
 
-<ImageZoom src="/assets/file-mount.png" width={800} height={630} className="rounded-lg"/>
+<ImageZoom alt="file-mount-location-image" src="/assets/file-mount.png" width={800} height={630} className="rounded-lg"/>
 
 ### Redirects
 

apps/docs/content/docs/core/applications/going-production.mdx

@@ -3,6 +3,7 @@ title: Going Production
 description: Learn how to deploy your application in production in Dokploy.
 ---
 
+import Link from 'next/link';
 import { Callout } from 'fumadocs-ui/components/callout';
 
 By default, dokploy offer multiple [Builds Types](/docs/core/applications/build-type) to deploy your application, the most common is `nixpacks` and `heroku buildpacks`
@@ -166,48 +167,10 @@ jobs:
 
 You can also use this Github Action [Action](https://github.com/marketplace/actions/dokploy-deployment) to automate the deployment.
 
-## Healthcheck & Rollbacks
+## Zero-downtime (healthcheck)
 
-When using Dokploy you can also configure healthchecks and rollbacks, this will allow you to configure your application to be able to recover from failures.
-
-In the repo we are using from the `Step 1.` we have a healthcheck endpoint `/health` that returns a 200 status code and running in the port 3000.
+Please refer to the <Link href="./zero-downtime">zero documentation</Link>.
 
-Go to `Advanced` Tab and go to Cluster Settings and enter to `Swarm Settings`
+## Rollbacks
 
-There are a couple options that you can use, in this case we will focus on `Health Check` and `Update Config`.
-
-Make sure the API Route exists in your application
-
-```json
-{
-  "Test": [
-    "CMD",
-    "curl",
-    "-f",
-    "http://localhost:3000/health"
-  ],
-  "Interval": 30000000000,
-  "Timeout": 10000000000,
-  "StartPeriod": 30000000000,
-  "Retries": 3
-}
-```
-
-Now in the `Update Config`
-
-Now when the application is getting unhealthy response from the health check, the container will rollback to the previous version.
-
-Paste the following code:
-```json
-{
-  "Parallelism": 1,
-  "Delay": 10000000000,
-  "FailureAction": "rollback",
-  "Order": "start-first"
-}
-```
-
-
-Now you everything a production ready application with automated deployments, zero downtime, rollbacks and healthchecks.
-
-We recommend strongly to use this approach in production since this will make your server never build the application, will only in charge of the deployment keeping your server without any downtime.
+Please refer to the <Link href="./rollbacks">rollbacks documentation</Link>.

apps/docs/content/docs/core/applications/rollbacks.mdx

@@ -3,50 +3,31 @@ title: Rollbacks
 description: Learn how to rollback your application in Dokploy.
 ---
 
-Rollbacks are a powerful feature that allows you to easily revert changes to your application. This is particularly useful when you encounter issues or want to revert to a previous version of your application.
+import Link from 'next/link';
 
+Rollbacks are a powerful feature that allows you to easily revert changes to your application. This is particularly useful when you encounter issues or want to revert to a previous version of your application.
 
 ## Requirements
 
 1. Have a `/health` endpoint in your application.
+2. Configured `Health Check` by following the instructions in the <Link href="./zero-downtime">Zero Downtime Instructions</Link>
 
 ## Steps to Rollback
 
+Suppose we have a NodeJS application running on port 3000 with a health check route `/api/health` that returns a 200 status code.
 
-Let's suppose we have a NodeJS application that has a health check route `/api/health` that returns a 200 status code and running in the port 3000.
-
-1. In your application is necessary to have a `Path` or `Health Route` to be able to achieve zero downtime deployments eg. in the case of a NodeJS app you can have a route `/api/health` that returns a 200 status code.
-2. Go to `Advanced` Tab and go to Cluster Settings and enter to `Swarm Settings`
-3. There are a couple options that you can use, in this case we will focus on `Health Check` and `Update Config`.
-4. Paste this code in the health check field:
-Make sure the API Route exists in your application
-
-```json
-{
-  "Test": [
-    "CMD",
-    "curl",
-    "-f",
-    "http://localhost:3000/api/health"
-  ],
-  "Interval": 30000000000,
-  "Timeout": 10000000000,
-  "StartPeriod": 30000000000,
-  "Retries": 3
-}
-```
-5. Now in the `Update Config`
-
-Now when the application is getting unhealthy response from the health check, the container will rollback to the previous version.
-
-Paste the following code:
-```json
-{
-  "Parallelism": 1,
-  "Delay": 10000000000,
-  "FailureAction": "rollback",
-  "Order": "start-first"
-}
-```
+Assuming you have already set up <Link href="./zero-downtime">healthchecks for your application</Link>, you can additionally configure rollback using the steps below:
 
+1. Go to `Advanced` Tab and go to Cluster Settings and enter to `Swarm Settings`
+2. Locate the `Update Config` section.
+3. Paste the code block below:
+    ```json
+    {
+      "Parallelism": 1,
+      "Delay": 10000000000,
+      "FailureAction": "rollback",
+      "Order": "start-first"
+    }
+    ```
 
+Now, when the application is unhealthy from the health checks, the container will automatically roll back to a previous available version.

apps/docs/content/docs/core/applications/zero-downtime.mdx

@@ -3,62 +3,80 @@ title: Zero Downtime
 description: Learn how to configure zero downtime deployments in Dokploy.
 ---
 
+import Link from 'next/link';
 
-Dokploy allows you to configure zero downtime deployments, which means that you can deploy your application without any downtime.
+By default, when you create a new deployment, it will stop the latest running container and start the new one. This is the default behavior of Docker Swarm and this leads to Bad Gateway since
+the containers are initialized at the same time.
 
-By default when you create a new deployment it will stop the latest running container and start the new one. This is the default behavior of Docker Swarm and this leads to Bad Gateway since
-the containers are initializing at the same time,
-but Dokploy allows you to configure zero downtime deployments.
+Dokploy allows you to configure zero downtime deployments, which means that you can deploy your application without any disruption.
 
 ## Steps to configure Zero Downtime Deployments
 
-Let's suppose we have a NodeJS application that has a health check route `/api/health` that returns a 200 status code and running in the port 3000.
-
-1. In your application is necessary to have a `Path` or `Health Route` to be able to achieve zero downtime deployments eg. in the case of a NodeJS app you can have a route `/api/health` that returns a 200 status code.
-2. Go to `Advanced` Tab and go to Cluster Settings and enter to `Swarm Settings`
-3. There are a couple options that you can use, in this case we will focus on `Health Check`.
-4. Paste this code in the health check field:
-Make sure the API Route exists in your application
-
-```json
-{
-  "Test": [
-    "CMD",
-    "curl",
-    "-f",
-    "http://localhost:3000/api/health"
-  ],
-  "Interval": 30000000000,
-  "Timeout": 10000000000,
-  "StartPeriod": 30000000000,
-  "Retries": 3
-}
-```
+Suppose we have a NodeJS application running on port 3000 with a health check route `/api/health` that returns a 200 status code.
+To enable zero-downtime,
+
+1. Go to the `Advanced` Tab, under Cluster Settings, and click the button `Swarm Settings`
+2. Paste the code below in the `Health Check` field:
+    ```json
+    {
+      "Test": [
+        "CMD",
+        "curl",
+        "--fail",
+        "http://127.0.0.1:3000/api/health"
+      ],
+      "Interval": 30000000000,
+      "Timeout": 10000000000,
+      "StartPeriod": 30000000000,
+      "Retries": 3
+    }
+    ```
+    Note:
+    1. Ensure the API Route exists in your application
+    2. For Dockerfile deployments, ensure that
+        - your host is configured to listen to 127.0.0.1 (or 0.0.0.0). For example, for NextJS Dockerfile, ensure `ENV HOSTNAME=0.0.0.0` is set.
+        - your docker image has `curl` installed - this is not available by default on alpine-based images. Alternatively, you can use wget:
+            ```json
+            "Test": [
+              "CMD",
+              "wget",
+              "--quiet",
+              "--spider",
+              "http://127.0.0.1:3000/api/health"
+            ],
+            ```
+
+Additionally, you are recommended to also configure <Link href="./zero-downtime">rollbacks</Link> for your application in production.
 
 ## Example
 
-1. We will use this example [Github Repo](https://github.com/Dokploy/swarm-test)
-2. It Have a endpoint called `health` [endpoint](https://github.com/Dokploy/swarm-test/blob/main/index.js#L20) which is the one that will tell us if our application is healthy.
-3. For testing purpose I've added a sleep to simulate the delay between the deployments and you can see the bad gateway error.
-
+- We will use this example [Github Repo](https://github.com/Dokploy/swarm-test)
+- It has an endpoint called `/health` [endpoint](https://github.com/Dokploy/swarm-test/blob/main/index.js#L20) which will inform us if our application is healthy
+- For testing purposes, I've invoked a sleep function to simulate delays. This will allow us to see the "Bad Gateway" error between deployments
 
-1. **Use Git Provider in Your Application**:
+**Use Git Provider in Your Application**:
    - Repository: `https://github.com/Dokploy/swarm-test`
    - Branch: `main`
    - Build path: `/`
 
-If you want to test that there is no zero downtime yet, you can simply deploy the application and then create another deployment and while doing the deployment reload the page in the path /health and you will see that a bad gateway will appear.
+To verify that zero downtime deployment is not yet enabled, follow these steps:
+1. Deploy the application.
+2. Initiate another deployment.
+3. While the deployment is in progress, reload the /health page.
+4. You should observe a Bad Gateway error, indicating downtime during the deployment process.
 
-Now go to the advanced section of our application, and go to the Swarm Settings section, we are going to modify the first section of Healtchecks.
-
-We will use this configuration specifically, paste and save it
+To configure health checks for zero downtime.
+1. Go to the `Advanced` tab of the application.
+2. Navigate to `Swarm Settings`.
+3. Locate the `Health Checks` section.
+4. Replace the existing configuration with the following:
 
 ```json
 {
   "Test": [
     "CMD",
     "curl",
-    "-f",
+    "--fail",
     "http://localhost:3000/health"
   ],
   "Interval": 30000000000,
@@ -68,9 +86,12 @@ We will use this configuration specifically, paste and save it
 }
 ```
 
-This configuration basically tells to Docker to do:
-
-Make a request inside the container to http://localhost:3000/health and then we are also saying to make in interval of 30000000000 nanosec, and also makes 3 retries before switching to the new container
+This configuration instructs Docker to:
 
-that would be all, Now you have Zero Downtime Deployments 🎊.
+1. Send a request inside the container to http://127.0.0.1:3000/health.
+2. Perform health checks every 30 seconds (30,000,000,000 nanoseconds).
+3. Wait up to 10 seconds (10,000,000,000 nanoseconds) for a response.
+4. Allow the container 30 seconds (30,000,000,000 nanoseconds) to start before running checks.
+5. Retry the health check 3 times before considering the container unhealthy.
 
+With this setup, new deployments will only replace old containers after the new instance passes health checks, preventing downtime 🎊.