Skip to content

feat: add ENZO AI workspace compose example - #141

Closed
theguysudo wants to merge 1 commit into
Haxxnet:mainfrom
theguysudo:add-enzo-compose-example
Closed

feat: add ENZO AI workspace compose example#141
theguysudo wants to merge 1 commit into
Haxxnet:mainfrom
theguysudo:add-enzo-compose-example

Conversation

@theguysudo

@theguysudo theguysudo commented Sep 9, 2026

Copy link
Copy Markdown

Summary

Adds a Docker Compose example for ENZO, a self-hosted, bring-your-own-key AI workspace (Apache-2.0).

What's included:

  • examples/enzo/docker-compose.yml — Single-service compose file following the existing repo conventions (DOCKER_VOLUME_STORAGE, Traefik labels, etc.)
  • examples/enzo/README.md — References and usage notes
  • Updated README.md Large Language Models & AI section with the new entry

ENZO fits naturally alongside the existing Ollama + Open WebUI and Serge entries in the Large Language Models & AI section. Where Ollama/Serge focus on local models, ENZO runs on the user's own cloud provider keys (Groq, OpenRouter, NVIDIA, Google AI, Hugging Face) and adds a plain-English agent builder, scheduled agent runs, and skills (web search, Gmail, Google Calendar). No API keys or environment variables are required to start the stack — keys are pasted in the web UI after first boot and sealed client-side (AES-256-GCM); the server only relays requests.

Image: ghcr.io/theguysudo/enzo:latest (a full tag with all theme videos is also published). The container runs as the unprivileged node user, so the README notes the 1000:1000 volume ownership requirement.

@l4rm4nd

l4rm4nd commented Sep 9, 2026

Copy link
Copy Markdown
Member

Project is too young. Won't add.

@l4rm4nd l4rm4nd closed this Sep 9, 2026
@theguysudo

theguysudo commented Sep 9, 2026 via email

Copy link
Copy Markdown
Author

@theguysudo

Copy link
Copy Markdown
Author

Fair enough — thanks for taking a look and for the clear feedback.

Is there a rough age/traction point where you'd reconsider a resubmission? Happy to circle back once the project has had more time to mature.

@l4rm4nd

l4rm4nd commented Sep 9, 2026

Copy link
Copy Markdown
Member

Hey @theguysudo,

it’s mainly about community adoption and popularity.

It wouldn’t make sense to add every public repo to the list, as that would quickly make it unmanageable. The list is mostly focused on software that’s commonly used and actively discussed in r/selfhosted and other self-hosting communities.

Hope that helps clarify the criteria!

Adoption and popularity is typically indicated by stars and forks.

Hope you reach it some day!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants