plausible: 2.0.0 -> 2.1.4

[xanderio]

Changelog: https://github.com/plausible/analytics/blob/v2.1.4/CHANGELOG.md

This upgrade was quite the undertaking, the major source of headaches was that plausible now has a dependency that makes use of rustler, tooling to call rust from elixir.

As the newer plausible version drop support for admin user reaction via env var in favour of a first install wizard, this can be backported to stable. This first install wizard is also the reason why the nixos test was reduces, as this new installed is based on phoenix live views, we can simply interact with it using curl and grep :/

I'm yet to deploy this onto a production installation of plausible, but looking at the web UI in a simple test installation everything look fine.

Closes: #314768

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/)
• 25.05 Release Notes (or backporting 24.11 and 25.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.

[xanderio]

Result of nixpkgs-review pr 356221 run on x86_64-linux 1

1 package blacklisted:

• nixos-install-tools

1 package built:

• plausible

[NetaliDev]

LGTM, but in my opinion, this should be split into multiple commits: one commit for the package update, one for package reformatting, one for the update script refactoring, one for the module changes and one for the test changes.

[xanderio]

LGTM, but in my opinion, this should be split into multiple commits: one commit for the package update, one for package reformatting, one for the update script refactoring, one for the module changes and one for the test changes.

I've thought about this, and I would like to keep it as one commit as otherwise we have one commit (package update) where the tests fail. This isn't that great when it comes to bisecting things.

[xanderio]

I've deployed this successfully.