Izakaya is a playground to answer:

• Q: When to use a Rust web backend instead of e.g. Flask / Django?
• Q: How different frontends feel against a Rust backend?
• Q: What different hosting solutions are there for Rust?

This mono-repo has various backends and frontends, some of which auto-deploy on the main branch change.

• 🟧 tatami: Rust + Axum + SQLx code, online

• 🍙 onigiri: Vite + React + React Router + RTK Query code, online
• 🍗 yakitori: Next 14 + App Router + SWR code, online
• 🥟 gyoza: Vite + SvelteKit + TanStack Query code, online

Mainly an excuse to play with Rust, but...

I love using launch-and-forget Platform as a Service (PaaS) solutions for personal projects, but I don't like the direction Heroku has been heading for ages now, so looking for alternatives: PaaS Provider Notes

For the time being, I'm convinced by Railway.

... and I realized that I don't know the ins and outs of all these "modern" frontend frameworks, so I decided to try out a couple of them.

Each subproject has their own README with usage instructions.

I use mise to manage tool/language versions; you can too:

mise install

Or manually set up versions defined in the .mise.toml file.

Take a seat, read some code and enjoy your time! 🍻