Selfhosted

41615 readers

392 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

Remote deployments of different capabilities (self.selfhosted)

submitted 3 days ago by Dust0741 to c/selfhosted

3 comments fedilink hide all child comments

I have a collection of my docker composes and configs. I would like to have the ability to remotely (over Tailscale) deploy and manage remote servers.

This isn't necessarily for redundancy, but I would like an automated way to test and deployments.

I want to make a seperate homelab at my parents that I can remotly manage for them. I have multiple servers at home, so having all of the config in a git repo, and having my secondary computer use the test branch would be super nice.

My ideal scenario:

So say I want jellyfin. I make a compose and config on the test branch. It automatically applies to my test server. Once I confirm it works, it goes to the master branch. Then it gets applied to the production servers.

Can this be done? If so, can Forgejo actions do it?

top 3 comments

sorted by: hot top controversial new old

[–] [email protected] 4 points 3 days ago* (last edited 3 days ago) (2 children)

I already replied to your last post, but my reply here is the same. You want kubernetes and gitops. There exists many ways to do staging/preprod/prod setups with gitops.

[–] [email protected] 2 points 3 days ago

Or a git repo and ansible/semaphore, thats how I manage my docker services. I have a git repo with all my configs and compose files (not in github, but my own server), then in semaphore I have a playbook to update a compose or swarm stack.

[–] Dust0741 1 points 3 days ago* (last edited 3 days ago)

Thank you for the replies. Do you have an sources to start my research on this more in depth?

Edit: I see you mentioned some in the other post. Thank you