Ooh, that’s a useful thing to know about! Thanks!

You’re getting ragged on but I would very much prefer an approach with these things that used some sort of modular system.

I’m imagining the service would have the option for “address for communication bridge” and it’d pass messages to it using JSON or something. The communication bridge would then decide which medium that would go through (email, SMS, smoke signals, whatever the owner configures).

As far as the service is concerned messages come and go (or just go) and how that side of things works isn’t its problem. It’d also mean that one could configure fallback messaging mediums and use dummy ones for if one doesn’t want anything like that (much like the “emails print to the console” debug tool Django has).

I don’t know what’s worth tagging and what isn’t. I don’t know which tags are popular and so have followers vs. which ones aren’t.

The information exists but isn’t presented anywhere convenient.

If I have to do homework before posting a picture I’m massively more inclined not to bother, which isn’t particularly good for the Fediverse.

I would love something that could give me suggestions for relevant and popular hashtags for my content.

At least for me it’s /etc/caddy/CaddyFile

Can you give us your config file?

I found the whole experience tremendously frustrating and as you can see from some of the other responses and votes, the community does not consider that to be a reasonable reaction.

Hence why I bailed on the whole thing. I don’t need the grief.

I was told a tool was a resilient approach to drive management. It wasn’t, outside of a very specific set of circumstances.

Your analogy not only makes no sense but is exactly why I’m hostile about this. I’m not an expert at the specific limitations of a niche hard disk technology is, I must be a fucking moron or something, and ridicule is a clearly an appropriate reaction.

My idea of a useful tool for dealing with hard disks is not one that loses its shit when a hard disk is temporarily disconnected. That is not a ridiculous assumption. If that’s an issue then that should be made abundantly clear.

I assigned drives based on serial number and passed them through to TrueNAS and it couldn’t handle that reliably. I do not think I was asking for the moon on a stick.

The USB interface is a temporary measure, I was going to move the disks to an internal setup after testing but if it can’t handle something that basic then like fuck am I trusting it with something like migrating from USB SATA to internal SATA.

If I need both disks to access mirrored data then it’s as useful as a chocolate teapot.

I was trying to use it for a mirrored setup with TrueNAS and found it to be flakey to the point of uselessness. I was essentially told that I was using it wrong because I had USB disks. It allowed me to set it up and provided no warnings but after losing my test data for the fifth time (brand new disks - that wasn’t the issue) I gave up and setup a simple rsync job to mirror data between the two ext4 disks.

If losing power effectively wipes my data then it’s no damn use to me. I’m sure it’s great in a hermetically sealed data centre or something but if I can’t pull one of the mirrored disks and plug it into another machine for data recovery then it’s no damn good to me.

Looks like I angered people by not loving ZFS. I don’t feel like being bagged on further for using it wrong or whatever.

Edit: elaborated, got bagged on. Shocked Pikachu face.

I have given up on ZFS entirely because of how much of a pig it was.

I wish government organisations would host their own Mastodon servers. Get off Twitter.

Unless they’ve changed it in the last month then it’s 50 GB for zip.

I have five users, max, and barely any files. I don’t know which one Nextcloud AIO uses and I don’t care. There’s no wrong answer for such a small deployment. It uses whatever database Nextcloud felt was sensible as the default. They know more about picking the right tool for their requirements than I do.

If I’m building something for myself, then I care.

What’s so WTF about it? I’m repurposing old hardware and testing out the concept. I’m not shelling out a pile of cash on something that might not work for me.

These are internal drives connected to a desktop PSU wired to a USB interface to connect to the laptop.

Haha, yeah. It does make me wonder whether I should bin the whole TrueNAS approach entirely. It seems like a tremendous faff when I could just have the files mirrored to another disk as a backup.

The hard disks are on a separate power supply. The TrueNAS software is running on an old laptop so it effectively has UPS protection.

Yeah, another vote for Caddy. I’ve run nginx as a reverse proxy before and it wasn’t too bad, but Caddy is even easier. Needs naff-all resources too. My ProxMox VM for it has 256 MB of RAM!

Which logs specifically should I be checking?

zpool doesn’t see any pools to import. The system does see the disks but I’m not sure why the disks aren’t being checked for pools.

I’ll give it a shot. I was asking here in case it was a common thing that everyone else knows about (i.e. “Oh you’re running TrueNAS without a UPS? That’s a non starter, everyone knows that”.