Set of redwax modules (modular/federated PKI Tooling)

[dirkx]

Set of apache modules that make up most of a PKI framework; along with things like SCEP (automated rollout to things like cisco routers, iPhones, etc), timestamping and so on.

Note that this is our first attempt at a NixOS module set - any and all comments welcome; e.g. should we do it 1) like this - fairly independent; 2) create a library with just the sha/name/desc per module file or 3) create the common elements in the mother module (mod_ca) and minimise the leaf modules by referring somehow to the mod_ca definitions ?

Motivation for this change

Things done

• Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
• Built on platform(s)
  • NixOS
  • macOS
  • other Linux distributions
• Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
• [X ] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
• Tested execution of all binary files (usually in ./result/bin/)
• Determined the impact on package closure size (by running nix path-info -S before and after)
• Ensured that relevant documentation is up to date
• Fits CONTRIBUTING.md.

Notify maintainers

cc @

[aanderse]

Welcome and thanks for deciding to contribute to nixpkgs! We're glad you came. I haven't had a chance to test your code yet, but I have left some suggestions I hope you find helpful. Since this is your first PR I thought that my suggestions might be a little overwhelming so I decided to write some code you can reference when going through my suggestions if you get stuck at any point:

https://github.com/NixOS/nixpkgs/compare/master...aanderse:httpd-redwax?expand=1

Do you have a working configuration.nix snippet you used to test this code with that you could share?

Don't hesitate to ask any questions at all.

[dirkx]

Ok - so just changes this to $out/modules -- but happy to change it back ! As to `to such standard location exists' -- it may be easiest go back to our first cut - and follow what 'apxs -q apxs -q libexecdir' tells you -- as that tends to follow the idiosyncrasies of the various (linux) platforms. And thus be closes to what the user expect.

[dirkx]

Jan - not sure if you noticed it - but there is a slight hidden tweak behind that make which is not default Apache-- the https://source.redwax.eu/projects/RS/repos/mod_ca/browse/Makefile.am has been tweaked to both allow the standard linux tweaking; the normal apache synced approach (*bsd, darwin, macports, etc) and a prefix so that you can have the same path within the NIX store that is unique from apache - but they are still the same structure, etc.

[dirkx]

All review issues should be address I hope.

[dirkx]

Thanks. Works like a treat.

[dirkx]

All issues from review addresed.

[dirkx]

Ok will do. And will check if one of my test configs is sufficiently clean/unencumbered to already share. Will take a bit of time - as a rebase/move of the commits onto their own branch gives me several conflicts ' pkgs/development/interpreters/octave' and ' pkgs/servers/documize-community/default.nix - so this may require some surgery on my end with the history first. Dw.

[jonringer]

i think the wrong branch was pushed

[aanderse]

@dirkx can you please take a look at your branch when you get a chance?

[dirkx]

Closing this pull request - will move & squash the commits onto a new branch - and resubmit a pull request (See #76417).