I redacted that part (https://github.com/Patryk27/website/commit/818c27967d7e6332c...), since it doesn't quite make sense if you think about it for longer than a couple seconds; it's 23:02 for me at the moment, maybe the night will bring me a new joke!
I’m rather surprised anyone would want a battery operated lamp at their bedside anyways, unless it was a backup battery for when the power goes out. There’s no battery indicator to know when it is low so you would just have to guess or pay attention when it looks like it needs to be charged. Most people would probably just plug it in and leave it plugged in all the time.
Thank you! I thought I missing something when this wasn’t the top comment. The idea of adding another device that I have to “tend to” is not attractive to me.
He has it setup to charge whenever he is not charging his phone. So, it's charging during the day and being used at night most likely. I have friends that have used battery operated lights where there aren't enough outlets or to avoid a cord to trip over.
Paw (Now RapidAPI) has a nice feature that generates a http request. The curl plugin and http plugin are the main ones I use but there's several others to generate the code in other languages too.
I don't mean it as discouragement but, at least for me, I would choose Heroku or Netlify because I don't want to self host it. I want someone else to manage all those bits for me.
It's good experience building the app though and good to have alternatives available.
I’m glad that the age of platform decay and VC backed companies that these OSS alternatives exist to counter this destructive trend of extraction based vendor lock in.
Vercel, Netlify and Heroku will inevitably not exist in 10-20 years but Coolify will, humming along on a regular VPS.
Because Salesforce decides it’s not profitable enough to be worth it, or they want to close Heroku off to Salesforce customers, or any number of other reasons
I work there. We are still around. Maybe not making waves as much as we used to but still hacking on stuff.
Right now I’m in the progress of rolling out a new platform powered by Cloud Native Buildpacks that allow you to build an OCI image locally. Here’s some language specific getting started (local) tutorials https://github.com/heroku/buildpacks#heroku-cloud-native-bui...
Nice to hear about the buildpacks. I use Containerfiles but since switching to Podman and Fedora/RockyLinux I've seen stuff about OpenShift which supports buildpacks. https://github.com/sclorg/s2i-base-container/
Money, I suppose? Heroku is notoriously trivial to use, and notoriously expensive for the amount of storage and compute you get.
A semi-successful but not heavily monetized side project on Heroku could cost you an arm and a leg, while running the same thing on some Hetzner box under Dokku, along with a couple of others, may be not that much noticeable.
That's great. I didn't mean any discouragement as much as to say, I would probably not promote its self hosting ability as much. Promote that it's open source and keep working on it because I am sure you'll learn a lot about the field space. If it comes down to it that Heroku, Netlify, Vercel, and all other PaaS companies are gone, I will most likely just do a VPS or server just for my app than launch my own PaaS.
tl;dr if I am looking for a PaaS, I don't care that it's self hostable. I don't want to host it, that's why I am looking.
A good way to promote that it's open source is to describe it as being self hostable and have a get starting page that quickly says how to self host it.
As for user experience, Vercel has a lot of UX talent but it hasn't been a great user experience for me. I had a glitch on their end that prevented the dashboard from loading for me and it took over a week to resolve, and transferring a domain out turned out to be a manual process. Meanwhile I have had great user experiences with spartan open source projects.
I feel like you got lost in my example/rambling that I probably shouldn't have said like that.
If I am a user looking for some place to host my application, I do not care that one service can be self hosted. I have already made my decision that I am going to host it somewhere else, so I am not going self host the PaaS just to host my application myself.
It can still be self hostable, just put it in the developer documentation and not necessarily promoting it so much on the main page.
I use (and love) Heroku in my day job, but when experimenting with Hetzner servers (and the like), it’s nice to have a GUI/framework like Coolify to manage the servers in a similar manner.
> I would choose Heroku or Netlify because I don't want to self host it
Why are people so afraid to self-host? It's usually cheaper and runs better than the hosted services. Get a cheap dedicated server from Hetzner, and you can run all your services there. Servers tend to keep working (usually longer than those cloud services do).
I wonder if it's a similar case with having tv shows running in the background? Music is often too stimulating for me but I like having the TV running in the background cycling through tv shows.
if one's childhood had many instances of tv playing in the background, then I suspect it's their nervous system marking that environment as their most safe/comfortable environment and that revisiting it can have a soothing effect on them?
Many years ago, I always used to have TV on whilst I did (composed) music.
With YouTube (and others) nowadays, I still found myself doomscrolling, so I bought a digital TV tuner and have that in a window.
Productivity up.
You might be remembering the 90s-era MDI user interface where you could have multiple documents open as sub-windows within the parent Excel application window.
One of the big things that Forge did for us a long time was handling of deployments. The ability to just have it respond to a commit: download the code, do the build and then restart FPM, was great.
We don't use that anymore, but we use it for provisioning and maintenance of systems... it's not GREAT at that, but it is still super nice to be able to say "stand up a MySQL server" and then it's just up and ready to go in a few minutes without having to deal with Ansible and Akamai...
2. it's, ironic?, because the post dates are in dd-mm-yyyy
reply