ktaraszk

4 ms·

1.
Deploy Rails With Kamal to a Managed Cluster(miget.com)
3 points by ktaraszk 2mo ago|0 comments
2.
by ktaraszk 2mo ago
Still free hosting
3.
by ktaraszk 2mo ago
They won't let you. It's part of their business to keep you locked in.
4.
by ktaraszk 3mo ago
Yes, it is, but why or what for?
5.
Show HN: Mashines.dev – Live-migrate microVMs between hosts without restarting(mashines.dev)
6 points by ktaraszk 4mo ago|2 comments
6.
by ktaraszk 8mo ago
The routing layer being down while workers/data services stay up is such a specific failure mode. Usually means the load balancers or edge routing got corrupted somehow, not the actual compute infrastructure. If you're serious abo
7.
by ktaraszk 8mo ago
Yeah, if Heroku's cert rotation depends on Google's CA and it tried to renew during the outage window, that'd definitely cause problems. The 8-hour ETA is rough. This is why multi-CA fallback configs exist, but most platforms
8.
by ktaraszk 8mo ago
The fact that your database is reachable but the app isn't after restart points to the routing layer being toast. If you can ssh into the dyno or check logs, look for anything related to the router handshake timing out. Usually when de
9.
by ktaraszk 8mo ago
The status page lag is the worst part. Hard to debug when you're questioning whether it's your config or their infrastructure. At least when multiple providers go down at once you know it's not just you going insane.
10.
by ktaraszk 8mo ago
The CA outage is hitting a lot of services, but yeah, Heroku's been on a slow decline since the Salesforce acquisition. Free tier killed, pricing creep, stagnant innovation. Even when it's not their fault, you start wondering if i
11.
by ktaraszk 8mo ago
I've been watching this thread closely. We built miget ( https://miget.com/ ) specifically because of these pain points. The Heroku-style DX without the eye-watering bills or corporate neglect. What stood out from the co
12.
by ktaraszk 8mo ago
The enterprise communication breakdown is rough. We built miget ( https://miget.com/ ) partly because we kept hearing stories like ojame's - long-time Heroku users stuck between expensive renewals and migration risk. The
13.
by ktaraszk 8mo ago
We built miget.com specifically for cases like this. Free tier (no card required) with 256MB RAM should handle Spring Boot apps fine for teaching purposes. It's much simpler than Azure but still supports any JVM app. If your students n
14.
by ktaraszk 8mo ago
The AI-assisted provisioning part is wild. That setup would've taken days just a few years ago. One thing worth considering: at $200/mo you're still managing patches, security updates, backups, and handling your own uptime. A
15.
by ktaraszk 8mo ago
This exactly. The tech migration part is usually straightforward (Buildpacks and Procfiles work mostly the same across platforms), but the harder question is "how do we avoid this situation again?" That's why we built miget.c
16.
by ktaraszk 8mo ago
I used Heroku until 2023 too. That "operational excellence" line felt like a euphemism for "we're done here." The frustrating part wasn't just the lack of new features - it was watching the price stay high whil
17.
by ktaraszk 8mo ago
The "on life support" analogy is spot on. We built miget ( https://miget.com ) specifically because of this pattern, watching platforms slowly sunset while users scramble to migrate under pressure. The ops planning point
18.
Show HN: Migetpacks – Zero-config container builds, no Dockerfile needed(github.com)
3 points by ktaraszk 8mo ago|1 comments
19.
by ktaraszk 8mo ago
Yes, have you seen miget.com by any chance? You can start with the free tier, and can have a backend with a database for free (256Mi plan). If you need more, just upgrade. They redefined cloud billing. Worth checking.
20.
by ktaraszk 9mo ago
Just use container-os as your runtime image: https://hub.docker.com/r/miget/container-os and you should be good
21.
by ktaraszk 9mo ago
Interesting. Is this going to be integrated with Jira, ClickUp, etc?
22.
by ktaraszk 11mo ago
A couple of questions I expect here (based on similar discussions in other channels): 1) What about memory - is it shared too? CPU is shared dynamically. Memory is still hard allocated as a guaranteed limit per workload. This was intentiona
23.
by ktaraszk 11mo ago
A quick example of why this matters for devs & startups: imagine you’ve got 5 small apps each using 0.3 CPU most of the time. In most PaaS you’d pay for 5 separate instances. On Miget you pay for one resource plan and those apps share t
24.
by ktaraszk 11mo ago
Here’s a bit more detail on how the scheduler works under the hood: 1. Each application still runs on its own Kubernetes node to guarantee isolation (so noisy-neighbor issues are eliminated). 2. We track CPU usage in real-time across all wo
25.
Show HN: Fair CPU scheduling to run unlimited apps on one plan(miget.com)
1 points by ktaraszk 11mo ago|3 comments
26.
by ktaraszk 1y ago
Hey, thanks for the comment - you're right. It’s pronounced /ˈmɪgɛt/ – like it’s spelled, with a hard “g”. No relation to “midget”, no offense intended. Thanks again for pointing it out!
27.
by ktaraszk 1y ago
Great question, let me clarify: At Miget, you always start with a fixed plan: say, 2 vCPUs and 4GB RAM. That’s your hard cap — you can deploy as many apps as you want within that limit. We support autoscaling within your plan, meaning your
28.
Launch: Miget – A New Kind of PaaS (No Per-App or Usage-Based Billing)
2 points by ktaraszk 1y ago|4 comments
29.
Launch: Miget – A New Kind of PaaS (No Per-App or Usage-Based Billing)(miget.com)
1 points by ktaraszk 1y ago|1 comments
30.
by ktaraszk 1y ago
Hey HN, After years of pain using platforms like Heroku, Render, Fly, and Railway, we decided to build our own. It’s called Miget, and it rethinks both the developer experience and the economics of deployment. Most PaaS platforms tax you pe

More ›