New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Comments
unattended-upgrades for security updates (only, because they are non-breaking)
ssh user&host
sudo su
apt-get update && apt-get dist-upgrade
https://commando.io/
Found this on DO as a project. Looks interesting.
Why not use:
fucking shell scripts
?
http://fuckingshellscripts.org/
related hilarity:
http://areyoufuckingcoding.me/
At a max of 10 servers and no simple self-hosted option, I'll pass. But interesting offer.
I run apt-get update && apt-get -y upgrade via cron daily.
+1 @albertdb with unattended-upgrades, security only.
I'd strongly advise against cron dist-upgrade or upgrade in general for any production environment.
I use Ansible to manage my servers, so I use a command like:
Instead of applying to all you can use Ansible's inventory to organize your servers into groups. Before updating packages on my production servers, I test against my test servers. Ansible's playbook feature is also great for deployment and configuration management.
Edit: link to docs if you want to get started: http://docs.ansible.com/
Debian / Ubuntu Linux: Send Automatic Email Notification When Security Upgrades Available
Old guide, but should still work..
+1 on the Ansible thing. Pretty easy to use for this sort of stuff. Playbooks are more involved. Probably better off using command line for this. You can create groups based on Linux version then run apt or yum depending on the group.
http://docs.fabfile.org/en/1.8/ python's fabric allows you to connect to multiple servers via ssh and run commands i was using it to run yum update -y
I use Apticron to email myself when my servers requires updates. Updates have broken my system before, I need to make sure I'm the one applying the updates - and not a cron script.
I connected them about self-hosting... they never responded.
on debian I use cron-apt (apt-get install cron-apt) I set it to check everyday and send email to me every updates available.
Everyday all I need to do is checking my email, I can review the details from cron-apt email, if I decided to apply the update, I use ansible/chef/puppet etc, or you can use manual approach if your have small farm server
fabric
Fabric is not bad but I think Ansible is better for sysadmin types. You can do much much more sysadmin stuff with it. Fabric is ok if your are a software development type and know python imho.
I've used both and although I do some python software development I tend to prefer Ansible for sysadmin things.
fucking shell scripts
I use puppet, so I just have an exec resource running a yum update. Runs every 30 minutes, and everything is good.