| > If that was your problem, you should've said so instead of spinning it up into an entirely different security problem that plainly did not exist. It was merely an answer to your remark about "this fork wasn't meant for external consumption". Please don't try to substitute the argument. > Except you didn't stop spreading falsehoods. You've spent more lines lying with your brand new account on HN. I spent much more time researching this project and trying to figure out the least ugly way to fix its problems. This time was effectively wasted. I just wrote my post so someone who faces issues similar to mine will investigate the matter more carefully. > Fixating on hyper specific implementation details taken out of context without considering the design, intent, and usage is not what I call professionalism in the software industry. Ad hominem, moving on. > So packaging problems won't exist if we just stick with Docker, but you would use distro packages to create a Docker image? How would that even work? I am not going on to explain how to work with docker, it's a mainstream technology that has plenty of documentation and examples. > You see, Please. Stop. Repeating. Lies. https://github.com/NixOS/nix/issues/8 Please don't go ad hominem and don't accuse me of lying. This issue is submitted by Nix devs themselves. > The typical Nix way of handling secrets is that you store in them in a secure path and point the configuration to that path. And this is precisely the hack I was talking about. Because of this approach you cannot manage secrets with nix at scale (just to clarify: when I say "nix" I always mean the package manager). This is an issue submitted by core designers. I think we ran out of productive arguments in this conversation. |