Sanitized single-commit public mirror of recipe-maintainer. - Removed test-ssh/.testenv (live creds); added test-ssh/.testenv.example placeholders. - Removed plans/ and planned-updates/ (deployment-planning docs) so no client/ deployment domains appear in the public repo. - All other secret stores were already gitignored. - docs.coopcloud.tech retained as a submodule (public upstream).
21 lines
893 B
Plaintext
21 lines
893 B
Plaintext
|
|
investigate whether this whole process could also be sped up by using opus for making changes to the recipes, but using sonnet (or some other fast model) for speedrunning through the tests
|
|
|
|
set up some infrastructure to do automated recipe maintenance in the night or on a timed weekly basis
|
|
|
|
consider documenting or collabing with autonomic to setup some intentional manual spot tests and verifications
|
|
|
|
***
|
|
|
|
- output pastable guide for walking through application of recipe updates
|
|
(thus completing two parts of the flower /recipes-overview and /apps-overview)
|
|
|
|
- abra-plan-creator
|
|
... a tool where you describe what type of maintenance you want to do,
|
|
or what kind of apps you want to deploy,
|
|
and it potentially asks you clarifying questions (depending on "expert" mode or not)
|
|
and it creates a detailed markdown plan for you,
|
|
where you can then copy and paste commands into terminal
|
|
|
|
***
|