LLM/n8n-install
1
0
Fork 0
mirror of https://github.com/kossakovsky/n8n-install.git synced 2026-04-27 02:06:03 +00:00
Code Issues Packages Projects Releases Wiki Activity
Files
07b76b01a614c8f7a11093cddf4584ab9fd6cfcd
n8n-install/memory-bank/reflection/reflection-comfyui-integration.md
Yury Kossakovsky 51d46d9144 Add ComfyUI as an optional service in the installer 
- Updated .env.example to include COMFYUI_HOSTNAME for configuration.
- Modified Caddyfile to add a reverse proxy for ComfyUI at the specified hostname.
- Enhanced docker-compose.yml to include a new ComfyUI service with persistent storage and health checks.
- Updated scripts to integrate ComfyUI into the setup wizard and final report.
- Documented the integration process and reflections in the memory bank for future reference.
2025-08-07 22:13:01 -06:00

1.8 KiB
Raw Blame History

Reflection: ComfyUI Integration (Level 2)

Summary

Added ComfyUI as an optional service using Docker Compose profile comfyui, proxied via Caddy at COMFYUI_HOSTNAME. Default CPU support, optional GPU planned. Updated .env.example, docker-compose.yml, Caddyfile, scripts/04_wizard.sh, scripts/06_final_report.sh, and README.md.

What Went Well

  • Followed existing installer patterns (profiles, Caddy host blocks, env generation/wizard/reporting) with minimal, clear edits
  • Simple reverse proxy through Caddy; WebSocket support expected to work without extra config
  • Compose config validated successfully

Challenges

  • No single “official” Docker image; community images differ in volume layout and flags
  • Volume paths for models/output/custom_nodes vary by image; chose a conservative mount point for persistence
  • GPU enablement requires NVIDIA toolkit and compose device reservations (not universally available)

Lessons Learned

  • Keep defaults CPU-first to minimize friction; add GPU as an opt-in
  • Abstract image details behind a validation checklist (port 8188, volume paths, CLI flags)
  • Document model storage and persistence expectations explicitly

Improvements / Next Steps

  • Consider adding a GPU-specific profile variant (e.g., comfyui-gpu-nvidia) when environment supports it
  • Evaluate switching to a more widely adopted/maintained image and standardize volume mappings
  • Extend final report with quick pointers to model directories and basic usage tips

Verification Checklist

  • Implementation reviewed end-to-end: YES
  • Successes documented: YES
  • Challenges documented: YES
  • Lessons learned documented: YES
  • Process/Technical improvements identified: YES

Impact

  • New optional service enabling visual Stable Diffusion workflows in the installer with minimal complexity