Selfhosted

53095 readers

754 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

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz

224

I made a project that can install/configure/orchestrate 115+ applications on your homelab using Ansible! (github.com)

submitted 1 week ago by Dylancyclone@programming.dev to c/selfhosted@lemmy.world

15 comments fedilink hide all child comments

Hi! I wanted to share a project I've been working on that lets you set up a huge variety of applications really quickly and painlessly. For example, instead of setting up and configuring a large docker compose for a complicated application like Immich, this playbook lets you simply write:

immich_enabled: true

And it will orchestrate all the containers, networks, directories, etc for you with reasonable defaults. All of which can be overwritten, for example to enable extra features like hardware acceleration:

immich_hardware_acceleration: "-cuda"

Or to automatically get a letsencrypt cert and expose the application on a subdomain to the outside world:

immich_available_externally: true

Included in the playbook is a ton of complicated applications, like Paperless, Meelo, TTRSS, Dawarich, as well as common self-hosted apps like Jellyfin, Home Assistant, Syncthing, Navidrome, Grafana, and a whole lot more (totaling 116 right now!).

It also comes with scripts and tests to help add your own applications (ansible roles) and ensure they work properly

I've been using this project myself for awhile, including to assist with moving from one homelab computer to another (point the playbook to the new address, run it to install everything, and restore a backup from the previous computer for data), and I hope it can help someone else build up their homelab without sinking too much time into setting things up

Here's the repository: https://github.com/Dylancyclone/ansible-homelab-orchestration

And the documentation (that I'm really proud of :D): https://dylancyclone.github.io/ansible-homelab-orchestration/

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

[–] AgaveInMyAss@lemmy.world 4 points 1 week ago (2 children)

This is probably my lack of Ansible experience here but how are multiple servers setup? Can I specify a different server per application?

[–] exu@feditown.com 9 points 1 week ago

You can use host_vars to set different variables per host. You'd still run the same playbook against both hosts, but each has different services activated.

Make the folder host_vars in the repo root
Make subfolders for every host with their hostname
Enable services you want by writing the variables into a yaml file for your host (any file name as long as it ends with .yml
Write an Ansible inventory for your hosts
Run the playbook with your inventory

Slightly fancier would be using group_vars instead, you can add a host to multiple groups. Then deploying the same services on a new hosts would simply be adding it to the group

[–] mumblerfish@lemmy.world 7 points 1 week ago

TL;DR: yes

Just from a quick view of the repo, the simplest way to do it would be to look at the playbook.yml and copy all roles you want for a host into a new playbook, say myhost.yaml. Copy not only the roles but all the other keywords as well. Then you go to the inventory and add your hosts where you to execute the playbook against. Then you change the hosts key value in the playbook you made from all to the hosts you added to the inventory.

That is, add your hosts to the inventory, create playbooks for for them and run. That is the easiest. Read up on how to do groups and organizing your inventory to improve it from there.