Elaborated further on the nature of the project and added some sections explaining some aspects of current logic
This commit is contained in:
		
							
								
								
									
										24
									
								
								README.md
									
									
									
									
									
								
							
							
						
						
									
										24
									
								
								README.md
									
									
									
									
									
								
							@@ -1,3 +1,25 @@
 | 
				
			|||||||
# SUKAATO Ansible
 | 
					# SUKAATO Ansible
 | 
				
			||||||
 | 
					
 | 
				
			||||||
Automates the implementation of VPS servers for my server ecosystem. There is a specific logic and structure to this project, that will be expounded on herein.
 | 
					This repository is for automating the management of the configuration of, and the provisioning of software for, my virtual private servers using [Ansible](https://www.redhat.com/en/ansible-collaborative?intcmp=7015Y000003t7aWQAQ). This repository is especially useful for setting up the virtual private server(s) that is(/are) to host and serve my website(s). It is also meant to be useful for provisioning of software and the configuration of that software for personal or household LAN computers.
 | 
				
			||||||
 | 
					
 | 
				
			||||||
 | 
					## Installation and Use
 | 
				
			||||||
 | 
					
 | 
				
			||||||
 | 
					All files with file extension `.example` must be converted to [YAML](https://yaml.org/) files that follow their semantics and naming (or follow the minimum bare "namespace" nesting for dictionaries or lists thereof) *prior* to executing any given [play or task](https://docs.ansible.com/ansible/latest/playbook_guide/playbooks_intro.html). For more on semantics and naming conventions see the [mini-documentation](#mini-documentation).
 | 
				
			||||||
 | 
					
 | 
				
			||||||
 | 
					> [!IMPORTANT]
 | 
				
			||||||
 | 
					> Keep in mind files with the `.example` extension may also be present recursively under given [role](https://docs.ansible.com/ansible/latest/playbook_guide/playbooks_reuse_roles.html) directories (i.e., under path `${SUKAATO_ANSIBLE_PROJECT}/.ansible/roles/**/**/`).
 | 
				
			||||||
 | 
					
 | 
				
			||||||
 | 
					## Mini-Documentation
 | 
				
			||||||
 | 
					
 | 
				
			||||||
 | 
					### Available Roles
 | 
				
			||||||
 | 
					
 | 
				
			||||||
 | 
					To surmise, the available or planned [roles](https://docs.ansible.com/ansible/latest/playbook_guide/playbooks_reuse_roles.html) are as follows (and are all found under `${SUKAATO_ANSIBLE_PROJECT}/.ansible/roles`):
 | 
				
			||||||
 | 
					
 | 
				
			||||||
 | 
					role name | purpose
 | 
				
			||||||
 | 
					---|---
 | 
				
			||||||
 | 
					lockdown | creating initial `sudo`-capable user, disabling system/SSH root login, setting up key-based SSH authentication, transferring GPG keys, configuring environment, hardening system
 | 
				
			||||||
 | 
					bootstrap | installing programming language and server/container packages, installing extra system managers and essential utilities, configuring and running servers/services/containers
 | 
				
			||||||
 | 
					postinstall | installing and configuring custom sets of packages, largely non-server related and not essential
 | 
				
			||||||
 | 
					
 | 
				
			||||||
 | 
					> [!TBC]
 | 
				
			||||||
 | 
					> This README is yet unfinished. Check back later.
 | 
				
			||||||
 
 | 
				
			|||||||
		Reference in New Issue
	
	Block a user