mirror of
https://github.com/Dokploy/website.git
synced 2026-06-15 20:25:25 +02:00
fix: update health check route in rollback and zero downtime documentation
- Changed the health check route in both rollback and zero downtime deployment sections from `/api/health` to `/health` for consistency and accuracy. - Ensured that the documentation reflects the correct endpoint for NodeJS applications, enhancing clarity for users. Close here https://github.com/Dokploy/dokploy/issues/3994
This commit is contained in:
@@ -33,9 +33,9 @@ This method uses Docker Swarm's built-in rollback feature, which automatically r
|
||||
|
||||
### Steps to Configure Automatic Rollback
|
||||
|
||||
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.
|
||||
Let's suppose we have a NodeJS application that has a health check route `/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.
|
||||
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 `/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:
|
||||
@@ -47,7 +47,7 @@ Make sure the API Route exists in your application
|
||||
"CMD",
|
||||
"curl",
|
||||
"-f",
|
||||
"http://localhost:3000/api/health"
|
||||
"http://localhost:3000/health"
|
||||
],
|
||||
"Interval": 30000000000,
|
||||
"Timeout": 10000000000,
|
||||
|
||||
@@ -12,9 +12,9 @@ but Dokploy allows you to configure zero downtime deployments.
|
||||
|
||||
## 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.
|
||||
Let's suppose we have a NodeJS application that has a health check route `/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.
|
||||
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 `/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:
|
||||
@@ -26,7 +26,7 @@ Make sure the API Route exists in your application
|
||||
"CMD",
|
||||
"curl",
|
||||
"-f",
|
||||
"http://localhost:3000/api/health"
|
||||
"http://localhost:3000/health"
|
||||
],
|
||||
"Interval": 30000000000,
|
||||
"Timeout": 10000000000,
|
||||
|
||||
Reference in New Issue
Block a user