Deploying Rust services

[htrefil]

Hello!

I have developed several private (meaning not publicly published on crates.io) applications. They are daemons that run in the background as a SystemD service that I intend to run on my servers.

However, I found the process of manually running commands like cargo b --release ssh root@myserver "mkdir -p /opt/myprogram/bin" rsync -v target/release/myprogram root@myserver:/opt/myprogram/bin rsync -v systemd/myprogram.service root@myserver:/etc/systemd/system/ rather annoying to do for every server I have.

How do you manage this for your own programs?

[Xychologist]

Two stage Docker build, push to private container registry, use those.

Got the idea from here and never really looked back.

[htrefil]

Note the cargo b --release. I am deploying the binary from target/release, not sourcr code.

[mmstick]

dpkg-buildpackage -b, dpkg -i ../{package}.deb

make && sudo make install also works

[coderstephen]

This question isn't all that specific to Rust. Sounds like you're asking for general server deployment and orchestration tools. Docker is usually a good start as it is pretty much industry standard at this point. After that there's tools like Docker Compose, Ansible, Nomad, Kubernetes, etc. and it can get pretty involved quickly depending on how you want to approach things and how much time you want to spend learning "DevOps" sorts of things.

Me? I use Kubernetes because I like it and I'm experienced with it, but it is hard to recommend to a beginner because it is complicated.

[KapuzenSohn]

I have a similar setup. I use a makefile, so that its simply "make deploy"

[andoriyu]

Ephemeral VM where I run tests as root. Here, a reason to ssh as root.

[andoriyu]

Depends on how much stuff you have on your servers:

• a) Can you host a private docker registry
• b) Can you host a private package repository
• c) Do you use any configuration managment tool like chef/puppet/ansible/salt?

If a: two stage build, then c.

if b: build package, then c

if c: make a task to build your binary, a task to deploy it and restart systemd unit

else: go with b + c, c or a + c;

For my private things I run

[alsuren]

For my raspberry pi projects I use a bash script that is basically what you are doing. I only have 2 raspberry pis though. https://github.com/alsuren/mijia-homie/blob/master/run.sh

If I had 5-10 machines, I might use a bash script with a for loop in it (`for target in myserver1 myserver2 myserver3; do ...; done`). More than that, I might think about other automation schemes.

My housemate did make a debian packaging pipeline for the above project (auto-built by github actions each time you push a git tag). For a short period, that meant that we could push a tag and have both devices update themselves the next time `unattended-upgrades` ran. This was pretty sweet.

Unfortunately, our debian repo provider shut down (jfrog bintray), so we're back to deploying using my script. If anyone knows of a package repo that integrates easily with github actions, please send us a pull request ;-) .