From 979a16bd1651faf59a6c5edd2c01945cebe2465a Mon Sep 17 00:00:00 2001 From: Mauricio Siu Date: Tue, 7 Jul 2026 02:50:23 -0600 Subject: [PATCH] docs: remove Redis from architecture documentation - Updated the architecture documentation to reflect the removal of Redis from the Dokploy setup, ensuring accuracy in the description of the system components. --- apps/docs/content/docs/core/architecture.mdx | 1 - 1 file changed, 1 deletion(-) diff --git a/apps/docs/content/docs/core/architecture.mdx b/apps/docs/content/docs/core/architecture.mdx index c62db7a..652d2b9 100644 --- a/apps/docs/content/docs/core/architecture.mdx +++ b/apps/docs/content/docs/core/architecture.mdx @@ -22,7 +22,6 @@ Each component in the Dokploy architecture plays a vital role: - **Next.js**: Provides a scalable and easy-to-manage frontend framework, encapsulating both server and client-side logic in one platform. This simplifies deployment and development workflows. - **PostgreSQL**: Delivers reliable and secure data storage capabilities. Its use within Dokploy ensures consistency and high performance for all database operations. -- **Redis**: Handles concurrency and job scheduling. By using Redis, Dokploy can efficiently manage deployment tasks, avoiding collisions and server overload during simultaneous operations. - **Traefik**: Enhances Docker integration. Its ability to read from and write to Docker configurations declaratively allows Dokploy to automate and streamline network traffic management and service discovery. This structure ensures that Dokploy is not only efficient in deploying applications but also robust in handling traffic and data at scale.