History

William Carroll 17c68d654b Prefer reading secrets.json to using pass show 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.		2020-08-20 18:31:37 +01:00
..
src	Run Prettier across projects	2020-03-27 10:59:50 +00:00
.envrc	Prefer reading secrets.json to using pass show	2020-08-20 18:31:37 +01:00
.gitignore	Add sandbox project using Contentful CMS	2020-03-24 13:27:30 +00:00
default.nix	Drop support for dir-locals.nix, <nixpkgs>, etc.	2020-08-20 11:26:32 +01:00
package.json	Add sandbox project using Contentful CMS	2020-03-24 13:27:30 +00:00
postcss.config.js	Run Prettier across projects	2020-03-27 10:59:50 +00:00
README.md	Add sandbox project using Contentful CMS	2020-03-24 13:27:30 +00:00
shell.nix	Drop support for dir-locals.nix, <nixpkgs>, etc.	2020-08-20 11:26:32 +01:00
tailwind.config.js	Run Prettier across projects	2020-03-27 10:59:50 +00:00
tsconfig.json	Run Prettier across projects	2020-03-27 10:59:50 +00:00
yarn.lock	Add sandbox project using Contentful CMS	2020-03-24 13:27:30 +00:00

README.md

Contentful

I have not used a CMS in a few years. I learned about Contentful from a Gatsby.js tutorial, and I wanted to learn more; I created a Contentful account, and I'm experimenting with the data here.

Developing

$ nix-shell
$ yarn run dev

Building

$ nix-build