Repository navigation
Packaging goals? #43
Description
Since this is pretty cool project and I want to see it grow I am also wondering what the plans are with regards to packaging. Since downloading a binary is cool and all but is not necessarily everyone's cup of tea.
To make myself clear: I am asking a question and hoping to start a conversation :)
Activity
encodeous commentedon Nov 21, 2025
Hmm, yeah I have been thinking of this too!
I can definitely offer a docker container for nylon nodes running as relays (no packet needs to enter the host network), for this, I can even add a tun-less variant, so we can reduce the required permissions :)
In terms of package managers... I kinda dug myself into a hole by naming this project nylon haha. I'm sure there might be many naming conflicts that arise from that. I think the option here is to simply name the package something like
nylon-wg(like NixOS/nixpkgs#454600)Though, currently the nylon config format hasn't been stabilized/versioned (though I try to keep changes to a minimum, or at least backwards compatible), so we might want to wait before publishing to pkg managers. It might be better to simply have a one-liner install script like many projects?
What do you think?
geraveoyomama commentedon Nov 21, 2025
I think a container image would be extremely powerful at the very least and a .deb and .rpm that take care of installing the systemd unit, binary and generating a /etc config. Or let the /etc be generated by nylon which would also streamline the config creation process a little bit.
I am very interested in this project and can help out with writing github actions to create containers and can also help with .deb packaging (most likely rpm as well) but I would like to do the "basic" things like a container images first.
Sidenote for the potentially breaking config changes. I personally think it's okay for projects to forsake old configs when they release v1.0 :)
EDIT: I also want to be ahead of the curve and apologise for my awful git-fu :')
encodeous commentedon Nov 21, 2025
That would be splendid! I already have a Dockerfile for my own private cluster, I'll clean it up a little bit and add it :)