WIP: bash-based deployment #301
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#301
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "kiara/fediversity:bash-deploy"
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?
implement #76 using bash/python to get a sense of what might be the simplest deployment method.
strategy used:
246380e00ftof4ad9b9f0ab3ee74ecfbto00bf58bbfc00bf58bbfcto429a4cbe23kiara referenced this pull request2025-04-05 16:07:07 +02:00
i don't actually want this merged, i'll apply the learnings here to #274.
I'm not entirely sure what the purpose of this PR is. My guess is that you are trying, with TF, to deploy NixOS configurations on pre-existing machines, without relying on things like nixos-anywhere. Is that correct?
(I will go back to reading the things when I get the bigger picture!)
Oh, it's closed. Sorry.
@Niols nah no problem, i had opened it for feedback, as (maiming
views.pyaside) the overall approach would be similar.this particular PR implements it without TF - the TF one without nixos-anywhere is branch
terraform-nixos(no PR as of yet, may get merged into #274).Without TF, does that mean with NixOps4, or in a standalone fashion?
@Niols tihs particular implementation is standalone, specifically handled in a bash script +
views.py- the rest of the implementation should be sharedPull request closed