• 1 Post
  • 14 Comments
Joined 9 months ago
cake
Cake day: January 9th, 2026

help-circle

  • I started in August. Running docker containers on ubuntu server lts minimal, on a ryzen 3 3200g with 16gb ram.

    Running:

    • Jellyfin
    • RomM
    • Kiwix
    • Seafile
    • Beszel
    • Portainer
    • WUD
    • Pi-hole
    • Unbound
    • Caddy
    • Syncthing
    • Tailscale

    The domain has no website and no open ports, so Caddy handles routing and automated tls certification via api. External access only via tailscale, per user and per device approval process. Split horizon dns so domain names resolve direct routes to server on lan, and via tailnet from outside.

    500GB nvme OS drive rsynched nightly to a second matched nvme in the server. HDD data drives backed up using rsynch to matching sized drives in a DAS unit. Script dumps romm and seafile databases to hdd before rsynch Git pulls to data drive, captured in backup and Syncthing to separate device.

    Parallel Pihole and Unbound on a RPi5. RPi5 is primary dns for the lan to spread load, but the config master is the server, RPi is kept in sync with a one way feed from the main server using Syncthing.

    Looking into adding openclaw and ollama to play with, maybe use to monitor the server a bit more proactively. Need to plan out permissions and security so nothing dumb happens.



  • GMac@feddit.orgtoSelfhosted@lemmy.world•Observability Stack?
    link
    fedilink
    English
    arrow-up
    1
    ·
    15 days ago

    No auto updates thanks. 😅 I’ve just reset all my compose files to pin versions today after an unintended mariadb update cost me hours to repair. I’ll look into dockhand though. Was unimpressed at portainer’s announcement that new version wont have a community edition. Portainer is really just an ‘at a glance’ view for me since i try to do all the compose and troubleshooting stuff in terminal. Wud will probably become a thing i just review every few weeks to make sure i dont get too adrift from latest.

    I ought to look into a unified dashboard as i dont have easy visibility or things like disk usage, sheduled backup success etc that id like to see alongside the container status and beszel activity graphs.

    Im still quite new to it all though.





  • Not just soma, the censorship of the different, the unavailability of inconvenient history or information is a direct parallel to the echo chamber bubbles of social media, then constant advertising, that anything new must be more expansive, complex, and require more equipment that the pre-existing alternative.

    I think we worried too much about one book and not enough about the other. 1984 seems to be coming now that the BNW prepared the population into distracted acquiesence but where does that then lead? Do we become the eloi after that?

    I find the psychosocial parallels fascinating. Sorry if it seems a bit tinfoil…





  • Dont think that would be as secure. Once a phone has been unlocked after reboot, even if it has been locked again, the operating system and ram can be accessed quite easily with the correct tools and border controls have those tools.

    Even a Graphene phone is only properly secure before first unlock after reboot. So i would not personally rely on allowing acess to any profile. I would assume its possible, (probably trivial) to gain complete access from there.

    Any duress pin use should be covered under a person’s right to avoid self incrimination.

    If the phone is owned by your employer and they are the investigation target, then you might be on dodgy ground.