AzuraTheSpellkissed

@AzuraTheSpellkissed@lemmy.blahaj.zone

• ⁨Comment⁩ on ⁨Question about using gluetun for other containers⁩ ⁨⁨4⁩ ⁨days⁩ ago⁩:

  Afaik you don’t need the depends_on at all, it’s basically implied. If you configure the container to use gluetun’s network, it shouldn’t just bypass it even if there’s any problem with the gluetun container. The gluetun documentation also says to just use network_mode: container:gluetun, even when connecting from a divergent compose.yaml. if you want to be sure, maybe test out what happens if that gluetun is down.

• ⁨Comment⁩ on ⁨Looking for a tool for browsing contents of unmounted cold storage⁩ ⁨⁨2⁩ ⁨weeks⁩ ago⁩:

  I like to use ncdu snapshots (“exports”). ncdu is an interactive file browser / disk usage analyzer with a terminal UI, which allow for convenient browsing but also, y’know, figuring out what to delete in case of storage cleanups.

  creating a snapshot (“exporting”):
  ncdu /pathyouwanttoscan -2 --one-file-system --compress -o snapshot_ncdu.json.zstd

  (-2 enables progress bar and error messages during the scan)

  reading (“importing”):
  ncdu -f snapshot_ncdu.json.zstd

• ⁨Comment⁩ on ⁨[deleted]⁩ ⁨⁨3⁩ ⁨weeks⁩ ago⁩:

  Why do you ask what “made it look like slop” instead of being honest about it?

• ⁨Comment⁩ on ⁨Caddy and multiple subdomains/reverse proxies⁩ ⁨⁨3⁩ ⁨weeks⁩ ago⁩:

  That would be great. Though I’ve had that not work as expected at the beginning of 2026, but maybe you are right.

• ⁨Comment⁩ on ⁨Caddy and multiple subdomains/reverse proxies⁩ ⁨⁨3⁩ ⁨weeks⁩ ago⁩:

  Note that you are likely leaking a list of all your subdomains in certificate transparency logs. Some users might not want that to happen, in that case using a wildcard certificate can help, but it’s either more tedious to set up (generating the cert outside of caddy) or less readable (using a Caddyfile with a single domain block for the wildcard containing a handle block per subdomains).

• ⁨Comment⁩ on ⁨Bitwarden Switches to Commercial License⁩ ⁨⁨5⁩ ⁨weeks⁩ ago⁩:

  I’m not saying that’s great news, but it doesn’t sound like the self destruction move that some OSS companies have done recently. I wouldn’t migrate away just because of that change. In the end, they have to find a sustainable mode of operation.

• ⁨Comment⁩ on ⁨Bitwarden Switches to Commercial License⁩ ⁨⁨5⁩ ⁨weeks⁩ ago⁩:

  As always, people overreacting in the comments (of the linked forum). So the current plan is that the core remains OSS, but upcoming features are partially not. To me that sounds similar to Chrome’s or VSCode’s approach.

• ⁨Comment⁩ on ⁨looking for lightweight ghost blog alternative⁩ ⁨⁨5⁩ ⁨weeks⁩ ago⁩:

  Ah, right its stored as (rather basic) html instead of markdown.

• ⁨Comment⁩ on ⁨looking for lightweight ghost blog alternative⁩ ⁨⁨5⁩ ⁨weeks⁩ ago⁩:

  I love ghost’s UI and feature set.

  What complex data format are you taking about? Last time I checked, it was plain markdown in a database (even supporting sqlite).

  What I’d recommend though, is coupling it with a static site generator and only using the ghost server for the administration / authoring (guides). That way, serving the blog to visitors is basically free in terms of resources (at last as low as it gets). You could even push these static builds to a CDN (yes yes, selfhost community, I’m just saying it for completeness)

  It might be some hassle to set this up somehow, but you could even have the container stopped unless you actively need it. You could even run the server application on your computer instead of the server, unless you want to access is from a smartphone/tablet.