Full Docker stack per project

A project isn’t a folder. It’s a folder plus the dozen things that have to be running around it: a dev server, a database, a queue, a cache, a worker, a mail catcher, sometimes a real browser. Loopyard treats that whole shape as the unit of work.

When you launch a project, Loopyard builds a Docker Compose stack tailored to what it found in the repo. A workspace container with your code mounted and the agent inside it. A dev server container running on the port the framework wants. Postgres if you have migrations. Redis if you have a sidekiq config. A reverse proxy that gives every service a real URL.

Because everything is in containers, nothing leaks onto your host. No “works on my machine,” no version pin against a tool installed three jobs ago, no manual cleanup when you’re done. Stop the project and the whole stack stops with it. Start it again tomorrow and you get back exactly what you left.

You can also reach into any container directly when you need to. The agent isn’t a black box living in a sandbox: it’s a process in a container you can ssh into, inspect, and operate alongside.