Add forgejo-ci
machine to our infrastructure #389
No reviewers
Labels
No labels
api service
blocked
bug
component: fediversity panel
component: nixops4
documentation
estimation high: >3d
estimation low: <2h
estimation mid: <8h
productisation
project-management
question
role: sysadmin
security
technical debt
testing
type unclear
type: key result
type: objective
type: task
type: user story
user experience
No milestone
No project
No assignees
3 participants
Notifications
Due date
No due date set.
Depends on
#412 set default value for nixops4Package
Fediversity/Fediversity
#413 allow configuring network interface
Fediversity/Fediversity
#414 allow configuring whether a node uses QEMU
Fediversity/Fediversity
Reference: Fediversity/Fediversity#389
Loading…
Add table
Reference in a new issue
No description provided.
Delete branch "kiara/Fediversity:forgejo-ci"
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?
picked up from https://git.fediversity.eu/Fediversity/Fediversity/compare/main...niols:forgejo-ci.
closes #356.
1a89e5980b
toc685cd7cfa
1beae79bbe
to2a2db3e376
2a2db3e376
to6daa28b0b0
WIP: forgejo-cito forgejo-ciThis is a bit too much for me to follow, we should walk through the state and diff in a pairing session.
1847c76736
to6a718cf0d3
6a718cf0d3
to6ae9bfac9e
@ -0,0 +30,4 @@
host = "45.142.234.216";
opts = "-J orianne"; # FIXME
hostPublicKey = hostPublicKey;
};
This is a bit of a problem, and IIRC it was one of the main reasons not to merge at the time:
will not work for anyone but me. I suppose a solution would be to just use
host = "forgejo-ci"
and removeopts
, and leave each user configure what to do to reach it in their own.ssh/config
.This contains a bunch of different things. I think we could extract smaller PRs, eg.:
infra/common
and the existing machinesforgejo-ci
@ -0,0 +9,4 @@
inherit (lib.attrsets) concatMapAttrs optionalAttrs;
inherit (lib.strings) removeSuffix;
secretsPrefix = ../../secrets;
Let's maybe put
sources
,secrets
,keys
into_module.args
at the evaluation entry point, or even better, some global option as the module gods intended?For
sources
, this is partially tackled by #421.01c3a7b3c7
tod59be61a1b
@ -169,1 +169,4 @@
# NOTE: `forgejo-ci`, being a physical machine and not a Proxmox VM, gets
# custom treatment.
imports = [ ./forgejo-ci/flake-part.nix ];
Is the treatment really that specific that it needs to get its own
flake-part.nix
and its own deployment and all?LGTM! Shouldn't we move it to
machines/dev
instead of having it ininfra
?forgejo-cito Addforgejo-ci
machine to our infrastructureAddto WIP: Addforgejo-ci
machine to our infrastructureforgejo-ci
machine to our infrastructured59be61a1b
to44f5da55f7
44f5da55f7
tod2f694a555
d2f694a555
to447cbbcdd8
447cbbcdd8
to4ec325f985
WIP: Addto Addforgejo-ci
machine to our infrastructureforgejo-ci
machine to our infrastructurethanks for your feedback @Niols, i've updated the PR to incorporate it now. would you mind reviewing?
edit: for reference, i have in fact gotten the deployment working now.
e52939dee8
to90ee90711b
90ee90711b
to22d1b43b72
22d1b43b72
to21b867a312
21b867a312
to22d1b43b72
22d1b43b72
tob42ec33f22
b42ec33f22
tod9574ed4b0