Go to file
Radar231 c8fd01f0a8 added ansible adhoc command to check daily backup results 2024-03-31 09:32:38 -04:00
collections resetting repository 2023-12-22 13:42:13 -05:00
inventory updated for vps changes 2024-03-30 19:10:04 -04:00
roles added filebrowser deploy role 2024-03-24 19:31:03 -04:00
README.md resetting repository 2023-12-22 13:42:13 -05:00
adhoc_ck-daily-backups.sh added ansible adhoc command to check daily backup results 2024-03-31 09:32:38 -04:00
adhoc_ck-distros.sh resetting repository 2023-12-22 13:42:13 -05:00
adhoc_ck-kernels.sh resetting repository 2023-12-22 13:42:13 -05:00
adhoc_ck-lxd.sh resetting repository 2023-12-22 13:42:13 -05:00
adhoc_ck-ups.sh resetting repository 2023-12-22 13:42:13 -05:00
adhoc_ck-uptimes.sh resetting repository 2023-12-22 13:42:13 -05:00
adhoc_ck-vm-disks.sh added new adhoc script 2024-01-31 11:17:59 -05:00
adhoc_ck-vps-crowdsec.sh disabled firewall check 2024-01-14 20:59:09 -05:00
adhoc_get-facts.sh updated host inventory 2024-01-12 20:15:07 -05:00
mk_dev_env_links updated dirs to git.lan 2024-03-21 09:12:28 -04:00
update_collections.sh resetting repository 2023-12-22 13:42:13 -05:00
update_roles.sh resetting repository 2023-12-22 13:42:13 -05:00

README.md

Ansible development environment configuration

Introduction

This is a skeleton for my ansible development environment.

Configuration

The location of playbook directory, this skeleton directory, and the target dev env directory are contained in variables at the start of the 'mk_dev_env_links' script.

Initialize a development environment

To initialize a new dev env, create a new directory for the environment, and copy the 'mk_dev_env_links' script into it. From within the dev env directory, run the 'mk_dev_env_links' script.

The 'mk_dev_env_links' script will populate the directory with symlinks pointing to the applicable ansible playbooks, collections and roles subdirectories, each of which contain requirements.yml files. It will also symlink any miscellaneous support scripts required for the dev env.

Once the symlinks have been created you can initialize any roles or galaxy collections required for the environment by running the 'update_roles.sh' script.