Bench-less app creation
bench new-app runs inside a throwaway container and the scaffolded app lands in your working directory. Nothing but a container runtime needs to exist on the host.
Dev Tooling
Frappe apps without a bench
Vyogo Dev Containers wrap the Single Node Environment in a small utility that creates a custom Frappe app inside a container, writes it back to your working directory, and wires the volume mount into your compose file. New contributors go from clone to coding without installing a bench.
# Docker (default)./create_custom_frappe_app.sh my_app # Podman./create_custom_frappe_app.sh my_app --podman# Just wire the volume mount into compose.yml./create_custom_frappe_app.sh my_app --compose-update-only --podmanpodman-compose up -d # Install onto the pre-existing sitepodman exec -it <container> \ bench --site dev.localhost install-app my_appbench new-app runs inside a throwaway container and the scaffolded app lands in your working directory. Nothing but a container runtime needs to exist on the host.
The utility edits compose.yml to add the volume mount, so the app you just created is live in the environment without hand-editing YAML.
Runtime is auto-detected and can be forced with --podman, so rootless setups are a first-class path rather than an afterthought.
Already have an app? --compose-update-only skips creation and just wires the mount, which is the common case on a second machine.
A pre-configured Single Node Environment optimised for local development, Gitpod and instant onboarding — the container carries the toolchain so the host only needs Docker or Podman.
Frappista is the image — a bootable Frappe/ERPNext environment. Dev Containers is the workflow around it: a utility that scaffolds a custom app inside that image, writes it to your filesystem and wires the compose mount. You use both together.
No. Podman is fully supported and selected either automatically or with the --podman flag, so rootless container workflows work without modification.
No. The SNE image ships with dev.localhost already installed, so the container is serving a working site the moment it starts.
Zero-config Frappe images
Pre-built, single-node Frappe and ERPNext container images that boot with a working site.
ExploreFrappe v16 as a native package
Frappe and ERPNext v16 installed with snap, apt, dnf or brew — no Docker, no bench setup script.
ExploreFrappe Package Manager
npm-style packaging for Frappe apps: versioned .fpm artefacts, private repos, no Git required.
ExploreWe build and maintain these tools, and we help teams adopt them. Tell us what you are trying to ship and we will tell you honestly whether this is the right piece.
Talk to the team