Advanced

This section is for changing the stack rather than running it. Most of it rests on one promise: lemonfiber is never the thing standing between you and your stack. Everything it knows about the services comes from a file you can read and edit, everything it writes you can edit back, and the stack underneath runs on plain Docker Compose with no lemonfiber binary anywhere.

The stack manifestEvery field of stack.toml — profiles, forms, services — and what validation refuses.

Adding a serviceThree data edits and no code. What to write, and what checks it against the compose file.

Adopt and resetYour edits survive by default. How to make one permanent, and how to throw them all away.

Running without lemonfiberThe stack is a standalone Compose project. Clone it, set the variables, run it.

Remote accessWatching from outside the home. Specified, and not yet built.

Runtime enginesWhat drives the containers today, and the Podman and native paths that are specified.

Two of these pages describe work that is specified and not yet built. They say so at the top and link to the specification, rather than describing something that does not run as though it did.

Where to go next

If you have not run the stack yet, running your stack comes first — particularly forms and slices, which is the vocabulary the manifest is written in. If something is wrong rather than missing, when something is wrong starts with the doctor. If you want to build on the boundary rather than the stack, the API describes the shape everything comes out in.