Intro
Asgard is the name chosen for managing the v2 of infastructure created by me - jikaven.
The first version of this adventure was named Olympus, so it felt right to change the second iteration in a simmilar fashion. Asgard contains my experiments with IaC, GitOps tools and other adventures that I have had.
Edda is the first thing created under Asgard as it is intended for everything to be documented and by the looks of it, You have found it!
This documentation is not a "TODO" guide. It's the way I created my infrastructure documentated for future me. If anything, there might be misconfigurations or other things that need to be addressed and I will be thankful if you point them out!
Metodology
Before starting Asgard, I enjoyed creating and storing configuration and build commands instead of clicking through menus and typing adhoc commands. This meant that once something was broken, I could nuke everythign and start from scratch, whilst maintaining the configurations and not losing all of the work I had done.
This is why for Asgard, I wanted to create EVERYTHING (or at least as much as possible) in code. Of course, this would come at a cost - my mental state, but I think it's worth it. Especially if I learn something in the end.
Overall the main takeaways and key points are:
- Use code or config files to store everything;
- All changes and most importantly choices need to be documented (here in Edda);
- Everything should be done following KISS: Keep it simple, stupid;