CocaineShrimp

Beautiful! Great job

IMO, Lenovo. Have had Lenovos in the past, no issues. I know someone who had an ASUS and the hinge broke. Also, don’t go through Staples - their warranty is garbage.

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…

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’m not in a country with the age verification thing, but has it been turned on for Lemmy servers?

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

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 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

Vim ftw!