When we get_or_create in the view, we want all the nested objects to be created as well. Here's a way how to do that in one step:
Please don't use hungarian notation, that's what we have types and namespaces for. More characters are harder to read, we only need as much information as needed to distinguish between the few different things we have.
We'll probably need this at some point, but it's not part of the user story.
No, you can't config // fediverse because both are functions. It would be slightly clearer given one doesn't know the implementation of the nixos.module option if we wrote
{...}: {…
Yeah I also think we probably want a data structure per service
Here's a sketch from the discussion @kiara and I had today about that issue. My way of phrasing this (to hopefully make the scribble easier to read): While NixOps4 allows managing configuration…
Actually this is a duplicate of Fediversity/Fediversity#76