Gabriel Fontes

Hey @MTRNord, sorry for the late reply! I do some of that on [my own config](https://github.com/misterio77/nix-config). I like to make a directory for each host, as well as a common...

Closing this for now, feel free to reopen if you folks want to discuss it further in the future :)

Fixed by #18

FYI @majora2007: The idea is to make it possible to separate software artifacts (code, build outputs, scripts, etc) from state on deployments. On Kavita, `config` is state (thus should be...

> If we're going to force people to move over, we should be handling that as a migration, but, I'm not sure we should force people to use an external...

This sounds good! Feel free to open up a PR.

Hey! Despite the scary error messages, a few schemes/templates failing to clone should not prevent the others from being cloned (just tested it in a fresh install). I'll see what...

Whenever you run `flavours update lists` or `flavours update all`, `~/.local/share/flavours/base16/sources/schemes/list.yaml` will be overwritten. In this case (schemes list manually edited), you should use only `flavours update schemes`.

I'd love to support tinted theming's format (all schemes on a single repo), but it's a little hard to implement that while keeping backwards compatibility. It's on my radar though!...

Hey Jamy, hope you're well! Sorry for taking too long to respond! I love your idea and I'm super happy with you building an alternative. I'd be happy to hand...