Selfhosted

60001 readers

698 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.
Posts here are to be centered around self-hosting. Please ensure it is clear in your post how it relates to self-hosting.
Don't duplicate the full text of your blog or git here. Just post the link for folks to click.
Submission headline should match the article title.
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 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

[–] raldone01@lemmy.world 3 points 9 months ago* (last edited 1 month ago) (1 children)

In linux user and group names don't matter. Only the gid and uid matter. Think of user and group names as human names like domains are for IPS.

In docker when you use mounts, all your containers that want to share data must agree on the gid and uids.

In rootless docker and podman the subuids and subgids make it a little more complicated since IDs get mapped between host and container, but its still the IDs that matter.

[–] Kaldo@fedia.io 1 points 9 months ago

I have one .env file with UUID/GUID 1000 set for all docker services in the docker-compose so it would make sense in theory if that's enough, but it seems it rarely is...