Wispr Flow: Dictation That Works EverywhereStop typing. Start speaking. 4x faster.
Promoted
GitHub
An ultra-lightweight, GitOps-first self-hosted PaaS.
10 followers
An ultra-lightweight, GitOps-first self-hosted PaaS.
10 followers
An ultra-lightweight, GitOps-first self-hosted PaaS in Go, SQLite, and Nginx. Deploy apps with zero downtime in <40MB of RAM.
under 40MB is wild, how are you handling database migrations and rollbacks with SQLite in a multi-tenant setup without running into locking issues?
how does the zero downtime deploy actually work under the hood, especially with SQLite as the database? curious if there's any locking or downtime during schema migrations
how does the zero downtime deployment actually work under the hood, especially with SQLite in the mix? curious whether you’re handling schema migrations somehow or if that’s on the dev to figure out
ran it on a tiny vps last night and the footprint is honestly wild, under 40mb and my deploys went out without any hiccups. finally feels like a paas that respects my resources.
ran a small node app on it over the weekend and the binary pulled in about 35mb, just like the docs claim. zero downtime deploys with the git push flow actually felt snappy instead of slow-roll like other paas toys i have tried.
Finally gave this a spin on a small side project and the under 40MB RAM claim actually holds up. Zero downtime deploys worked smoothly without me touching a single config file.
Spun it up on a small VPS and was surprised how painless the deploy flow felt for something this light. The SQLite choice is bold but it clearly works for the use case.