Same. My config was public until I started needing to declare user accounts for friends or family on shared infra. I've considered whether to try and split some public modules off from the private config, but it's just not been important yet.
Same here, just not nix. Also some of the secret storage options I'd gladly use at work I find completely overblown for my home setup, e.g. theoretical SOPS encryption of the usernames used. Just not worth cleaning it up in a form I'd publish.
For my dotfiles I solved it by pasting the 2 secret-ish tokens into a ~/.config/.zshrc.post that is sourced from the main file if it exists.
I'm also keeping my nixOS config private because it doesn't feel like there's much reason to share it, while there is some potential downside.
I recently added SOPS support and switched some API keys because "it's just what you do and what's expected", and I wanted to get a feel for the system. But after trying it out I realized that this is just adding a potential point of risk to my config and creating extra burden for a security scenario I'm not worried about. If I could talk to my past version I would tell myself to avoid SOPS unless some new situation arises to merit its use. It's a good lesson though, and a gentle reminder to think about your specific use-case before going all-in on security measures.
All my repos are public bc I want to use GHA allowance to build and cache everything (I compile kernels with some weird flags and I’m tracking nixos-unstable-small)
my YTD was about $5k on GHA, and since the repo is public, I pay nothing at the end
This resonates a lot with me. I have another repo where I let out some of it to the public, https://github.com/wucke13/minimal-nixos . Whenever I feel like something might be useful to the greater public, I copy it to there.
jaculabilis | 20 hours ago
Same. My config was public until I started needing to declare user accounts for friends or family on shared infra. I've considered whether to try and split some public modules off from the private config, but it's just not been important yet.
wink | 20 hours ago
Same here, just not nix. Also some of the secret storage options I'd gladly use at work I find completely overblown for my home setup, e.g. theoretical SOPS encryption of the usernames used. Just not worth cleaning it up in a form I'd publish.
For my dotfiles I solved it by pasting the 2 secret-ish tokens into a ~/.config/.zshrc.post that is sourced from the main file if it exists.
cesarandreu | 18 hours ago
I'm also keeping my nixOS config private because it doesn't feel like there's much reason to share it, while there is some potential downside.
I recently added SOPS support and switched some API keys because "it's just what you do and what's expected", and I wanted to get a feel for the system. But after trying it out I realized that this is just adding a potential point of risk to my config and creating extra burden for a security scenario I'm not worried about. If I could talk to my past version I would tell myself to avoid SOPS unless some new situation arises to merit its use. It's a good lesson though, and a gentle reminder to think about your specific use-case before going all-in on security measures.
ysun | 17 hours ago
All my repos are public bc I want to use GHA allowance to build and cache everything (I compile kernels with some weird flags and I’m tracking nixos-unstable-small)
my YTD was about $5k on GHA, and since the repo is public, I pay nothing at the end
wucke13 | 16 hours ago
This resonates a lot with me. I have another repo where I let out some of it to the public, https://github.com/wucke13/minimal-nixos . Whenever I feel like something might be useful to the greater public, I copy it to there.