Beautiful! Great job

Fellow homebox user here. As an aside: I’ve got a storage room with a bunch of shelves and bins. For each bin, I’ve suck labels on them (using a label maker or sharpie + painters tape), and an NFC tag. Each box in Homebox has its own location, and each NFC tag is a direct link to its instance in Homebox.

It’s much easier to categorize larger quantities of things that aren’t as valuable as vintage media. Ie. hygiene products, off-season clothing, etc…

Bookmarked this to try this setup next weekend!

I separate the name from the ID, so the IDs are relative to the specific device only, and the names represent the device and location.

I’ve set the IDs for all my sensors to use a code. The letters identify the type of sensor, and the numbers are sequential when I got them. I also have a label maker and labeled all the devices with their codes.

Example:

AA##

So my first temperature sensor is

TS01

Then the name of the sensor is a little more elaborate, where it includes the type of the sensor, the code, and the location.

{Type} {ID} - {Location}

So my bedroom motion sensor is:

Motion MS02 - Bedroom

Then if I have to rearrange anything, I don’t update the device ID, just the name and how it’s used.

I recently moved and had to rearrange some of the devices. It wasn’t as bad as it could have been as I tried sticking the sensors in the proper rooms (ie all the old bedroom devices stayed in the bedroom). But there were some cases where I did have to rename them & update the integrations.

Linkwarden user here. Can confirm - it’s a great tool to dump links for later. I’ve setup an iOS shortcut that lets me share links directly to linkwarden. Super handy

I was thinking OP could give everyone their own VM to use as a workstation so they could access the files on the server easily, and/or run programs based on their work. When their coworkers leave, OP can easily destroy the VM and the resources would be automatically reallocated (depending on the servers configuration). With a physical device, the storage on that device is only allocated to that device and can’t be shared when it’s not in use

Me, personally? I have multiple VMs for different contexts: my teaching job (super clean, video sharing tools, presentation tools), gaming, media server (has scripts to download stuff off of YouTube), server management (just a regular Debian install), and a fuck around box (I just use it to try new OSs like Fedora, or try breaking OSs like deleting the system32 folder on windows)

I know this isn’t exactly what you’re asking for, but I’d recommend also looking into a VM OS such as proxmox or unraid (I’m running unraid)

They’ll let you create/destroy VM instances you can access remotely. So in theory, you can give everyone their own VM to use and access the files on the server.

However, unraid / proxmox may have performance issues running in a VM on a Mac mini…

She’s a liability to them. She holds so much power over them; and all she has to do is run to the media and give them “the truth” (“the truth” being what everyone suspects anyway. Doesn’t matter if it’s actually true or not)

Looking through the docs n’ stuff, this is what I found:

• Updating Guide. Just basic steps, similar to what I explained above; but with commands to run.
• Backing up and restoring
• 2.0.0 Change Log. Unfortunately they don’t include any notes about how to upgrade

I wasn’t able to find any additional instructions on how to update other than the expected generic steps (docker pull or pip install -r requirements.txt). So my guess at this point is that they have scripts built in to check the version and run upgrade scripts as needed

deleted by creator

I haven’t gone through your specific case, but generally what I do when doing a major update with potentially breaking changes:

• Read the upgrade guides, if they have them. Some devs will put them out if they know their users will encounter issues when upgrading. If they don’t have an upgrade guide, there might be some in the change logs. Going from 1.17.1 to (assuming) 2.x.y, check the change logs at 2.0.0.
• Backup everything. I’d recommend doing this on a regular basis anyway.
• (If you’re running it in a docker container) Setup a second instance, restore the backup, then run the upgrade. You’ll be able to check to see if it breaks at all. If it works, you can just destroy the old one and use the new one
• (if you’re not running it in a container) with the backup, try upgrading. If it breaks, you should be able to uninstall & reinstall the old version, then restore the backup

I hate how this official letter reads like one of his social media posts