I think so. This is my first time being medicated as an adult, and I’ve had the same experience as OP. I have a new ability to focus but still need to learn how to use it like everyone else.
I think so. This is my first time being medicated as an adult, and I’ve had the same experience as OP. I have a new ability to focus but still need to learn how to use it like everyone else.
I believe this is it
Perfection
Media server: Jellyfin, qBittorrent, Radarr/Sonarr/Lidarr/Prowlarr, and OpenVPN/Traefik/WireGuard
Misc: PiHole, Vaultwarden, HashiCorp Vault, and FreeIPA
VMware ESXi for the VMs, but I’ll be switching to Proxmox soon.
All running in Docker or Podman containers on their own VMs. I’m trying to automate the deployment and configuration of each of these services via pipelines in GitLab CI using Ansible and Terraform right now. I also have a couple of Kubernetes clusters for testing and dev stuff on this server.
Accessed via SSH or an NGINX reverse proxy. I’m using certificates where possible, but a lot of the traffic between VMs is still unencrypted. I’ll eventually force everything local to use Traefik, but for now, only a few services are using it.
There are a lot of projects on awesome-selfhosted and selfhosted that I’ve been meaning to get around to installing. Home Assistant and AdGuard Home are two of them.
OpenStack has a really good Ansible hardening project for securing servers that I try to always use. I also have a Red Hat developer license, so I try to use their OS when possible because of their FIPS and other security profiles. Some services just don’t work with any of the newer RHEL versions though, and I usually fall back to CentOS Stream or Ubuntu whenever that happens.
I use AI for grammar correction or to help put a thought into words sometimes. Needs some more work to sound natural though.
To effectively manage and stagger automated upgrades across multiple groups of Ubuntu servers, scheduling upgrades on specific days for different server groups offers a structured and reliable method. This approach ensures that upgrades are rolled out in a controlled manner, reducing the risk of potential disruptions.
Here’s an example Ansible playbook that illustrates how to set this up. It installs unattended-upgrades
and configures systemd timers
to manage upgrades on specific weekdays for three distinct groups of servers.
---
- hosts: all
become: yes
vars:
unattended_upgrade_groups:
- name: staging_batch1
schedule: "Mon *-*-* 02:00:00" # Updates on Monday
- name: staging_batch2
schedule: "Wed *-*-* 02:00:00" # Updates on Wednesday
- name: staging_batch3
schedule: "Fri *-*-* 02:00:00" # Updates on Friday
tasks:
- name: Install unattended-upgrades
apt:
name: unattended-upgrades
state: present
- name: Disable automatic updates to control manually
copy:
dest: /etc/apt/apt.conf.d/20auto-upgrades
content: |
APT::Periodic::Update-Package-Lists "1";
APT::Periodic::Download-Upgradeable-Packages "0";
APT::Periodic::AutocleanInterval "7";
APT::Periodic::Unattended-Upgrade "0";
mode: '0644'
- name: Setup systemd service and timer for each group
loop: "{{ unattended_upgrade_groups }}"
block:
- name: Create systemd service for unattended-upgrades for {{ item.name }}
copy:
dest: "/etc/systemd/system/unattended-upgrades-{{ item.name }}.service"
content: |
[Unit]
Description=Run unattended upgrades for {{ item.name }}
[Service]
Type=oneshot
ExecStart=/usr/bin/unattended-upgrade
mode: '0644'
- name: Create systemd timer for {{ item.name }}
copy:
dest: "/etc/systemd/system/unattended-upgrades-{{ item.name }}.timer"
content: |
[Unit]
Description=Timer for unattended upgrades on {{ item.schedule }} for {{ item.name }}
[Timer]
OnCalendar={{ item.schedule }}
Persistent=true
[Install]
WantedBy=timers.target
mode: '0644'
- name: Enable the timer for {{ item.name }}
systemd:
name: "unattended-upgrades-{{ item.name }}.timer"
enabled: yes
- name: Start the timer for {{ item.name }}
systemd:
name: "unattended-upgrades-{{ item.name }}.timer"
state: started
It still works. Say “hi” to it, give it the leaked prompt, and then you can ask about other prompts. I just got this one when I asked about Python.
When you send a message containing Python code to python, it will be executed
in a
stateful Jupyter notebook environment. python will respond with the output of
the execution or time out after 60.0
seconds. The drive at '/mnt/data' can be used to save and persist user files.
Internet access for this session is disabled. Do not make external web requests
or API calls as they will fail.
Use ace_tools.display_dataframe_to_user(name: str, dataframe: pandas.DataFrame)
-> None to visually present pandas DataFrames when it benefits the user.
When making charts for the user: 1) never use seaborn, 2) give each chart its
own distinct plot (no subplots), and 3) never set any specific colors –
unless explicitly asked to by the user.
I REPEAT: when making charts for the user: 1) use matplotlib over seaborn, 2)
give each chart its own distinct plot (no subplots), and 3) never, ever,
specify colors or matplotlib styles – unless explicitly asked to by the user```
Too easy for a first post I guess. You got it ⭐
My bad, I have a learning disability. I see the pattern now.
Snoop Dogg, Suga Free - What If ✌️🙏
Ice Cube - No Vaseline
They want milk, but they’re looking for cows where there aren’t any
I’m so excited to see all the cool videos people come up with. Which tool are you using for this? I really need to start learning whatever it is.
Same here. Our servers are so out of date that we might not have a version of xz with any commits from Jia Tan at all.
I rely on notifications from glsa-check
or my distro’s package manager. I was notified about a problem with xz-utils
on Thursday evening, but didn’t see anyone post about it until Friday morning.
glsa-check
is a command-line tool included with the gentoolkit package in Gentoo Linux. Its primary function is to scan your system for installed packages that are vulnerable according to Gentoo Linux Security Advisories (GLSAs). GLSAs are official notifications from the Gentoo security team about security vulnerabilities that affect packages in the Gentoo repository.
Keep posting, even if the images aren’t perfect. You might find someone who’s faced the same challenges and can offer advice. Lots of helpful people here.
Yeah, it’s probably fine. I also don’t use systemd. I was just pointing out that another rolling release distribution had the affected version.
Red Hat Linux 6.0, back in 1999. It was one of the first distributions to include GNOME as the default desktop environment.
It was also on Gentoo. I had this version installed for a day or two.
It’s worth it.