toolshed/docs.coopcloud.tech
3
2
Fork 22
Code Issues 8 Pull Requests Packages Releases Activity

migrate The Moving Parts to the Intro area, stylize #248

Merged
basebuilder merged 4 commits from improve-operators into main 2024-02-21 16:27:04 +00:00
Conversation 3 Commits 4 Files Changed 6 +165 -120
basebuilder commented 2024-02-05 19:28:06 +00:00
Contributor
Copy Link

My first commit towards #537 does what the title says. A peak at stylization, I took a stab at making a graph of The Moving Parts using the mermaid graphs plugin in the theme.

Screenshot 2024-02-05 at 20-10-10 Project Strategy - Co-op Cloud Public Interest Infrastructure.png

Getting the Operators area really refined will take a few passes at things, I suggest the workflow of me continuing to push to this improve-operators branch and merging as we go.

My first commit towards [#537](/coop-cloud/organising/issues/537) does what the title says. A peak at stylization, I took a stab at making a graph of `The Moving Parts` using the [mermaid graphs](https://squidfunk.github.io/mkdocs-material/reference/diagrams/) plugin in the theme. ![Screenshot 2024-02-05 at 20-10-10 Project Strategy - Co-op Cloud Public Interest Infrastructure.png](/attachments/ee80dbaf-277f-4791-944b-db616c69453e) Getting the `Operators` area really refined will take a few passes at things, I suggest the workflow of me continuing to push to this `improve-operators` branch and merging as we go.
Screenshot 2024-02-05 at 20-10-10 Project Strategy - Co-op Cloud Public Interest Infrastructure.png
97 KiB
basebuilder added 1 commit 2024-02-05 19:28:06 +00:00
migrate The Moving Parts into Intro area, stylize daa594edde
decentral1se reviewed 2024-02-06 00:03:21 +00:00
decentral1se left a comment
Owner
Copy Link

e p i c

e p i c
docs/intro/strategy.md Outdated
@ -20,0 +26,4 @@
graph LR
A[Libre Software Apps] --> B{Recipe Packaging};
B --> C[Command-line Tool];
B --> D[Container Orchestrator];
decentral1se commented 2024-02-06 00:03:01 +00:00
Owner
Copy Link

So Cool!

If you skip straight to orchestrator from the recipe packaging, do you use plain 'ol Docker to deploy? Seems to me like maybe we don't want to emphasise this in the initial presentation of the system? It's all technically possible but I'd keep it simple here and just do "package, CLI, orchestrator"?

So Cool! If you skip straight to orchestrator from the recipe packaging, do you use plain 'ol Docker to deploy? Seems to me like maybe we don't want to emphasise this in the initial presentation of the system? It's all technically possible but I'd keep it simple here and just do "package, CLI, orchestrator"?
basebuilder commented 2024-02-12 09:49:35 +00:00
Author
Contributor
Copy Link

This makes total sense, thanks for the feedback 👍 I updated it to the following:

Moving Parts Flow Chart

This makes total sense, thanks for the feedback 👍 I updated it to the following: ![Moving Parts Flow Chart](/attachments/9c54e55b-021b-48ef-ad53-70619c073842)
basebuilder marked this conversation as resolved
basebuilder added 1 commit 2024-02-10 15:04:34 +00:00
Small improvements to Operators tutorial fe476b5f76 
- Made info boxes collapsible (default: closed)
- Put links at end of sentences for clarity
basebuilder added 1 commit 2024-02-12 09:30:48 +00:00
Improvements to Operators docs (manal verifying, CLI setup) 0cbb00c0df 
- Move 'Validating abra binary checksums' to abra/install.md
- Flatten #command-line-setup sub headings in Operators Handbook
basebuilder commented 2024-02-12 09:38:39 +00:00
Author
Contributor
Copy Link

In 0cbb00c0df I cleaned up the Operators Tutorial further by removing the ### Command-line setup heading because semantically it did not make sense to put adding a server under that, and installing abra is a first class install step to give focus to.

Screenshot 2024-02-12 at 10-29-45 New Operators Tutorial - Co-op Cloud Public Interest Infrastructure.png

In doing this, I moved Validating abra binary checksums to the Abra -> Install location, which is more logical and it cleans up Operators Handbook slightly.

In 0cbb00c0dfd7612b352f000f00280a07ba11a992 I cleaned up the `Operators Tutorial` further by removing the `### Command-line setup` heading because semantically it did not make sense to put adding a server under that, and installing abra is a first class install step to give focus to. ![Screenshot 2024-02-12 at 10-29-45 New Operators Tutorial - Co-op Cloud Public Interest Infrastructure.png](/attachments/27f574f9-4f4a-4d13-8ebd-05a290a8210f) In doing this, I moved `Validating abra binary checksums` to the `Abra -> Install` location, which is more logical and it cleans up `Operators Handbook` slightly.
Screenshot 2024-02-12 at 10-29-45 New Operators Tutorial - Co-op Cloud Public Interest Infrastructure.png
16 KiB
🚀 1
basebuilder added 1 commit 2024-02-12 09:50:25 +00:00
update Moving Parts flow chart d856135506
basebuilder commented 2024-02-21 16:26:57 +00:00
Author
Contributor
Copy Link

I'm merging this as well and will resume working on this branch.

I'm merging this as well and will resume working on this branch.
basebuilder merged commit b9c7ebd500 into main 2024-02-21 16:27:04 +00:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
3wordchant aadil abra-bot ammaratef45 Apfelwurm carla cas coopcloud cyrnel decentral1se fauno iexos jade jmakdah2 joe-irving kawaiipunk knoflook kolaente lambdabundesverband linnealovespie moritz notplants p4u1 pharaohgraphy renovate-bot ripclap simon sixsmith trav val yksflip
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: toolshed/docs.coopcloud.tech#248
No description provided.
Delete Branch "improve-operators"

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?