Moving to Fedora: Automating Discord Updates with Ansible

2024-11-15T00:00:00+00:00

Why, You Ask?

So, you've found yourself running Fedora and decided to install Discord, huh? Great choice - Fedora is fantastic. But then you realize Discord's tarball updates are a hassle. Every week, it's the same story: download, extract, and pray you didn't miss a step. Tedious, right?

I use the following Ansible playbook to install and update Discord on Fedora. It handles the repetitive steps and makes the setup easy to reuse on another machine.

Step 1: Understanding the Process

Discord on Linux isn't as straightforward as we'd like. Flatpak is an option, but it can be slow with updates or cause compatibility issues. For those of us who prefer the direct tarball approach, we need a way to automate the mess. With Ansible, we can ensure Discord is always up-to-date with just one command. No more hunting for the latest download link or worrying about cleaning up old versions.

Step 2: The Playbook

Here's an Ansible playbook to make your life easier. It handles everything - downloading the tarball, extracting it to the proper location, and cleaning up afterward.

---
- name: Install and Update Discord on Fedora 41 using Ansible
  hosts: localhost
  become: true
  tasks:
    - name: Ensure /usr/share/discord is removed if it exists
      file:
        path: /usr/share/discord
        state: absent

    - name: Download Discord tarball
      get_url:
        url: "https://discord.com/api/download/stable?platform=linux&format=tar.gz"
        dest: "/tmp/discord.tar.gz"
        mode: "0644"

    - name: Create /usr/share/discord directory
      file:
        path: /usr/share/discord
        state: directory
        mode: "0755"

    - name: Extract Discord tarball to /usr/share/discord
      unarchive:
        src: "/tmp/discord.tar.gz"
        dest: "/usr/share/discord/"
        remote_src: true
        extra_opts: ["--strip-components=1"]
      args:
        creates: "/usr/share/discord/discord"

    - name: Clean up temporary files
      file:
        path: "/tmp/discord.tar.gz"
        state: absent

Step 3: What This Playbook Does

Step 1: If Discord is already installed, it removes the existing files to prevent conflicts.
Step 2: It downloads the latest stable Discord tarball directly from the official API.
Step 3: Creates the required directory at /usr/share/discord.
Step 4: Extracts the tarball into /usr/share/discord, stripping unnecessary folder components.
Step 5: Cleans up temporary files, leaving your system tidy.

A Note About Bash Aliases

If you're like me and love shortcuts, consider adding a bash alias to streamline running the playbook. This way, updating Discord becomes as simple as typing a single command. Here's how you can set it up:

cat ~/.bashrc.d/alias.sh
alias ansible-venv=". ~/repos/ansible/.venv/bin/activate"
alias update-discord="ansible-venv && ansible-playbook ~/repos/ansible/update-discord.yml --connection=local -K"

With this in place:

ansible-venv activates your virtual environment for Ansible.
update-discord runs the playbook with local connection and prompts for sudo permissions when needed.

Now, keeping Discord updated is literally a one-liner. Perfect, right?

Summary

The same playbook handles both the first installation and later updates, so keeping Discord current only takes one command.

So, go ahead - run it, relax, and enjoy Fedora without the hassle. Because let's face it: managing updates manually is so last year.

Moving to Fedora: Automating PowerShell Installation with Ansible

2024-11-15T00:00:00+00:00

Why, You Ask?

I use PowerShell on Fedora for scripting and automation. Installing it manually is fine once, but it becomes repetitive across workstations, VMs, dev containers, and servers.

This Ansible playbook automates the installation and keeps the setup consistent across those environments.

Step 1: The Problem

Installing PowerShell on Fedora involves downloading Microsoft's repository package, registering it, updating the package index, and then installing the actual PowerShell package. It's fine if you're doing it once, but if you have to repeat the process on multiple systems, it quickly becomes a chore.

The solution? Use Ansible to do it for you. Write the playbook once, and it works everywhere - no matter how many machines you're dealing with.

Step 2: The Playbook

Here's the Ansible playbook that automates PowerShell installation on Fedora:

---
- name: Install PowerShell on Fedora 41 using Ansible
  hosts: localhost
  become: yes
  gather_facts: true

  tasks:
    - name: Download Microsoft repository package
      ansible.builtin.get_url:
        url: https://packages.microsoft.com/config/rhel/8/packages-microsoft-prod.rpm
        dest: /tmp/packages-microsoft-prod.rpm

    - name: Register Microsoft repository
      ansible.builtin.command:
        cmd: rpm -i /tmp/packages-microsoft-prod.rpm
      args:
        creates: /etc/yum.repos.d/microsoft-prod.repo

    - name: Remove repository package after registration
      ansible.builtin.file:
        path: /tmp/packages-microsoft-prod.rpm
        state: absent

    - name: Update package index
      ansible.builtin.dnf:
        update_cache: yes
        state: latest

    - name: Install PowerShell
      ansible.builtin.dnf:
        name: powershell
        state: present

    - name: Verify PowerShell installation
      ansible.builtin.command:
        cmd: pwsh --version
      register: pwsh_version_output

    - name: Display PowerShell version
      ansible.builtin.debug:
        msg: "Installed PowerShell version: {{ pwsh_version_output.stdout }}"

Step 3: Usage

Running this playbook is straightforward. If you're working with a virtual environment for Ansible, make sure it's activated. Then, execute the playbook locally with the following command:

ansible-playbook /path/to/install-powershell.yml --connection=local -K

Here's a quick breakdown:

ansible-playbook: Runs the playbook.
/path/to/install-powershell.yml: Path to the playbook file.
--connection=local: Executes the playbook on the local machine instead of a remote host.
-K: Prompts for sudo privileges to perform the installation.

With this command, you can easily install PowerShell on your Fedora system without worrying about missing steps.

Summary

With this playbook, installing PowerShell on a new Fedora system takes one command and produces the same setup each time.

So, the next time you're staring down the prospect of yet another manual PowerShell install, let Ansible take care of it. Because honestly, you've got better things to do.

svnscha - fedora

Moving to Fedora: Automating Discord Updates with Ansible

Why, You Ask?

Step 1: Understanding the Process

Step 2: The Playbook

Step 3: What This Playbook Does

A Note About Bash Aliases

Summary

Moving to Fedora: Automating PowerShell Installation with Ansible

Why, You Ask?

Step 1: The Problem

Step 2: The Playbook

Step 3: Usage

Summary