initial working flake

[akshatagarwl]

• [x] Currently the jetty package in nixpkgs is broken so this won't work as is. For now I have used a modified version of jetty created using overrideAttrs but the upstream jetty should be fixed as well I have left a comment regarding the same at https://github.com/NixOS/nixpkgs/pull/132287#pullrequestreview-736233478.

• [ ] Also I haven't made this into an executable yet so the only way to run this would be by

  nix build
  nix develop
  cd result/
  java -jar <path-to-jetty>/start.jar 

• [x] Another problem is that fetching the dependencies is a hit-or-miss currently it's working fine for this commit https://github.com/decentralized-identity/universal-resolver/commit/5c2147f7992dd2c622aaf659309131e4cb881c05 but when I updated it to this https://github.com/decentralized-identity/universal-resolver/commit/0ff709c86b27a0aebd5d6b08b6a7a6827ddeed79 it failed Now we're using mvn2nix instead of FOD and use the tagged version of universal-resolver and it's drivers so there is no SNAPSHOT dependencies which break reproducibility.

• [x] Also a question: I have no idea what the standard way of packaging web servers in Nix is. Is it just a single binary that we would run? Services/Modules (don't even know what they are) or something else. So I would love to hear some thoughts/opinions on this as well Answered here: https://github.com/ngi-nix/universal-resolver/pull/1#issuecomment-909105283

• [x] TODO create a GitHub Action #2

[oppiliappan]

Also a question: I have no idea what the standard way of packaging web servers in Nix is. Is it just a single binary that we would run? Services/Modules (don't even know what they are) or something else. So I would love to hear some thoughts/opinions on this as well

Yes ideally you would make a Nixos module. With flakes, you can provide a module as an output as well. For example, a Nixos user would enable a mysql server like so:

# within /etc/nixos/configuration.nix
services.mysql = {
    enable = true;
};

The next nixos-rebuild-switch will bring the service up.

While I don't know too much about this package, I'd assume we can start with a simple module that just runs the package as a systemd service. We can layer on configuration options etc. later. The wiki is a good reference to start with.