Selfhosted

60366 readers

731 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:

Detailed Rules Post

Be civil.
No spam.
Posts are to be related to self-hosting.
Don't duplicate the full text of your blog or readme if you're providing a link.
Submission headline should match the article title.
No trolling.
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details.

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 3 years ago

MODERATORS

curbstickle@anarchist.nexus

curbstickle_lw@lemmy.world

103

Selfhosting Sunday! What's up? (lemmy.nocturnal.garden)

submitted 9 months ago by tofu@lemmy.nocturnal.garden to c/selfhosted@lemmy.world

98 comments fedilink hide all child comments

With the recent discussions around replacing Spotify with selfhosted services and the possibilities to obtain the music itself, I've been finally setting up Navidrome. I had to do quite a bit of reorganization to do with my existing collection (beets helping a ton) but now it's in a neatly organized structure and I'm enjoying it everywhere. I get most of my stuff from Bandcamp but I have a big catalog from when I've still had a large physical collection.

I'm also still working on my docker quasi gitops stack. I've cleaned up my compose files and put the secrets in env files where I hadn't already, checked them into my new forgejo instance and (mostly) configured renovate. Komodo is about to get productive but I couldn't find the time yet. Also I need to figure out how to check in secrets in a secure way. I know some but I haven't tried those with Komodo yet. This close of my fully automated update-on-merge compose stacks!

I've also been doing these for quite a while and decided to sometimes post them in !selfhosting@slrpnk.net to possibly help moving a bit from the biggest Lemmy instance, even though this community as it is is perfectly fine as well as it seems.

What's going on on your servers? Anything you are trying to pursue at the moment?

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

[–] csm10495@sh.itjust.works 4 points 9 months ago* (last edited 9 months ago) (1 children)

I have a couple pis that run docker containers including pihole. The containers have their storage on a centralized share drive.

I had a power outage and realized they can't start if they happen to come up before the share drive PC is back up.

How do people normally do their docker binds? Optimally I guess they would be local but sync/backup to the share drive regularly.

Sort of related question: in docker compose I have restart always and yet if a container exits successfully or seemingly early in it's process (like pihole) it doesn't restart. Is there an easy way to still have them restart?

[–] MangoPenguin@lemmy.blahaj.zone 2 points 9 months ago (1 children)

You should be able to modify the docker service to wait until a mount is ready before starting. That would be the standard way to deal with that kind of thing.

[–] csm10495@sh.itjust.works 1 points 9 months ago (1 children)

What if it's a network mount inside the container? Doesn't the mount not happen till the container starts?

[–] MangoPenguin@lemmy.blahaj.zone 1 points 9 months ago

Correct yeah, you'd still need a way on the host to check if the mount is ready though before starting the service. Or you could just do a fixed delay time.