trigger nixops from panel #253
No reviewers
Labels
No labels
0 points
0.5 points
1 point
13 points
2 points
21 points
3 points
34 points
5 points
55 points
8 points
api service
blocked
component: fediversity panel
component: nixops4
documentation
estimation high: >3d
estimation low: <2h
estimation mid: <8h
infinite points
productisation
project-management
question
role: application developer
role: application operator
role: hosting provider
role: maintainer
security
technical debt
testing
type unclear
type: bug
type: deliverable
type: key result
type: objective
type: task
type: user story
user experience
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: fediversity/fediversity#253
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "kiara/fediversity:deploy-button"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
adds a deploy button to the panel form - covers the local part of #76.
As a workaround to pass info (from our user form) into nixops4 uses
environment variable
DEPLOYMENTthru nix's--extra-experimental-features configurable-impure-env.9d99fc0c9bto3886d2ea47@ -44,0 +49,4 @@submission = obj.parsed_value.model_dump_json()# in dev we can use a relative path, for deployed versions we must explicitly# specify our root flake as the directory to trigger nixops from, see #94.cwd = os.getenv("REPO_DIR") or f"{os.getcwd()}/.."Instead of polluting business logic with a conditional dealing with inessential details, let's instead set
REPO_DIRin the devhell. Also don't grab the environment variable directly, but please go via config, where all of these knobs are defined in a central place, and will make the application error out early if not handled correctly.pushed an update for this
@ -44,0 +51,4 @@# specify our root flake as the directory to trigger nixops from, see #94.cwd = os.getenv("REPO_DIR") or f"{os.getcwd()}/.."# FIXME: let the user specify these from the form (#190)dummy_user = {Why do we need the user here? In any case we can get it from the request context.
I've seen this comment Fediversity/Fediversity#190 (comment)
Do we strictly require that already merely to conclude the user story this implements? If we can avoid it let's not touch that part here.
Fediversity/Fediversity#215/files indeed rendered
initialUsera mandatory property there, unfortunatelyfwiw i have not checked whether this pixelfed cli command accepts empty values for these properties, or which of its flags are even considered mandatory
Alright, please add this as an in-code comment so we don't lose track of it.
21f26ecfb8toc5fe0157b0