Ah so you're saying that what we today call deployment should be async? Yes, it should be that in any case, and it's implied in the later user stories where one gets a notification even when…
This seems to be blocked by Fediversity/Fediversity#69 because triggering NixOps from the Panel in a development environment will deploy to our only environment.
I don't think this is relevant because Nixpkgs already allows managing Python dependencies.. I also don't think adding another tool in between would make anything easier, since its, well, another…
I removed all the dependencies since they're not actually blocking this user story. All this one here says is that a deployment can be run and takes effect.
This is implemented with #235 (and reduced in scope by #247)
This is implemented with #235 (and reduced in scope by #247)
This is implemented with #235 (and reduced in scope by #247)
right now nothing is actually using that code, so I don't think we should put more thought into it until that changes.
IIUC the last state of discussion was that we'd generate the module options from the Pydantic schemas and test their compatibility in CI, not simply hope they match up by keeping them in sync…