Skip to content

Latest commit

 

History

History
49 lines (39 loc) · 2.07 KB

INSTALL.md

File metadata and controls

49 lines (39 loc) · 2.07 KB
Raw

Installation

Prerequisites

You will need a machine from which to run Ansible (the "Ansible control" machine). You might find my ansible-control repo a useful starting point.

In addition, your target machine(s) should meet the following requirements:

  • Ubuntu or AlmaLinux installed (preferably minimal, for the cleanest results; I use Ubuntu Server 22.04 and AlmaLinux 9)
  • OpenSSH installed
  • A user account set up, with a password and sudo capability
  • Public/private keys set up for this user
  • python3 and python3-pip installed (don't be tempted to use, e.g. python39 - it may not be able to import the libraries Ansible requires for operation)
  • An internet connection, to download the necessary additional packages

Having installed your base operating system, it is recommended to update fully.

Setup and run

In brief (TODO: expand):

  1. Copy config.yml.example to config.yml and edit to suit your preferences (see annotations in that file)
  2. Copy ansible.cfg.example to ansible.cfg. Edit to specify your username on the machine to be configured and the path for your private_key_file
  3. Copy inventory.example to inventory. Enter your target machine[s] DNS name[s] or IP address[es].
  4. On your Ansible control machine, run ansible-galaxy install -r requirements.yml to pull down the required external roles
  5. Run ansible-playbook main.yml --ask-become-pass (once you've run the playbook, the default sudo group is given passwordless sudo, so you can drop the "--ask-become-pass" after that)

The final step will take a while, particularly during the installation of packages. Unfortunately Ansible does not have good facilities for showing progress during package installation. Patience will usually be rewarded; the installation make take minutes or hours, depending on the speed of your internet connection and hardware.

Note: for advanced use (e.g. during further development of the playbook), you can use [--skip-tags "tag1"] [--tags "tag2"] to skip or target specific features as required.