BobsAccountant

@BobsAccountant@lemmy.world

• ⁨Comment⁩ on ⁨Interesting media, podcasts, shows, blogs on topic of self-hosting you like?⁩ ⁨⁨6⁩ ⁨days⁩ ago⁩:

  I like Self-hosted Show, as well. Sometimes it feels like they talk about a subject immediately after I start looking into it. The home lab zeitgeist can be eerie, I guess.

• ⁨Comment⁩ on ⁨What do you use for notes?⁩ ⁨⁨1⁩ ⁨week⁩ ago⁩:

  A little rough, to be honest. It’s a docker-compose deployment, but it requires you to run make to deploy it. The makefile does extra configuration and such to allow the containers to come up healthy. It works, but it’s overcomplicated and styled after their own deployments, so probably way more compute than what is needed for one household.

• ⁨Comment⁩ on ⁨What do you use for notes?⁩ ⁨⁨1⁩ ⁨week⁩ ago⁩:

  I’ve been using this, as well. They default to hosting your “vault.” It does peer-to-peer syncing, if you don’t want to have a server involved at all. I’m running their self-hosted server, but that’s only after I decided that AnyType was what I was looking for. I really like that it’s object based, so you can create templates for things like meetings that are their own type, separate from a bog-standard page.

• ⁨Comment⁩ on ⁨Best Filesystem for NAS?⁩ ⁨⁨11⁩ ⁨months⁩ ago⁩:

  Adding on to this:

  These are all great points, but I wanted to share something that I wish I’d known before I spun up my array… The configuration of your array matters a lot. I had originally chosen to use RAIDZ1 as it’s the most efficient with capacity while still offering a little fault tolerance. This was a mistake, but in my defense, the hard data on this really wasn’t distributed until long after I had moved my large (for me) dataset to the array. I really wish I had gone with a Striped Mirror configuration. The benefits are pretty overwhelming:

  • Performance is better than even RAIDZ2, especially as individual disk size increases.
  • Fault tolerance is better as you could have up to 50% of the disks fail, so long as one disk in a mirrored set remains functional.
  • Fault recovery is better. With traditional arrays with distributed chunks, you have to resilver (rebuild) the entire array, requiring more time, costing performance and shortening the life of the unaffected drives.
  • You can stripe mismatched sets of mirrored drives, so long as the mirrored set is identical, without having the array default to the size of the smallest member. This allows you to grow your array more organically, rather than having to replace every drive, one at a time, resilvering after each change.

  Yes, you pay for these gains with less usable space, but platter drives are getting cheaper and cheaper, the trade seems more worth it than ever.

• ⁨Comment⁩ on ⁨Is anyone successfully running Nginx in opnsense?⁩ ⁨⁨1⁩ ⁨year⁩ ago⁩:

  The same front end? Nah it has it’s own menus and such. If you’re familiar with the anatomy of the conf files you can piece each sub-menu within the plugin to it’s corresponding section in the conf. Not everything that I need was represented. There is a way to inject custom blocks, but it’s pretty cumbersome.

  Honestly? I’m considering going back to a dedicated nginx host for two reasons. Firstly it’s just easier to configure. Secondly, I’m sending internal traffic to the public DNS addresses for some of the services and I’m not 100% positive those fuck-heads over at Comcast aren’t charging me for the hairpin route. If I had a local, internal proxy, I could avoid that.