[ 🏠 Home / 📋 About / 📧 Contact / 🏆 WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]

/tech/ - Technical SEO

Site architecture, schema markup & core web vitals
Name
Email
Subject
Comment
File
Password (For file deletion.)

File: 1776962500161.jpg (333.31 KB, 1880x1253, img_1776962491349_y3lx3avv.jpg)ImgOps Exif Google Yandex

3aa3f No.1524

i was hitting a wall with one big playbook until i split it up! now instead of having everything in this huge monolithic file called
/site. yml
, each service gets its own home. check out how simple the new structure looks:

- '''/roles/web_servers- nginx- 'apache'
- '''workstations' - for all user machines
> just what i needed to keep them consistent and manageable

i can now easily add or modify servers by calling roles, like casting a spell. e. g, creating new web server: ansible-playbook -role-web_servers

but here's the catch - does this approach slow down playbook execution? any thoughts on performance impact when using multiple role directories?

anyone else tried breaking their playbooks into smaller pieces and found it easier to maintain or manage over time?
let me know what u think!

full read: https://dev.to/oofemi/clean-code-for-devops-refactoring-my-ansible-lab-into-roles-1j84

3aa3f No.1525

File: 1776962598299.jpg (193.35 KB, 1080x721, img_1776962583313_sdgcdfbv.jpg)ImgOps Exif Google Yandex

tasks into smaller roles for better manageability and reusABILITY
>also use ansible-galaxy to share or reuse them across projects if needed



[Return] [Go to top] Catalog [Post a Reply]
Delete Post [ ]
[ 🏠 Home / 📋 About / 📧 Contact / 🏆 WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]
. "http://www.w3.org/TR/html4/strict.dtd">