Elliot Cameron
Elliot Cameron
Yes please make a PR!
IMO using a hash-based file structure to mimic nix is the least-bad solution. You could give it very restrictive permissions and drop the write bit to make it clear that...
Isn't the config dir already effectively a git repo since it's part of the deployment repo? The deployment git repo is effectively nothing more than a src thunk + config.
Perhaps we shouldn't have a `--disableHttps` flag at all. We can tell from the route that you want https can't we?
Yes the route is mandatory.
I've found `MonadMask` to be a less surprising tool for getting general bracketing.
I don't see a reason this *shouldn't* be supported. It's just a matter of doing it.
No it was mostly an accident. But this is an RFC at this point so I just wanted to get the idea out there for you and others to consider.
@ali-abrar I guess you would know that you needed to add docs when you added a target that you expected people to use semiregularly... About adding a test.... any ideas?
@ali-abrar I guess adding tests to this seems strange to me. I could see something like adding "documentation coverage", like "90% of our nix-build targets must be documented" or similar....