4 ms·

LOL. I want to go back 10 years then. Or just use dokku. We've gone crazy guys.

by midrus 6y ago

rektide 6y ago
What seems crazy to me is that, a decade or two ago, * We had few standard ways of doing things. Everyone was cobbling together their own stack, figuring out their own ways to run a plethora of services needed to run & operate an internet connected box. * Each service or daemon needed to run your systems had it's own stand-alone management interfaces & systems. Nothing worked with anything else. There was no apiserver there to store the configurations you wanted. You had whatever scripts you wrote, checked in to source, then a big "do the scripts" button, and then you got a bunch of files written all over kingdom come to various hosts to do all the various tasks that supposedly would run your system, you hoped. * People with bare-metal had few tools to auto-scale or get resiliency for their systems. If you do have three machines, most operators managed them like pets, not cattle.
- xorcist 6y ago
  Ten years ago was 2010. VMs had already taken over everything by then. Some were convinced that VM images would take over application distribution, because it solved all dependency problems. Others weren't convinced and pointed to problems with insight and integration. Resiliency or scaling wasn't any easier or harder than now. It's not 1985 we're talking about.
- znpy 6y ago
  > * We had few standard ways of doing things. We still have few standard ways to do things. Yeah, docker. It's a thing. Then add kubernetes, you're really back to ten years ago. Unless you're running either stock GKE/EKS/AKS (thee different variants already), you don't really have a standard.
tdeck 6y ago
I actually still use dokku for my side projects and it works great. Very little learning curve, minimal headaches. Sure it doesn't scale out but that's not been a problem so far.
- StavrosK 6y ago
  Dokku scales fine, just resize the VM to something bigger. I have a looong way to go before my 15 side-projects need a server that costs anything over $20/mo.
  - tdeck 6y ago
    Yes it scales "up" which has been sufficient for my needs, but not "out" (i.e. to multiple app servers, without a lot of manual work on top).
StavrosK 6y ago
Dokku is fantastic for deploying web apps. I use it to deploy sideprojects and it works perfectly. For my home server, I use Docker with Compose, though I do find myself wishing for something a tiny bit more turnkey. Not too turnkey, just something that would allow me to push to a repo and have that be autodeployed with Compose.
- jswny 6y ago
  This is the same process I use. I’m still annoyed at the lack of simple deployment systems which use Compose, so I wrote my own: https://github.com/jswny/sad https://github.com/jswny/sad.

LOL. I want to go back 10 years then. Or just use dokku. We've gone crazy guys.

by midrus 6y ago

LOL. I want to go back 10 years then. Or just use dokku. We've gone crazy guys.

What seems crazy to me is that, a decade or two ago, * We had few standard ways of doing things. Everyone was cobbling together their own stack, figuring out their own ways to run a plethora of services needed to run & operate an internet connected box. * Each service or daemon needed to run your systems had it's own stand-alone management interfaces & systems. Nothing worked with anything else. There was no apiserver there to store the configurations you wanted. You had whatever scripts you wrote, checked in to source, then a big "do the scripts" button, and then you got a bunch of files written all over kingdom come to various hosts to do all the various tasks that supposedly would run your system, you hoped. * People with bare-metal had few tools to auto-scale or get resiliency for their systems. If you do have three machines, most operators managed them like pets, not cattle.

xorcist 6y ago
Ten years ago was 2010. VMs had already taken over everything by then. Some were convinced that VM images would take over application distribution, because it solved all dependency problems. Others weren't convinced and pointed to problems with insight and integration. Resiliency or scaling wasn't any easier or harder than now. It's not 1985 we're talking about.
znpy 6y ago
> * We had few standard ways of doing things. We still have few standard ways to do things. Yeah, docker. It's a thing. Then add kubernetes, you're really back to ten years ago. Unless you're running either stock GKE/EKS/AKS (thee different variants already), you don't really have a standard.

tdeck 6y ago

I actually still use dokku for my side projects and it works great. Very little learning curve, minimal headaches. Sure it doesn't scale out but that's not been a problem so far.

StavrosK 6y ago
Dokku scales fine, just resize the VM to something bigger. I have a looong way to go before my 15 side-projects need a server that costs anything over $20/mo.
- tdeck 6y ago
  Yes it scales "up" which has been sufficient for my needs, but not "out" (i.e. to multiple app servers, without a lot of manual work on top).

StavrosK 6y ago

Dokku is fantastic for deploying web apps. I use it to deploy sideprojects and it works perfectly. For my home server, I use Docker with Compose, though I do find myself wishing for something a tiny bit more turnkey. Not too turnkey, just something that would allow me to push to a repo and have that be autodeployed with Compose.

jswny 6y ago
This is the same process I use. I’m still annoyed at the lack of simple deployment systems which use Compose, so I wrote my own: https://github.com/jswny/sad https://github.com/jswny/sad.