Selfhosted

40645 readers

303 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 2 years ago

MODERATORS

[email protected]

Homeserver Ansible Playbook (github.com)

submitted 7 months ago by [email protected] to c/[email protected]

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

[–] [email protected] 9 points 7 months ago (1 children)

If I read this correctly, Immich is setup entirely through Ansible, no docker compose. That's fine, however if Immich changes something drastically in their setup topology, it'll be more work for you to implement those changes. For services that use docker compose, you could use Ansible to deploy a compose file in a dir, say /opt/immich-docker along with its requisite .env and other files. Then setup running it via systemd. Then when you need to update it, it's almost copy-paste from the upstream compose file into your Ansible repo.

[–] [email protected] 2 points 7 months ago (1 children)

Heck, you could do a pre-stage play where you delegate to localhost an ansible.builtin.get_url to download the compose file before doing the rest.

[–] [email protected] 6 points 7 months ago* (last edited 7 months ago)

I wouldn't do that because I'd be inevitably picking up breaking changes without my knowledge that I'd have to fix after the fact. Unless you're pulling from a tag I guess. Still storing along the playbook feels more robust. It's less likely to get any surprises. Also I'm working under the assumption that you want to write idempotent code so you don't get breakage when your rerun it, which allows to run it on a schedule, to ensure your config doesn't drift too much.