Compare commits

..

No commits in common. "c0557813eb03ea221d794fa1657cb4872dcad26a" and "b85288ee807d2679ca06e6dbf941829327163404" have entirely different histories.

View file

@ -28,12 +28,8 @@ Picture it…
* Domain Name System servers IP addresses
* ref names for deployment contexts of feature, staging & release
* alternate locations of
* Git repositories of this project & its parent framework
* Operating Systems & Software packages
* Git repositories of
* this project
* its parent framework
* projects not available in some distributions
* shunit2
* SSH key & hosts for deployments
* a standalone POSIX shell script payload
@ -44,34 +40,9 @@ Picture it…
### Integration & Deployment
#### Shell
* [X] setting up the chosen Operating System container
* [X] Domain Name System resolving
* [X] package manager configuration & repositories
* [X] Certificate Authorities trusting
* [X] Operating System updating
* [X] installing Git to clone
* [X] this project
* [X] its parent framework
* [X] installing both Python
* [X] system environment
* [X] virtual environment
* [X] generating a Python module to switch context
#### Python
* [X] setting up an OpenSSH client
* [X] known hosts
* [ ] private key
* [ ] and finally parsing commands from
* [X] system
* [ ] workflow
* [ ] to run available actions
* [ ] check project
* [ ] build project
* [X] browse workspace
* [ ] synchronize
* configuring the Operating System container
* installing Python system & virtual environments
* parsing common YAML syntax to launch Python actions
---
@ -79,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
@ -186,7 +157,7 @@ Handle project workflows in a unified way:
### For
* People feeling the need to aim for consistency in the CI / CD universe
* People feeling the need to aim for consistency in the CI & CD universe
---