u/ajitbohra

Frappe Local

We spend a lot of time working with Frappe, and one thing kept bothering us.

Sometimes you just want to spin up a local Frappe site to explore an app, test an idea, or reproduce an issue. Instead, you end up installing dependencies, configuring services, or figuring out Docker before you can even get started.

So we built Frappe Local to scratch our own itch.

The goal is simple: make running Frappe locally as effortless as possible.

Frappe Local bundles everything needed under the hood, so you don't have to worry about installing or configuring the various moving parts yourself. It handles the setup while giving you a clean desktop interface to manage your local benches and sites.

Current beta includes:

• Create and manage local benches
• Create and manage sites
• Start and stop services from a desktop app
• Docker managed behind the scenes
• Cross-platform (macOS available today, more platforms coming)
• Free and open source

It's still an early beta, so expect rough edges. We're already using it internally and thought it might be useful to share with the community.

GitHub: https://github.com/lubusIN/frappe-local

Quick walkthrough: https://www.youtube.com/watch?v=UImalRAxq3s

Would love to hear your thoughts. Is this something you are looking to simplify? What would you like to see in a tool like this?

We've open-sourced something we've been using internally called Frappe Brewery 🍺

• It started as a small script to extract metadata from Frappe app repositories.
• Then we needed JSON endpoints for tooling.
• Then we needed validation.
• Then submission workflows.

Eventually it turned into a full app registry.

A few things it does:

• Extracts app metadata from repositories
• Tracks compatibility and installation information
• Generates static JSON indexes
• Provides APIs for tooling and integrations
• Uses GitHub issues and PRs for submissions
• Can be self-hosted on Cloudflare Pages

Registry Website

Registry GitHub Worlkflow

One design goal was keeping it lightweight and easy to fork. You can run a public registry, a private company registry, or a curated collection of apps for a specific use case.

We're planning to use it as a building block for some of our other Frappe projects, but it felt useful enough to release on its own.

Curious to hear feedback from others building tools around the Frappe ecosystem. What metadata or discovery features do you wish existed today?

GitHub Repo:
https://github.com/lubusIN/frappe-brewery

Our Public Registry:
https://frappe-brewery.lubus.in/

Read More:
https://lubus.in/blog/introducing-frappe-brewery-an-open-app-registry-for-frappe

We’ve been experimenting with running the Frappe framework fully client side in the browser using WASM + SQLite, inspired heavily by what WordPress Playground did for the WordPress ecosystem.

The idea was simple:
“What if trying Frappe could be as easy as opening a link?”

After a lot of hacks and broken experiments, we now have a working prototype running entirely in the browser.

Current setup is highly experimental:

• SQLite instead of MariaDB
• In-memory/cache workarounds instead of Redis
• WASM runtime
• Browser persistence experiments
• Lots of rough edges!

But even in this state, it already feels like a gateway to interesting possibilities!

Live demo: (hosted on cloudflare pages)
https://frappe-playground.lubus.in

Credentials:
User: Administrator
Pass: admin

>playground is temporary / disposable and reloads on page refresh or new tab.

Would love feedback, ideas, and people interested in exploring this further with us.

Very early days, but exciting to see what might be possible here.

Open source and available to explore or contribute:
https://github.com/lubusIN/frappe-playground 

Read More:
https://lubus.in/blog/running-frappe-entirely-in-the-browser-with-wasm-pyodide-and-sqlite