HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
basecamp
kamal
Ruby2023–2026
basecamp / kamal

kamal

Deploy web apps anywhere.

30Distinct people
37Mentions
0Explicit recommenders
14.7KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Deploy web apps anywhere.

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 10:01:16 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year37 dated mentions

Observed mentions: 2023-01-11 21:27:06 UTC to 2026-06-25 10:08:23 UTC.

051015202023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 22 mentions; 7 submissions, 15 comments20232024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 11 mentions; 5 submissions, 6 comments20242025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 3 mentions; 2 submissions, 1 comments. Incomplete calendar period.2026*

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC22715
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC1156
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC101
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC321

What Hacker News says

22 sources
I don't think there's a writeup out there, but mrsk just uses docker under the hood. So, if you have a CMD in your Dockerfile, it will use that. If you have an image that can run multiple things, like a rails app that can run the app process for web traffic by default, but it can also run job workers with the right command, you can provide the cmd in the mrsk config. You can see this in the jobs role in the example: https://github.com/mrsked/mrsk#using-different-roles-for-ser....
In MRSK vs. Fly.io
> When you look at the issues: https://github.com/mrsked/mrsk/issues/44 Wow. That’s uh, that’s certainly a decision. > They're the same service, because they're running the same image If something purports to “run my containers” and “be an alternative to K8s”, I’d kind of expect it to run whatever it’s told. Whether running identical containers on the same host is a good thing or not really depends on your architectures choices and trade offs. Blindly being like “you can’t have this because reasons” makes this whole tool a giant non-starter IMO.
In MRSK vs. Fly.io
I may be ignorant but doesn't that scenario you described encapsulate how MRSK functions? From the MRSK readme[1]: Connect to the servers over SSH (using root by default, authenticated by your ssh key) Install Docker on any server that might be missing it (using apt-get) Log into the registry both locally and remotely Build the image using the standard Dockerfile in the root of the application. Push the image to the registry. Pull the image from the registry onto the servers. Ensure Traefik is running and accepting traffic on port 80. Ensure your app responds with 200 OK to GET /up. Start a new container with the version of the app that matches the current git version hash. Stop the old container running the previous version of the app. Prune unused images and stopped containers to ensure server
Read the rest
In MRSK vs. Fly.io
Such a terrible idea, let's build something that everyone else has a solution for, we're on our own with our custom solutions that no one else know or use. We'll see how many years it will take them to come back to Kubernetes or equivalent. And the argument k8s is too complicated so build our own looks really bad from an engineering perspective. When you look at the issues: https://github.com/mrsked/mrsk/issues/44 you can some see trivial shortcoming that has been solved for years by other solutions.
In MRSK vs. Fly.io
The intro from README explains it well: ”MRSK deploys web apps anywhere from bare metal to cloud VMs using Docker with zero downtime. It uses the dynamic reverse-proxy Traefik to hold requests while the new application container is started and the old one is stopped.” https://github.com/mrsked/mrsk I’m looking forward testing this out. I already use Traefik and back in the day I used to use Capistrano to deploy Django apps, it feels like closing the circle :)
In MRSK – Deploy Apps Anywhere

Showing the 15 most recent of 22 sources. Enable JavaScript to search and browse every indexed mention.

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.