Add forgejo-ci machine to our infrastructure #389
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
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
Add a link
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.
1a89e5980btoc685cd7cfa1beae79bbeto2a2db3e3762a2db3e376to6daa28b0b0WIP: 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.
1847c76736to6a718cf0d36a718cf0d3to6ae9bfac9e@ -0,0 +30,4 @@host = "45.142.234.216";opts = "-J orianne"; # FIXMEhostPublicKey = 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/commonand 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,keysinto_module.argsat the evaluation entry point, or even better, some global option as the module gods intended?For
sources, this is partially tackled by Fediversity/Fediversity#421.01c3a7b3c7tod59be61a1b@ -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.nixand its own deployment and all?LGTM! Shouldn't we move it to
machines/devinstead of having it ininfra?forgejo-cito Addforgejo-cimachine to our infrastructureAddto WIP: Addforgejo-cimachine to our infrastructureforgejo-cimachine to our infrastructured59be61a1bto44f5da55f744f5da55f7tod2f694a555d2f694a555to447cbbcdd8447cbbcdd8to4ec325f985WIP: Addto Addforgejo-cimachine to our infrastructureforgejo-cimachine 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.
e52939dee8to90ee90711b90ee90711bto22d1b43b7222d1b43b72to21b867a31221b867a312to22d1b43b7222d1b43b72tob42ec33f22b42ec33f22tod9574ed4b0