removing the dependency on hexchen's nixfiles #6
Loading…
Reference in a new issue
No description provided.
Delete branch "removing-nix-hexchen"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
since we're working pretty much out-of-sync these days and people keep being confused about where certain settings are set, it might be useful to consider moving the parts we use to be in-tree / thinking about how that may look.
For now this bundles three modules (encboot, boundmounts, and nopersist), and is otherwise a no-op as far as nix is concerned (modulo the auto-deployed docs & /etc/haccfiles, which copy our repo). See individual commits for details.
(cc @hexchen obviously, if you have opinions on this)
oh also, i noticed that https://gitlab.com/hexchen/nixfiles does not contain a license (but our repo does), so that's a thing to consider as well.
3fd4079265
tob31d180144
On first sight this looks good to me.
As for the license, maybe contact @hexchen directly, though I doubt she would have a problem with out usage or license.
b31d180144
to958c5840b7
I'm perfectly fine with you using my code, including releasing it into public domain under the unlicense license. I'd prefer a slightly more restrictive license personally, but honestly; who cares.
For legal reasons: I agree with the relicensing of my code to the Unlicense, as can be found on https://unlicense.org/.
As for the whole "out of sync" issue: yeah, forking my code sounds like a good idea.
958c5840b7
to0f678c5e80
okay, so the pure work of having a buildable haccfiles without depending on hexchen's nixfiles is done, and so far a no-op (module changes to the repo itself, which show up on our docs page):
This also results in some uncomfortable-looking code in
parsons/nftables.nix
, since I preserved whitespace exactly as it was.We can now deploy this as-is, or first think about if we want to add at least a little abstraction back in (e.g. currently the firewall.allowedTCPPorts options do nothing; these are hardcoded in the nftables ruleset). Alternatively, it seems upstream nixpkgs now has an nftables module with at least a couple more options than a few years ago, which I guess we could also try and use.
WIP: removing the dependency on hexchen's nixfilesto removing the dependency on hexchen's nixfilesheh, turns out you can't just merge things manually & push them and expect forgejo to pick up on it. so instead this is now in a weird place & i did some database foo to at least make it look correct at a first glance. oh well.