1 Answers

Actually, I already had the framework's DI container booting and responding right inside the blog page https://www.frameworkm.dev/blog/the-beauty-of-clean-architecture#-live-interactive-wasm-playground

Then I had moved on to the HA scheduler, https://www.frameworkm.dev/blog/stateless-ha-scheduling-with-nats

When I found out about Ajit’s shiny new thing, it gave me that spark for absolute closure. We want a full playground—and I figured if frappe could run in Pyodide, our clean, async architecture was practically born for it. So I went back, decoupled our database migrations, and brought the whole thing into WebAssembly! More details: https://www.frameworkm.dev/blog/zero-cliff-in-the-browser-decoupling-database-migrations-in-webassembly

Playground link: https://www.frameworkm.dev/playground

What are the login credentials for Playground link: https://www.frameworkm.dev/playground

Hover over the key icon for credentials:

username: admin@example.com
password: Secret@1234

Related