docs: remove Redis references from architecture and installation documentation

- Updated the architecture documentation to reflect the removal of the Redis database from the Dokploy setup.
- Modified the manual installation guide to eliminate Redis configuration instructions.
- Adjusted troubleshooting documentation to indicate that only three containers should be running, following the removal of Redis.
- Cleaned up the installation script by removing Redis service creation commands.

apps/docs/content/docs/core/architecture.mdx

@@ -14,8 +14,7 @@ When Dokploy is installed, it automatically sets up the following components:
 
 1. **Next.js Application**: Serves as the frontend interface. Utilizing Next.js allows for an integrated server-side rendering experience, streamlining the UI and backend into a single cohesive application.
 2. **PostgreSQL Database**: Acts as the primary database for Dokploy, chosen for its robustness and widespread adoption. It stores all the configuration and operational data.
-3. **Redis Database**: Employed for managing deployment queues. This ensures that multiple deployments do not trigger simultaneously, which could lead to high server load and potential freezing.
-4. **Traefik**: Used as a reverse proxy and load balancer. Traefik facilitates dynamic routing and service discovery which simplifies the configuration process by allowing declarative setup through the UI.
+3. **Traefik**: Used as a reverse proxy and load balancer. Traefik facilitates dynamic routing and service discovery which simplifies the configuration process by allowing declarative setup through the UI.
 
 ## Purpose and Functionality
 

apps/docs/content/docs/core/manual-installation.mdx

@@ -11,8 +11,7 @@ If you wish to customize the Dokploy installation on your server, you can modify
 4. **ADVERTISE_ADDR** - Set to another IP address if you want to use a different IP address for Swarm.
 5. **RELEASE_TAG** - Set to a dokploy docker hub tag(latest, canary, feature, etc)
 6. **DATABASE_URL** - Set to another database url if you want to use a different database.
-7. **REDIS_HOST** - Set to another redis url if you want to use a different redis.
-8. **TZ** - Set to another timezone if you want to use a different timezone.
+7. **TZ** - Set to another timezone if you want to use a different timezone.
 
 ## Installation Script
 
@@ -153,13 +152,6 @@ install_dokploy() {
     --mount type=volume,source=dokploy-postgres,target=/var/lib/postgresql/data \
     postgres:16
 
-    docker service create \
-    --name dokploy-redis \
-    --constraint 'node.role==manager' \
-    --network dokploy-network \
-    --mount type=volume,source=dokploy-redis,target=/data \
-    redis:7
-
     # Installation
     docker service create \
       --name dokploy \

apps/docs/content/docs/core/troubleshooting.mdx

@@ -319,15 +319,18 @@ First, verify the running containers:
 docker ps
 ```
 
-You should see all four of these containers running:
+You should see all three of these containers running:
 ```bash
 2a5b955c32b6   dokploy/dokploy:latest      "docker-entrypoint.s…"   4 days ago     Up 4 days     0.0.0.0:3000->3000/tcp, :::3000->3000/tcp                                                                             dokploy.1.4bkuszk98muz372kw5mvwkw0h
 5a989bf52bc6   postgres:16                 "docker-entrypoint.s…"   4 days ago     Up 4 days     5432/tcp                                                                                                              dokploy-postgres.1.9hvjaxrmby7ex2denjtwo0csf
-a29d56342175   redis:7                     "docker-entrypoint.s…"   4 days ago     Up 4 days     6379/tcp                                                                                                              dokploy-redis.1.epl51a9bt8yr7ur0f1akeeyuk
 05be01c5612f   traefik:v2.5                "/entrypoint.sh trae…"   4 days ago     Up 4 days     0.0.0.0:80->80/tcp, :::80->80/tcp, 0.0.0.0:443->443/tcp, :::443->443/tcp, 0.0.0.0:8080->8080/tcp, :::8080->8080/tcp   dokploy-traefik.1.2oktabjmfu558x2d2dy6czt8m
 ```
 
-If all four containers are running but you still can't access the interface, it's time to debug:
+<Callout type='info'>
+  **Note:** If you're running a version older than v0.29.9, you'll also see a `dokploy-redis` container. Redis is no longer used in self-hosted Dokploy since v0.29.9.
+</Callout>
+
+If all three containers are running but you still can't access the interface, it's time to debug:
 
 ### Debugging Process
 
@@ -337,7 +340,6 @@ Start by examining the logs of each container:
 ```bash
 docker service logs dokploy # Dokploy UI
 docker service logs dokploy-postgres # Postgres
-docker service logs dokploy-redis # Redis
 docker logs dokploy-traefik # Traefik
 ```
 
@@ -464,22 +466,9 @@ In the case you want to recreate the dokploy services, you can do the following:
   **Important:** Before recreating services, make sure you have backups of your data. Recreating services will not delete your volumes, but it's always good to have backups.
 </Callout>
 
-### Recreate Redis Service
+### Recreate Postgres Service
 
-Remove and recreate the dokploy-redis service:
-```bash
-docker service rm dokploy-redis
-
-# Create a new dokploy-redis service
-docker service create \
-  --name dokploy-redis \
-  --constraint 'node.role==manager' \
-  --network dokploy-network \
-  --mount type=volume,source=dokploy-redis,target=/data \
-  redis:7
-```
-
-Remove the dokploy-postgres service:
+Remove and recreate the dokploy-postgres service:
 
 ```bash
 docker service rm dokploy-postgres
@@ -502,6 +491,8 @@ docker service create \
 </Callout>
 
 
+### Recreate Traefik Service
+
 Remove the dokploy-traefik service:
 
 ```bash