852 karma · joined June 5, 2021
I tried dokku (and still am!) and it is so hard getting started.
For reference, - I've used Coolify successfully where it required me to create a Github app to deploy my apps on pushes to master - I've written GH actions to build and deploy containers to big cloud
This page is what I get if I want to achieve the same, and it's completely a reference book approach - I feel like I'm reading an encyclopedia. https://dokku.com/docs/deployment/methods/git/#initializing-...
Contrast it with this, which is INSTANTLY useful and helps me deploy apps hot off the page: https://coolify.io/docs/knowledge-base/git/github/integratio...
What I would love to see for Dokku is tutorials for popular OSS apps and set-objective/get-it-done style getting started articles. I'd LOVE an article that takes me from baremetal to a reverse proxy+a few popular apps. Because the value isn't in using Dokku, it's in using Dokku to get to that state.
I'm trying to use dokku for my homeserver.
Ideally I want a painless, quick way to go from "hey here's a repo I like" to "deployed on my machine" with Dokku. And then once that works, peek under the hood.
Umm...haven't seen that one before!
I mean, companies optimise for profits and at some point people fall for it in excess which is the point OP made.
It kinda makes sense, because the means the companies employ are psychologically advanced plays on people who don't know the spelling of psychology.
I'm probably manipulated into scrolling more than I wanted to or buying more than I wanted to on an everyday basis.
Hey hey you're the TIL guy! I was designing my blog and I looked at what was suggested as the best blogs, yours was on it.
The TIL is such a great idea, takes the pressure off of "is it really good enough to post as a blog"
Glad to see you here :D
And he's done it five years back! Great blog, look at his other posts too
While true that all classes can be inherited, treating _all_ classes with the assumption that they will be would just lead to a labyrinth of code.
The threat model is sufficiently low to justify the much better UX of not having to look the code up everytime.
(cries in enterprise customers who required me to RDS into a barebones Windows installation to troubleshoot. Of course any other software installation was also blocked by security policies)
The OTP is the same for a user across rides, so I have mine memorised which is nifty. No fiddling with the phone during boarding.
On security: exploiting this would require the driver to stay in my vicinity the next time I book a ride, and also get the ride assigned to them. In a high population density area, it's rare - I've never had the same driver twice.
Btw I did exactly that! I cut (literally) a cheap keyboard at the numpad boundary. Installed AHK (Windows) which runs macros on button click.
Postits to label each button.
Now I have one of those fancy few-button keyboards that do my bidding.
I've been meaning to post it. Would that be interesting?