Hacker Newsnew | past | comments | ask | show | jobs | submit | sameklund's commentslogin

It seems that your claim is that “this is how it should be” and also “this is how it is/has been” - not sure if you are referring to a specific region, considering the parent comment, but assuming you mean the tech industry in general, this seems patently false.

This is not a description of how talented, or smart, or “good at something” someone is. You are describing how risk-averse someone is, as well as how able to survive failure. The latter is slightly different from the former, although related. Someone not able to survive failure at all (due to having no savings, for example, or perhaps someone who has high monthly fixed costs) ought to have a low tolerance for risk, but they might still have a lower threshold for what they consider risky relative to someone else.

I’ve met plenty of talented/smart/etc people in each of these groups, and also plenty of the opposite. To be fair, my experience is anecdotal and biased, although I would reasonably expect such a pattern to continue.


Considering both of these right now. Why was Dokku so much better for you?


I’m working on Lunni – similar to Coolify, but centered around compose files (hopefully that’s less magic!): https://lunni.dev/

Would love to hear your thoughts if you give it a try!


Looks like this is a web UI for docker swarm? Does it have additional PaaS-like features? I think I would probably just use Portainer if I wanted a GUI. Unless I am missing something?


Lunni is similar to Portainer. (And it uses Portainer as the backend, actually!)

Before I started Lunni, I was using Portainer myself, but it got too painful. Here are some paper cuts I’m trying to solve with Lunni:

- I only manage one cluster (of one server), but I still had to select endpoint every time. In Lunni, the first thing you see when you log in is the status of your stacks/projects

- I use Traefik with routing config living in service labels. It’s a huge snippet, impossible to remember, which I had to copy from project to project. In Lunni it’s autocompleted for you: https://lunni.dev/docs/deploy/#:~:text=This%20is%20quite%20l...

- When you look at the service logs in Portainer, they refresh once in a while and throw away your scroll position, which is super frustrating. In Lunni, it works as you’d expect. As a bonus, you can copy a link to a log line (e.g. if you want to share it with somebody or just bookmark it)

- If you need to create a Docker config or secret for a stack in Portainer, you have to go to another dashboard section, make a config yourself, then copy the name to your stack. In Lunni, you can do that right on the New project page: https://lunni.dev/docs/configs-secrets/

- ...and a lot of other things like error messages that don’t disappear in 5 seconds, before you’ve had a chance to read them

Basically, I’m trying to make a Portainer that is a pleasure to use. Maybe it’s not as close to Coolify as I thought, but I’m trying to maintain a more PaaSy feel than Portainer. Some things you’d expect from a PaaS, like a built in CI and automated DB/volume backups, are also on the roadmap!


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: