I no longer use docker and caddy on this machine due to having a
preference for using flat files over self-hosted web applications,
especially when I am the sole user of said services.
In general, using the file system offers much more flexibility since it
makes backups easier and we can manipulate any of our data with standard
unix tools.
This is by far the best software I found for my own personal image
management.
Although web interfaces like Immich and Szurubooru are cool and useful
when sharing a collection of images online, they pale in comparison to
the simplicity and low maintenance of using Shotwell, which also happens
to be considerably faster to browse large collections of images with.
By default images are stored in a YYYY/MM/DD hierarchy, which helps
prevent images from losing their creation date over time and enables
filtering images by their file name without having to add the date to
the file.
Furthermore, by organizing images in this way, the usage of tags is
encouraged, enabling images to belong to multiple groups of images
instead of a single folder categorization.
I originally thought a monorepo was the way to go here and, although it
worked, I do want to keep this config as simple as possible for people
that just want to see how to set up Hyprland/dwm on NixOS.
For those curious in running NixOS on a phone specifically, there will
soon be a separate mobile-config repository that should make learning
from it easier.
Reduces complexity since we no longer have to manually update each
package from a non-firefox source.
Requires internet connectivity at runtime but should ensure that the
extensions are always up to date.
This is part of making the config easier to understand for users by only
having directories that directly map to flake outputs.
This also simplifies using the config a bit since it's possible to
remove containers entirely by simply deleting the containers.nix file.
The wg-mullvad interface was at some point renamed to wg0-mullvad.
Note that in the future this method can be used to prevent certain
containers from accessing the internet in a similar way.
At some point this started causing the /run/user/1000 directory to be
deleted when changing container configurations, which was definitely not
ideal.
An alternative approach will have to be taken if we want the wine
container to auto-start on boot.
This is the start of my fun attempt at using NixOS containers for web
services as a Docker replacement.
After spending some time on other servers I realized that I don't
actually *need* my dotfiles on those servers, so it becomes
significantly faster to build these containers without worrying about
home-manager and command-line programs I use on the host.
Main advantages include web service configuration with Nix instead of
Docker. Disadvantages include increased complexity for anything that
isn't already maintained by others in nixpkgs.
