News for hackers. Stuff that matters.
Re:Replacing a $3000/mo Heroku bill with a $55/mo server by bigstrat2003 on Tuesday October 21, 2025 @08:27PM (#45663568)
> It's fun the first time, but becomes an annoying faff when it has to be repeated constantly.

Certainly true, but there are a whole lot of tools to automate those operations so that you aren't doing them constantly.

Re:Replacing a $3000/mo Heroku bill with a $55/mo server by liqilin1567 on Tuesday October 21, 2025 @11:36PM (#45664673)
Mind sharing these tools and what each one does?
Re:Replacing a $3000/mo Heroku bill with a $55/mo server by c0balt on Wednesday October 22, 2025 @12:41AM (#45664944)
Ansible, Salt and Puppet are mostly industry standard. Those tools are commonly referred to as configuration management (systems).

Ansible basically automates the workflow of: log in to X, do step X (if Y is not present). It has broad support for distros and OSes. It's mostly imperative and can be used like a glorified task runner.

Salt let's you mostly declaratively describe the state of a system. It comes with a agent/central host system for distributing this configuration from the central host to the minions (push).

Puppet is also declarative and also comes with an agent/central host system but uses a pull based approach.

Specialized/ exotic options are also available, like mgmt or NixOS.

Re:Replacing a $3000/mo Heroku bill with a $55/mo server by liqilin1567 on Wednesday October 22, 2025 @01:21AM (#45665144)
Thanks, this is very detailed! Could you share some real-world use cases for these tools?

Actually I am looking for tools to automate DevOps and security for self-hosting

Re:Replacing a $3000/mo Heroku bill with a $55/mo server by indigo945 on Wednesday October 22, 2025 @03:19AM (#45665822)
Salt and Puppet are useful for managing a fleet of servers running various applications, especially when you need to scale those applications horizontally or want geo-distribution.

Ansible can also do that, on top of literally anything else you could want - network configuration, infrastructure automation, deployment pipelines, migrations, anything. As always, that flexibility can be a blessing or a curse, but I think Ansible manages it well because it's so KISS.

RedHat's commercial Ansible Automation Platform gives you more power for when you need it, but you don't need it starting out.

Re:Replacing a $3000/mo Heroku bill with a $55/mo server by comprev on Wednesday October 22, 2025 @04:49AM (#45666397)
A combination of HashiCorp Packer and Ansible means I can "publish" a VM ready-to-rock image to a public cloud provider gallery and use it to run a VM in said cloud.

Ansible-Lockdown is another excellent example of how Ansible can be used to harden servers via automation.

Re:Replacing a $3000/mo Heroku bill with a $55/mo server by c0balt on Wednesday October 22, 2025 @04:59AM (#45666464)
The other commenter already answered the usecase question, for self-hosting you will likely find ansible the easiest entrypoint.

It is in general the simplest of these systems to get started with and you should be able to incrementally adopt it. There is also a plethora of free online resources available for it.

Re:Replacing a $3000/mo Heroku bill with a $55/mo server by chickensong on Wednesday October 22, 2025 @04:26PM (#45674719)
> Puppet is also declarative and also comes with an agent/central host system but uses a pull based approach.

The person you're replying to mentioned a self-hosting use case, so this probably isn't relevant for that, but Ansible can also be configured for a pull approach, which is useful for scaling.

Re:Replacing a $3000/mo Heroku bill with a $55/mo server by chickensong on Wednesday October 22, 2025 @04:14PM (#45674582)
Even with automation, it can be a full-time job just to keep pace with the rate of change, never mind the initial development which can be non-trivial.