migrate The Moving Parts to the Intro area, stylize #248
Loading…
Reference in New Issue
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?
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.Getting the
Operators
area really refined will take a few passes at things, I suggest the workflow of me continuing to push to thisimprove-operators
branch and merging as we go.e p i c
@ -20,0 +26,4 @@
graph LR
A[Libre Software Apps] --> B{Recipe Packaging};
B --> C[Command-line Tool];
B --> D[Container 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"?
This makes total sense, thanks for the feedback 👍 I updated it to the following:
In
0cbb00c0df
I cleaned up theOperators 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.In doing this, I moved
Validating abra binary checksums
to theAbra -> Install
location, which is more logical and it cleans upOperators Handbook
slightly.I'm merging this as well and will resume working on this branch.