PowerShell with oh-my-posh

2024-11-16T00:00:00+00:00

Why, You Ask?

I use PowerShell on Fedora because I like having the same shell across workstations, VMs, dev containers, and Windows. oh-my-posh gives that shell a useful and consistent prompt.

Here is how I set it up with Cascadia Code Nerd Font and KDE Konsole.

Oh and guess what: This all works on Windows using Windows Terminal, too.

Step 1: Install oh-my-posh

First, we need to install oh-my-posh. It's as easy as running this command:

curl -s https://ohmyposh.dev/install.sh | bash

This script downloads the latest version of oh-my-posh and installs it. Feel free to inspect the script if you're cautious. If you're running Windows the installation is slightly different, but I guess you figure this out.

Step 2: Install Cascadia Code Nerd Font

oh-my-posh relies on a Nerd Font for its icons and styling. I chose Cascadia Code Nerd Mono because it's clean and works beautifully across different environments.

oh-my-posh font install

Set the Font in KDE Konsole:

Open Konsole.
Go to Settings > Edit Current Profile > Appearance.
Click Edit Font and select Cascadia Code Nerd Mono.

Set the Font in Windows Terminal:

Open Settings
Navigate to Font and choose Cascadia Code Nerd Mono.

Step 3: Configure PowerShell

To load oh-my-posh in PowerShell, edit your $PROFILE file.

code $PROFILE

Add the following lines to load oh-my-posh with your configuration:

oh-my-posh init pwsh --config "/path/to/oh-my-posh.json" | Invoke-Expression
clear

This initializes oh-my-posh with your chosen theme and clears the screen for a clean start.

Step 4: My oh-my-posh configuration

Here's my oh-my-posh config file. It's simple but does the job perfectly:

{
  "$schema": "https://raw.githubusercontent.com/JanDeDobbeleer/oh-my-posh/main/themes/schema.json",
  "blocks": [
    {
      "type": "prompt",
      "alignment": "left",
      "segments": [
        {
          "properties": {
            "cache_duration": "none",
            "style": "full"
          },
          "template": "{{ .Path }} ",
          "foreground": "#77E4F7",
          "type": "path",
          "style": "plain"
        },
        {
          "properties": {
            "cache_duration": "none"
          },
          "template": "{{ .HEAD }} ",
          "foreground": "#FFE700",
          "type": "git",
          "style": "plain"
        },
        {
          "properties": {
            "cache_duration": "none"
          },
          "template": "$ ",
          "foreground": "#43D426",
          "type": "text",
          "style": "plain"
        }
      ]
    }
  ],
  "version": 3
}

Path Segment: Displays the current directory in a bright cyan.
Git Segment: Shows the current Git branch in yellow, if applicable.
Prompt Character: Displays a green $, keeping it clean and minimal.

Step 5: (optional) Create a New Profile for PowerShell in Konsole

Let's set up a dedicated profile for PowerShell in Konsole:

Duplicate an Existing Profile:

In Konsole, go to Settings > Manage Profiles.
Select your default profile and click Duplicate.

Configure the PowerShell Profile:

Rename it to PowerShell.
Set the command to pwsh.
Under Appearance, set the font to Cascadia Code Nerd Mono.
Save your changes.
Set it as default (optional)

Summary

With oh-my-posh, Cascadia Code Nerd Font, and a dedicated profile in KDE Konsole, my PowerShell setup is consistent, stylish, and super effective. Whether I'm on Fedora, a VM, or a devcontainer, my terminal always feels like home.

If you're a PowerShell fan like me, give this setup a try. Trust me, your terminal (and your productivity) will thank you.

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 - powershell

PowerShell with oh-my-posh

Why, You Ask?

Step 1: Install oh-my-posh

Step 2: Install Cascadia Code Nerd Font

Step 3: Configure PowerShell

Step 4: My oh-my-posh configuration

Step 5: (optional) Create a New Profile for PowerShell in Konsole

Summary

Moving to Fedora: Automating PowerShell Installation with Ansible

Why, You Ask?

Step 1: The Problem

Step 2: The Playbook

Step 3: Usage

Summary