Hacker News Reader

Comment by dnautics | Hacker News Reader

> And deployment in 2021, whatever the language, is best served with containers.

...in 2020 I deployed to bare metal servers. Mix released a gzip to S3 and pulled the artifact down, systemctl restart dnautics_service.

You're making me feel like some sort of dinosaur.

View on HN

Bare Metal / Containers / VM It's all about managing your dependency chain, and how much variation of environment you're willing to accept. You don't need to feel like a dinosaur if what you're doing is principled and reasonable.

There's no one size fits all.

Haha we bought these servers for 5k, very op, but since we had a rack full of HW (that this one blade was managing) anyways, the server price/power consumption for a 1U was a drop in the bucket. Very strange world. I think the server was at 10% CPU consumption, and we didn't bother doing the erlang "turn off IO polling for modern cloud operating systems" option.

Don't let the kids get you down. My deployment scripts look something like this:

rsync --rsync-path=/usr/bin/openrsync -r --delete config lib mix.exs mix.lock priv server:my_project

ssh server "tmux respawn-window -t my_project:1 -k"

It's only weird if it doesn't work, right?

I also use tmux as part of my deploy process. ;)

If you're already using systemd, you can use systemd-nspawn to launch your service in a container and nothing would change in your workflow.

Reply on news.ycombinator.com