My bash prompt is just me copying the prompt I have set on fish.

# Prompt
green=$'\e[38;5;2m'
bright_red=$'\e[38;5;9m'
bright_green=$'\e[38;5;10m'
reset=$'\e[0m'

prompt_command()
{
    local exit_status=$?

    if [[ $exit_status != 0 ]]; then
        exit_color=$bright_red
        exit_prompt=" [$exit_status]"
    else
        exit_color=$bright_green
        exit_prompt=""
    fi
}

PROMPT_COMMAND=prompt_command
PS1='\[$green\]\w\[$exit_color\]$exit_prompt\n❯ \[$reset\]'

I have a small issue with this prompt though. Sometimes the ❯ ends up turning white for some reason.

I haven’t had any issues with the kernel yet. The worst thing that I can remember doing is messing up the systemd boot entry on my Arch Linux install.

Yeah. I just found out about it by accident when I ran it with the --help flag.

I’d like to add that you can setup desktop shortcuts pretty easily for Mullvad and TOR browser manual installs. For TOR browser simply run this after opening a terminal in the folder it was extracted to:

./start-tor-browser.desktop --register-app

Same thing should work for mullvad.

Containers within a pod can use localhost to access each other. Containers outside of the pod needs to use the pod name to access the containers in the pod.

I looked up when pasta became the default networking backend for rootless and it seems to have been with podman 5.0. I do remember using podman 5.x versions, so I was most likely using pasta.

The reason why I seperated each app into their own network was indeed for security. The only container with access to all the networks is the reverse proxy.

I made a comment on another post a while ago, talking a bit about inter-container/pod networking.

https://sh.itjust.works/comment/17072681

It is the default atime option used when mounting if I’m correct. If it’s an ubuntu specific mount option it will be specified in /etc/fstab file.

You can run this to check

findmnt --real

Do you actually need to move the admin ui off of port 80/443 if you are just forwarding ports? I don’t think you need to. That said I actually don’t know much about port forwarding since I use Tailscale because of CGNAT.

My understanding of port forwarding is that you are forwarding connections to your WAN IP/port to a LAN IP/port. Since the router admin ui is available only on LAN by default, you don’t need to change it’s port from 80/443.

You don’t need 2 reverse proxies as others have said. What I did is just add a DNS rewrite entry in my adguardhome instance to point my domain.tld to the LAN IP of my reverse proxy.

The Talos Principle: Gold Edition

I remember back when I was a kid, playing these random games with my siblings and friends. I still remember some of those games like feeding frenzy, farm frenzy and big city adventure.

I use some generic names.

• Phone: phone
• Current Laptop: fedora
• Old laptop: laptop
• Router: openwrt

Yeah obsidian’s pretty nice. I use the daily notes feature built into it for my journal.

I actually use both in fish. I use aliases for some longer commands. For example I have la as an alias for eza -la --icons=auto --group-directories-first because I don’t really want to see it every time I run la. I use abbreviations for some shorter commands. For example systemctl abbreviated to sys and systemctl --user abbreviated to sysu.

I ran a podman quadlet setup as a test some time ago. My setup was a little like this:

• Create a pod if the app uses multiple containers
• Create a seperate network for each app (an app is either a single container or multiple containers grouped in a pod)
• Add the reverse proxy container to all networks
• I don’t expose any ports to the host unless necessary

If you create a new network in podman you can access other containers and pods in the same network with their name like so container_name:port or pod_name:port. This functionality is disabled in the default network by default. This works at least in the newer versions last I tried, so I have no idea about older podman versions.

For auto-updates just add this in your .container file under [Container] section:

[Container]
AutoUpdate=registry

Now there’s two main ways you can choose to update:

1. Enable podman-auto-update.timer to enable periodic updates similar to watchtower
2. Run podman auto-update manually

# Check for updates
podman auto-update --dry-run

# Update containers
podman auto-update

If you run adguard home it’s pretty easy. Just add a DNS rewrite to your local IP.

How are you running nginx and immich exactly? With containers or on the host?

I don’t know nixos that much but that looks like nixos configuration to me, so it’s running on the host I assume?

Some feeds I follow

• Adventures in Linux and KDE: https://pointieststick.com/feed/
• F-Droid: https://f-droid.org/feed.xml
• GamingOnLinux: https://www.gamingonlinux.com/article_rss.php
• Project Zomboid: https://projectzomboid.com/blog/feed/
• This Week in KDE Apps https://blogs.kde.org/categories/this-week-in-kde-apps/index.xml
• This Week in Plasma: https://blogs.kde.org/categories/this-week-in-plasma/index.xml

You’d need to install the windows version of steam within the prefix you launch the game probably. I haven’t tried so that’s just a guess.