Our team currently SSHs into every Linux device individually whenever we need to deploy an update, and it's becoming a huge time sink. What deployment or configuration-management approach works well for devices deployed in the field?
4 Answers
A CI pipeline can build and publish the application artifact—such as a container image—and then trigger the devices to update. Just make sure the devices have a reliable way to reach the control plane; requiring a VPN connection for every deployment can add a lot of operational complexity.
Ansible is a common starting point. It mainly requires SSH and Python on the target devices, and it lets you run the same deployment steps across many machines instead of connecting to each one manually.
The right choice depends on what these machines are. For ordinary endpoints, tools such as Ansible, Puppet, or Salt can handle configuration and software deployment. For IoT-style devices, it’s better to build an update mechanism and deployment pipeline into the device platform from the beginning.
If the devices can reach a repository or control service themselves, ansible-pull can work well. Each device periodically pulls the desired configuration or deployment tasks, which avoids needing to connect inbound to every device.

Related Questions
Can't Load PhpMyadmin On After Server Update
Redirect www to non-www in Apache Conf
How To Check If Your SSL Cert Is SHA 1
Windows TrackPad Gestures