spoljarevic/Ansible
spoljarevic/Ansible
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
The Ansible Playbooks I use via CLI and Semaphore UI. Ditch boring and repetitive tasks by automating your Homelab and IT-Infrastructure. https://donate.spoljarevic.sh
68 commits 1 branch 0 tags 111 KiB
Find a file
Exact
Luca Matteo Spoljarevic ff07cc9e8a
 AI generated proton vpn toggle. Works on my machine idiot *~*
2026-05-06 19:52:25 +02:00
Bash-Scripts to Ansible AI generated proton vpn toggle. Works on my machine idiot *~* 2026-05-06 19:52:25 +02:00
checks Changed package manager detection 2025-12-15 11:36:11 +01:00
configuration Decided to publish the code (was a private Repo of Who2Industries). Needs testing since it was written by ai before it can be used! 2026-02-07 02:26:02 +01:00
deployment Delete deployment/kubernetes/inventory-test.ini 2026-03-10 12:44:17 +01:00
health Fixed errors 2025-11-21 19:46:17 +01:00
installation Removed weird git stuff, no clue what happened there 2026-03-25 17:34:52 +01:00
LICENCE.MIT Renamed Licence to Lincence.mit to make the type clear without the need to open it 2026-02-19 01:29:29 +01:00
README.md Updated README file 2026-02-26 02:10:07 +01:00

README.md

Notes about this Project

All the code gets published to Codeberg. All other platforms are just mirrors.

Issues, pull requests, and everything else will only be looked at on codeberg.org.

Ansible Playbooks for Semaphore UI

Explanation

In this playbook, you'll be able to see a lot of Ansible Playbooks for a lot of different use cases.

I designed them to work seamlessly with SemaphoreUI, an RHAAP (Red Hat Ansible Automation Platform) alternative.

That's why in most of the playbook, the host is set to all since the correct Inventory can be added in SemaphoreUI within seconds.

Branches

At the moment, there are two branches. The master branch contains tested and production ready playbooks.

On the development branch, I push Playbooks that might not be finished yet.

They are still in the testing phase and should only be used at your own risk.

Goal of this Repository

If you're in IT like me, you know that automation is key.

I try to automate every task that is repeditive or complicated to reduce time waste and user errors.

For example, the archinstall playbook, which currently revieves a complete overhaul as seen here, saved me around 5 to 7 hours of manually doing post-installation on my Arch Linux OS. After this overhaul, it's supposed to save even more time.

So as you can see, these are not just for playing around, but for real world use cases.

MIT License

This Repository is released under the MIT License, which can be viewed here.

What that means is basically that you can do whatever you want with what's in here, including selling it, as long as you include the copyright notice.