Doomseeker

[nonetrix]

Description

Doomseeker is a Doom server browser, the issue is that it requires a path to each Doom source port directory. Managing this in home manager would make a lot of sense, however, it seems there is no module for this currently

This should be fairly easy to implement, it just has a .ini config under ~/.config/zandronum along with your wads

[aguirre-matteo]

Hi! I'm not one of the assignees but I want to contribute! I've searched for documentation about the options for the config file, but was unsuccessfull. I installed Doomseeker and it seems it uses two INI files at ~/.config/doomseeker/.

As you said, implementing a module should be easy, but it seems like those files have a lot of default values, and maybe the inmutability of HM's files may break the app.

[keenanweaver]

While not as elegant, it's practically a lot easier to set the doomseeker.ini with home.file after going through the GUI and setting it up manually:

home.file = {
  doomseeker-ini = {
    enable = true;
    source = config.lib.file.mkOutOfStoreSymlink "./dotfiles/config/doomseeker/doomseeker.ini";
    target = "${config.xdg.configHome}/doomseeker/doomseeker.ini";
  };
};

The mkOutOfStoreSymlink should allow you to edit the INI with the Doomseeker GUI without hassle.

Point the executables to the absolute path like this:

[ChocolateDoom]
BinaryPath=/etc/profiles/per-user/keenan/bin/crispy-doom
ChocolateHereticBinaryPath=/etc/profiles/per-user/keenan/bin/crispy-heretic
ChocolateHexenBinaryPath=/etc/profiles/per-user/keenan/bin/crispy-hexen
ChocolateStrifeBinaryPath=/etc/profiles/per-user/keenan/bin/crispy-strife