-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
docs: refactor pages and rewrite installation #1014
Conversation
.docs/content/0.armonik/components/3.armonik/2.compute-plane.md
Outdated
Show resolved
Hide resolved
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
I'm even wondering if most of this doc should be in core and we link to core |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
should be in the control plane if we speak about the one that tells the number of tasks in each status
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't know. I juste move content from this file: https://github.com/aneoconsulting/ArmoniK/blob/main/infrastructure/quick-deploy/localhost/README.md#introduction
.docs/content/0.armonik/components/2.monitoring/5.metrics-server.md
Outdated
Show resolved
Hide resolved
.docs/content/0.armonik/components/3.armonik/1.control-plane.md
Outdated
Show resolved
Hide resolved
.docs/content/0.armonik/components/3.armonik/2.compute-plane/1.polling-agent.md
Show resolved
Hide resolved
infrastructure/utils/scripts/installation/prerequisites/install-k3s.sh
Outdated
Show resolved
Hide resolved
We need to explain ArmoniK to new users. I think that Core is not the entry point. |
Co-authored-by: Dylan Brasseur <[email protected]>
Co-authored-by: Dylan Brasseur <[email protected]>
Co-authored-by: Dylan Brasseur <[email protected]>
Co-authored-by: Dylan Brasseur <[email protected]>
Co-authored-by: Dylan Brasseur <[email protected]>
…l-k3s.sh Co-authored-by: Dylan Brasseur <[email protected]>
Co-authored-by: Dylan Brasseur <[email protected]>
Co-authored-by: Dylan Brasseur <[email protected]>
.docs/content/0.armonik/components/2.monitoring/5.metrics-server.md
Outdated
Show resolved
Hide resolved
…er.md Co-authored-by: Dylan Brasseur <[email protected]>
Co-authored-by: Dylan Brasseur <[email protected]>
Kudos, SonarCloud Quality Gate passed! |
This PR aims to refactor the documentation to facilitate the understanding of ArmoniK and to update script (corresponding to the update documentation).
To-do
Components explanationsMove to Explain components in ArmoniK #1035armonik_dev_environment.ps1
script (now that documentation is cristal clear and systemd exist, we no longer need to maintain this script)Rework guidesMove to Rework guides #1037Explanation
The main goal of this refactoring was to simplify and unify documentation on how a new user could install ArmoniK.
Documentation have now an installation section to easily find how to install ArmoniK without navigating through many folders from the GitHub UI.
Then, I added a way to install ArmoniK using the new native
systemd
in wsl2.And, because of code duplication, I unified the prerequisites installation script into a single file. Each program is in a separate file in order to facilitate understanding and updates. This modularity allows the user to install only the program needed.
Fix
fix #1018
fix #1015
fix #1012
fix #821