Envoryx documentation
Envoryx gives every project its own little stack - web server, PHP, Python, Go, Ruby,
Java, .NET or Node.js, a database, whatever services it needs - and runs all of it as Docker containers on a
machine you own. You click it together in the browser; nobody has to write a
docker-compose.yml.
Envoryx itself is one container on a Linux Docker host. It was built with Unraid in mind, but
any Linux box with Docker is fine. Each project then gets its own Docker network, its own
containers and two addresses: a plain port like http://<host>:20000, and through the built-in
proxy a proper name like https://shop.test.
Where to start
Section titled “Where to start”If Envoryx isn’t running yet, begin with the installation. After that, the first project is the quickest way to see how everything fits together.
Finding your way around
Section titled “Finding your way around”The sidebar follows roughly the order in which you’ll need things.
Getting started covers the requirements, the installation (with docker run, Compose or
on Unraid) and a first project. Projects is about creating them - from a template, a Git
repository or an existing website - and about starting, duplicating, renaming and deleting
them, their environment variables, the envoryx.yml manifest and resource limits.
Runtimes has one page per language: PHP, Node.js, Python, Go, Ruby and static sites. Each one explains what’s in the container, how the server runs and how you attach a debugger.
For everything around your code there are databases and the other services like Redis, Mailpit, search engines and object storage. Domains and HTTPS explains the names and certificates, sharing the temporary public links.
Day-to-day work lives under development tools: IDE integration, terminal and SSH, actions and tests. Then there are backups, the automation side with workers and cron jobs, the command line and MCP for AI assistants - and finally operations: updates, troubleshooting and security.