• 0 Posts
  • 21 Comments
Joined 1 month ago
cake
Cake day: November 21st, 2025

help-circle
  • Yeah, I hate facebook too, but sometimes you just have to acknowledge that flying the FOSS flag is not your primary objective. Like someone else said, if you have half the people on whatsapp, you’ll get much less than that with anything else.

    I occasionally dream of having a better “community” in my suburb but basically, I just have zero available effort to invest in that. Like I’m not working today and looking forward to spending the afternoon in my pyjamas fiddling around at home. If I feel super motivated and energetic later I might take the kids somewhere. If there were a community thing scheduled I just… wouldn’t feel like going.

    I think the best form of community I can manage is simply having a few people’s numbers in my phone and telling them when something happens “Hey Barb, just letting you know the neighbours car got broken into last night, hows things down your end?”



  • Containers have layers. So if you create an instance of a syncthing container whoever built that container would have started with some other container. Alpine linux is a very popular base layer, just used as an example in this discussion.

    When you download an image, all the layers underlying the application that you actually wanted, will only be as fresh as the last time the maintainer built that image. So if there were a bug in the alpine base, that might have been fixed in alpine, but wouldn’t by pushed through to whatever you downloaded.




  • This is me.

    For example, /srv/docker/synching contains:

    compose.yml .env ./Sync

    That last one is a directory bound to the container which contains all my sync folders.

    Occasionally it makes more sense to put the mounted folder in /srv like /srv/photos is mounted by /srv/docker/photoprism/compose.yml

    However, thats a rarity. Things mostly accessed by a single compose stack are kept alongside the other files for that stack.














  • fizzle@quokk.autoSelfhosted@lemmy.worldDocker security
    link
    fedilink
    English
    arrow-up
    5
    ·
    17 days ago

    I basically just avoid exposing ports from containers unless I really do want them exposed on the host?

    Most services go through my reverse proxy, traefik.

    Things like databases don’t publish ports on the host because they’re only accessed internally, using their container name.