mirror of
https://github.com/DO1JLR/ansible_playbook_servers.git
synced 2024-09-14 19:53:56 +02:00
|
|
||
|---|---|---|
| .. | ||
| do1jlr.acmetool@eaf3617f6b | ||
| do1jlr.admin_base@7d430bec45 | ||
| do1jlr.ansible_version@2bf5d7c436 | ||
| do1jlr.auth@1b60b7da3a | ||
| do1jlr.avahi_client@9e0ac15d20 | ||
| do1jlr.dotfiles@348ea9a127 | ||
| do1jlr.dovecot@07e9cc918f | ||
| do1jlr.mailserver_preperation@ff1fb3952f | ||
| do1jlr.nginx@e2e4a10595 | ||
| do1jlr.ntp@c3fabc5fc6 | ||
| do1jlr.ranger@dafcaefe12 | ||
| do1jlr.rspamd@1a34c90b44 | ||
| do1jlr.rtl_nic_firmware@7b2d2adbb9 | ||
| do1jlr.sshd@15b7867a37 | ||
| do1jlr.unbound@2f26c3e27e | ||
| do1jlr.users@9203f239c6 | ||
| do1jlr.webhost@c8d0feb203 | ||
| do1jlr.weechat@8d80bd750d | ||
| gantsign.bat@dae043fe28 | ||
| geerlingguy.firewall@0dfa0689d0 | ||
| geerlingguy.mysql@d29da05560 | ||
| geerlingguy.postgresql@7f20fe244b | ||
| l3d.etebase@944fb8b73e | ||
| l3d.homebox@e11f365fba | ||
| l3d.nginx_exporter@05a970b942 | ||
| l3d.packages@76941650c1 | ||
| l3d.rustdesk@f40187808a | ||
| mailserver_dovecot | ||
| postfix@d104fdf714 | ||
| robertdebock.dovecot@db11ad4b80 | ||
| robertdebock.fail2ban@7c531fe59f | ||
| unattended_upgrades@9717a3d27b | ||
| 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