I'm attempting to maintain a top-level secrets.json that defines all of the sensitive data that I'd like to version-control without exposing everything in cleartext to the world. To that end, I'm using `git secret`, which will use `gpg` to encrypt secrets.json everytime I call `git secret hide` and decrypt everytime I call `git secret reveal`. I'm going to try this until I don't like it anymore... if that day comes... I should write a blog post about my setup to solicit useful feedback and share my ideas with others. |
||
|---|---|---|
| .. | ||
| blog | ||
| days-of-week-habits | ||
| goals | ||
| habitgarden | ||
| habits | ||
| learn | ||
| sandbox | ||
| default.nix | ||
| index.html | ||
| README.md | ||
wpcarro.dev
https://wpcarro.dev is my personal website. I expose a few subdomains, one of which you are probably visiting right now, git.wpcarro.dev. Here are some of the others:
blog.wpcarro.dev: My personal bloglearn.wpcarro.dev: Teaching others to codesandbox.wpcarro.dev: Where I deploy some pet projects and code sketches
Visit https://wpcarro.dev for a sitemap.