From b85288ee807d2679ca06e6dbf941829327163404 Mon Sep 17 00:00:00 2001 From: Marc Beninca Date: Fri, 23 Aug 2024 07:57:45 +0200 Subject: [PATCH] readme --- readme.md | 23 ++++++++++++----------- 1 file changed, 12 insertions(+), 11 deletions(-) diff --git a/readme.md b/readme.md index 93f2bda..f7e3c69 100644 --- a/readme.md +++ b/readme.md @@ -1,6 +1,6 @@ # Shell to Python Continuous Deployment -Get a common set of Python CI & CD commands\ +Get a common set of Python based CI / CD commands\ from various contexts of CA, DNS, CI and OS / OCI. --- @@ -10,7 +10,7 @@ from various contexts of CA, DNS, CI and OS / OCI. Project workflows can occur in: * an online or offline context, dealing with custom CA & DNS servers * various Continuous Integration platforms, with different workflow syntaxes -* specific Operating Systems, having different sets of commands and packages +* specific Operating Systems, having different commands and package names * specific containers for JavaScript based actions (ForgeJo, Gitea, GitHub) What if there was a unified way to do so? @@ -26,23 +26,23 @@ Picture it… * numbered * Certificate Authority armored certificates * Domain Name System servers IP addresses -* set group environment variables for - * ref names for deployment contexts of feature, staging & release - * alternate locations of - * Git repositories of this project & its parent framework - * Operating Systems & Software packages - * SSH key & hosts for deployments - * a standalone POSIX shell script payload +* ref names for deployment contexts of feature, staging & release +* alternate locations of + * Git repositories of this project & its parent framework + * Operating Systems & Software packages +* SSH key & hosts for deployments +* a standalone POSIX shell script payload ### Workflow files * calling the POSIX shell script payload as their very first step * using a unified YAML syntax made of actions implemented in Python -### Continous Integration & Deployment +### Integration & Deployment * configuring the Operating System container * installing Python system & virtual environments +* parsing common YAML syntax to launch Python actions --- @@ -50,7 +50,7 @@ Picture it… ### Features -Handle project workflows in a unified way: +SPCD handles project workflows in a unified way: * whether the network infrastructure is * [X] online @@ -233,4 +233,5 @@ Handle project workflows in a unified way: ### Later +* automate versions fetching * turn readme into documentation