auter VS Autoenv

For your couple of Linux servers, if you have their repositories sorted out, look at auter. Really easy to setup and schedule servers and especially when it's just a few of them.

I'm quite fond of Auter. I've been using it to automate patching of about 250 servers (RHEL, but Auter supports Ubuntu as well). It's quite flexible and easily extendable via its hooks. You can use Ansible or similar to deploy the config and cronjob to all your hosts, and then just sit back and watch it do its thing. No GUI, though.

How about auter? Auter link It's a github project built by people I work with, and it has some very nice configuration options available. We've configured environments that autoreboot for kernel updates but not everything else, options for not patching a group of systems if a different group failed for some reason (to keep from taking down all redundant systems in a patching run), unlimited automation options and scripting. In the dept I'm with now, we use a commercial product but we're really leaning into moving to Ansible. This is because it's easier to manage multiple envs with playbooks, than it would be to write all the customization into scripts for auter (and we're not allowed to completely automate the patching process in the new dept).

the way I manage (2) is with a kind of DIY pipenv system i've come up with. i have a tool installed in my terminal called autoenv. when i navigate to a new directory, if there's a .env file in it, autoenv executes it. that's basically all autoenv does. I have a .env in my home folder that, among other things, activates my "master" venv. when I create a new project that I want to have its own venv, I just add a .env file to that folder to activate it. otherwise, the master venv is active whenever I roam around my filesystem, functionally serving as a default environment i reuse.

Inspired by autoenv, pyautoenv hooks into the cd command in your shell and will automatically activate a poetry or venv Python environment if that environment is defined in the directory you're cd-ing into. Zsh, Bash, and PowerShell are supported.

There is an autoenv tool you can use to automatically activate a python virtualenv when you cd into a directory but it’s a little annoying to set up https://github.com/hyperupcall/autoenv

But IMO the best solution by far is to use autoenv. There is autoenv for bash and autoenv for zsh.