korbit-ai[bot] commented on code in PR #34324:
URL: https://github.com/apache/superset/pull/34324#discussion_r2232099072


##########
docs/docs/installation/docker-compose.mdx:
##########
@@ -103,13 +106,36 @@ and help you start fresh. In the context of `docker 
compose` setting
 from within docker. This will slow down the startup, but will fix various 
npm-related issues.
 :::
 
-### Option #2 - build a set of immutable images from the local branch
+### Option #2 - lightweight development with multiple instances
+
+For a lighter development setup that uses fewer resources and supports running 
multiple instances:
+
+```bash
+# Single lightweight instance (default port 9001)
+docker compose -f docker-compose-light.yml up
+
+# Multiple instances with different ports
+NODE_PORT=9001 docker compose -p superset-1 -f docker-compose-light.yml up
+NODE_PORT=9002 docker compose -p superset-2 -f docker-compose-light.yml up
+NODE_PORT=9003 docker compose -p superset-3 -f docker-compose-light.yml up
+```
+
+This configuration includes:
+- PostgreSQL database (internal network only)
+- Superset application server
+- Frontend development server with webpack hot reloading
+- In-memory caching (no Redis)
+- Isolated volumes and networks per instance

Review Comment:
   ### Missing In-Memory Cache Data Persistence Warning <sub>![category 
Documentation](https://img.shields.io/badge/Documentation-7c3aed)</sub>
   
   <details>
     <summary>Tell me more</summary>
   
   ###### What is the issue?
   The documentation fails to mention the potential data persistence 
implications of using in-memory caching instead of Redis.
   
   
   ###### Why this matters
   Users might lose critical data or face unexpected behavior if they're 
unaware that in-memory cache contents are lost when the service restarts.
   
   ###### Suggested change ∙ *Feature Preview*
   Add a warning about in-memory cache limitations:
   ```markdown
   This configuration includes:
   - PostgreSQL database (internal network only)
   - Superset application server
   - Frontend development server with webpack hot reloading
   - In-memory caching (no Redis)
   - Isolated volumes and networks per instance
   
   :::warning
   In-memory caching means cache contents will be lost when the service 
restarts. This is suitable for development but may affect functionality that 
relies on cached data.
   :::
   ```
   
   
   
   ###### Provide feedback to improve future suggestions
   [![Nice 
Catch](https://img.shields.io/badge/👍%20Nice%20Catch-71BC78)](https://app.korbit.ai/feedback/aa91ff46-6083-4491-9416-b83dd1994b51/8ddf5509-1025-44fd-bd84-6b1f8f5ac873/upvote)
 
[![Incorrect](https://img.shields.io/badge/👎%20Incorrect-white)](https://app.korbit.ai/feedback/aa91ff46-6083-4491-9416-b83dd1994b51/8ddf5509-1025-44fd-bd84-6b1f8f5ac873?what_not_true=true)
  [![Not in 
Scope](https://img.shields.io/badge/👎%20Out%20of%20PR%20scope-white)](https://app.korbit.ai/feedback/aa91ff46-6083-4491-9416-b83dd1994b51/8ddf5509-1025-44fd-bd84-6b1f8f5ac873?what_out_of_scope=true)
 [![Not in coding 
standard](https://img.shields.io/badge/👎%20Not%20in%20our%20standards-white)](https://app.korbit.ai/feedback/aa91ff46-6083-4491-9416-b83dd1994b51/8ddf5509-1025-44fd-bd84-6b1f8f5ac873?what_not_in_standard=true)
 
[![Other](https://img.shields.io/badge/👎%20Other-white)](https://app.korbit.ai/feedback/aa91ff46-6083-4491-9416-b83dd1994b51/8ddf5509-1025-44fd-bd84-6b1f8f5ac873)
   </details>
   
   <sub>
   
   💬 Looking for more details? Reply to this comment to chat with Korbit.
   </sub>
   
   <!--- korbi internal id:ca3ede9d-cf79-48ef-9c0e-fc03cb2ef302 -->
   
   
   [](ca3ede9d-cf79-48ef-9c0e-fc03cb2ef302)



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to