spoons.technology/plots
4
0
Fork 0
Code Issues 13 Pull requests 3 Projects 1 Releases Packages Wiki Activity Actions

#1 Describe core service bootstrapping #15

Open
tom wants to merge 1 commit from 1-bootstrapping into main
pull from: 1-bootstrapping
merge into: spoons.technology:main
Conversation 3 Commits 1 Files changed 2 +25
tom commented 2025-12-27 11:54:43 +00:00
Owner
Copy link
No description provided.
tc424 reviewed 2025-12-27 17:22:43 +00:00
services/bootstrapping.md Outdated
@ -0,0 +5,4 @@
While several members of the core team have existing services
that could be used to bootstrap, using Terraform local state
temporarily. This proves the "cold start" workflow, and reduces
tc424 commented 2025-12-27 17:22:43 +00:00
Owner
Copy link

Confused by the "While .." here - not sure this sentence are parses? Are we recommending for or against using existing services to bootstrap?

Confused by the "While .." here - not sure this sentence are parses? Are we recommending for or against using existing services to bootstrap?
tom commented 2025-12-28 08:40:18 +00:00
Author
Owner
Copy link

Hmm yes, that doesn't really parse does it? Lemme try that again :)

Hmm yes, that doesn't really parse does it? Lemme try that again :)
tc424 commented 2025-12-27 17:27:09 +00:00
Owner
Copy link

Is the idea that infra-as-code is the key thing, even if we have to leverage personal services (like this forgejo instance) to bootstrap? Rather than bootstrapping "imperatively"? If so, yes, I agree :) Otherwise you end up trying to declaratively reproduce an imperatively created environment exactly .. reminds me of compiler bootstrapping where you to have to recompile the compiler with itself a few times to be sure everything's working correctly and producing identical output - a complication best avoided, I think.

Having a git replica hosted somewhere not on the project's infra might not be a bad idea in case of disasters though - otherwise a full "black start" could involve someone digging around in an S3 bucket somewhere trying to find the last git backup :)

Is the idea that infra-as-code is the key thing, even if we have to leverage personal services (like this forgejo instance) to bootstrap? Rather than bootstrapping "imperatively"? If so, yes, I agree :) Otherwise you end up trying to declaratively reproduce an imperatively created environment exactly .. reminds me of compiler bootstrapping where you to have to recompile the compiler with itself a few times to be sure everything's working correctly and producing identical output - a complication best avoided, I think. Having a git replica hosted somewhere not on the project's infra might not be a bad idea in case of disasters though - otherwise a full "black start" could involve someone digging around in an S3 bucket somewhere trying to find the last git backup :)
tom commented 2025-12-28 08:47:14 +00:00
Author
Owner
Copy link

The thought was mostly that we should avoid using people's stuff to bootstrap. I suppose "this git server" might be alright, but it feels like it would be bad to depend on "that thing @tc424 happened to be running at the point where we started".

Infra-as-code also feels key, yeah. Ideally getting to the point where we can have a CI-based workflow pretty quickly.

The thought was mostly that we should avoid using people's stuff to bootstrap. I suppose "this git server" might be alright, but it feels like it would be bad to depend on "that thing @tc424 happened to be running at the point where we started". Infra-as-code also feels key, yeah. Ideally getting to the point where we can have a CI-based workflow pretty quickly.
tom force-pushed 1-bootstrapping from 2d6cf0a6ea to b05568fd79 2025-12-28 09:55:34 +00:00 Compare
This pull request can be merged automatically.
This branch is out-of-date with the base branch
You are not authorized to merge this pull request.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin 1-bootstrapping:1-bootstrapping
git switch 1-bootstrapping

Merge

Merge the changes and update on Forgejo.

Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.

git switch main
git merge --no-ff 1-bootstrapping
git switch 1-bootstrapping
git rebase main
git switch main
git merge --ff-only 1-bootstrapping
git switch 1-bootstrapping
git rebase main
git switch main
git merge --no-ff 1-bootstrapping
git switch main
git merge --squash 1-bootstrapping
git switch main
git merge --ff-only 1-bootstrapping
git switch main
git merge 1-bootstrapping
git push origin main
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
spoons.technology/plots!15
No description provided.