Selfhosted

40329 readers

368 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago

MODERATORS

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz

Homeserver Ansible Playbook (github.com)

submitted 6 months ago by Tywele@lemmy.dbzer0.com to c/selfhosted@lemmy.world

20 comments fedilink hide all child comments

After getting fed up with TrueNAS (after it borked itself for the third time and I would have had to set it up AGAIN) I decided to learn Ansible and write a playbook to setup my homeserver that way.

I wanted to share this playbook with you in case someone might find it useful for their own setup and maybe someone has some tips on things I could improve.

This server will not be exposed to the public/internet. If I want to access a service on it from outside my home network I have Wireguard setup on my router to connect to my home network from anywhere.

Keep in mind that I'm relatively new to sysadmin stuff etc so don't be too harsh please 😅

you are viewing a single comment's thread
view the rest of the comments

[–] idefix@sh.itjust.works 4 points 6 months ago (2 children)

Nice, well done. I wish I could find the same for Debian.

[–] BrianTheeBiscuiteer@lemmy.world 7 points 6 months ago (2 children)

DebOps my dude.

[–] idefix@sh.itjust.works 3 points 6 months ago

Thanks!

[–] k_rol@lemmy.ca 1 points 6 months ago

Thx I had no idea!

[–] Tywele@lemmy.dbzer0.com 3 points 6 months ago (1 children)

It should be pretty easy to adapt it for Debian. The only thing you need to change as far as I can see is the usage of the dnf module to the apt module.

[–] vortexsurfer@lemmy.world 2 points 6 months ago (1 children)

If you want to make your playbooks/roles more universal, there's a generic package module which will figure out what package manager to use based on the detected OS.

Or, if that doesn't fit your needs, you can add conditions to tasks (or blocks of tasks), like

when: ansible_os_family == "Debian"

and use that for tasks specific to a given Linux distro/family.

Ansible will detect a lot of info about each host and make it available as facts. See for example https://docs.ansible.com/ansible/latest/playbook_guide/playbooks_vars_facts.html

[–] Tywele@lemmy.dbzer0.com 1 points 6 months ago

I know but I also learned that it's generally better to use the specific module for the package manager (just can't remember why from the top of my head) and I never intended this playbook to be generally usable.