mirror of https://github.com/DO1JLR/ansible_playbook_servers.git synced 2024-09-14 19:53:56 +02:00

History

L3D cbd376396b update module and ansible config		2020-12-23 17:09:14 +01:00
..
acmetool2@06f6215431	web site deployment ongoing	2020-12-23 01:17:14 +01:00
base@ca00bca0f1	define webserver	2020-12-13 00:10:12 +01:00
bat@430331438f	define webserver	2020-12-13 00:10:12 +01:00
dotfiles@05ff3aec13	define webserver	2020-12-13 00:10:12 +01:00
nginx2@642aa37a60	update module and ansible config	2020-12-23 17:09:14 +01:00
ranger@a97cf9b55b	Initial commit	2020-12-12 23:42:36 +01:00
ssh_auth@bf16a2583f	update module and ansible config	2020-12-23 17:09:14 +01:00
sshd@db846c9dc6	update module and ansible config	2020-12-23 17:09:14 +01:00
users@3dc308270b	update sshd	2020-12-20 22:33:01 +01:00
webhost2@7a7a04e45d	web site deployment ongoing	2020-12-23 01:17:14 +01:00
README.md	Initial commit	2020-12-12 23:42:36 +01:00

README.md

Subfolders to include ansible roles.

All roles should be included in this subfolder. This is usually done as git submodule.

The most common command needed for this is:

git submodule add <public_path_to_gitrepo.git> <submodule_destination>

A simple way to checkk out the latest commit at the main branch for all submodules is:

git submodule foreach "(git checkout $(git symbolic-ref --short refs/remotes/origin/HEAD | sed "s@^origin/@@"); git pull)"

In abstract terms, the easiest way to do this is to treat submodules like normal git repositories after you have cloned them. This means checking out the main branch, committing things and similar actions. And when the local changes to submodule git repo are complete, add the new commit hash of submodule indein main git repo by adding, committing and pushing the entire submodule like an updated file.

Further information is also available at git-scm.com/docs/git-submodule