nixos/alist: init

[Moraxyc]

Things done

• Built on platform(s)
  • x86_64-linux
  • aarch64-linux
  • x86_64-darwin
  • aarch64-darwin
• For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)
  • sandbox = relaxed
  • sandbox = true
• Tested, as applicable:
  • NixOS test(s) (look inside nixos/tests)
  • and/or package tests
  • or, for functions and "core" functionality, tests in lib/tests or pkgs/test
  • made sure NixOS tests are linked to the relevant packages
• Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
• Tested basic functionality of all binary files (usually in ./result/bin/)
• 24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)
  • (Package updates) Added a release notes entry if the change is major or breaking
  • (Module updates) Added a release notes entry if the change is significant
  • (Module addition) Added a release notes entry if adding a new NixOS module
• Fits CONTRIBUTING.md.

---

Add a 👍 reaction to pull requests you find important.

[yunfachi]

Many descriptions do not end with a period, and some are not capitalized correctly. Please fix this.

I believe null would be more appropriate for the logic that disables http_port and https_port. However, you might need to change these null values to -1 specifically for the genJqSecretsReplacementSnippet context.

Additionally, you need to add a new module in the NixOS 24.11 release notes in alphabetical order.

[SuperSandro2000]

Suggested change

	default = null;
	default = "alist";

[Moraxyc]

I followed @pluiedev's suggestion for setting the user in this module — setting the default to null and creating the user only when it's not null. I’ve been using this pattern in all my modules where DynamicUser isn’t an option. Just wondering, is there a specific reason we shouldn’t do it this way?

[SuperSandro2000]

Suggested change

	default = null;
	default = "alist";

[SuperSandro2000]

Suggested change

	User = if cfg.user == null then "alist" else cfg.user;
	Group = if cfg.group == null then "alist" else cfg.group;
	User = cfg.user;
	Group = cfg.group;

[SuperSandro2000]

Can't this be placed with systemd-tmpfiles?

[Moraxyc]

Could you please provide some explanation? I'm not quite sure how systemd-tmpfiles is related here.

The reason we're writing to /var/lib/alist/config.json is to forcibly overwrite the previously generated config file and set a specific option in it. This is to test whether, with mutableConfig enabled, the script in preStart can make the previous settings persist.

[SuperSandro2000]

Can this be overwriten?

[Moraxyc]

I'm still not sure I understand what you mean. Could you explain it in more detail?

[qbisi]

DLGM. services.alist.enable = true and everything is fine.