45

Is there a FOSS program where I can inventory my high value items in case there is an insurance claim?

I was thinking of the item, the picture of the item and serial number, maybe the UPC, and then an attachment of the receipt.

I'm guessing some kind of database that integrates file attachments per item.

you are viewing a single comment's thread
view the rest of the comments
[-] nimmo@lem.nimmog.uk 2 points 8 months ago

Could Snipe it work for you? https://docs.linuxserver.io/images/docker-snipe-it/

It looks like an asset management tool. The description copied and pasted from above reads:Snipe-it makes asset management easy. It was built by people solving real-world IT and asset management problems, and a solid UX has always been a top priority. Straightforward design and bulk actions mean getting things done faster

[-] wreckedcarzz@lemmy.world 4 points 8 months ago* (last edited 8 months ago)

Snipe it is hardcore overkill for this need. I started using it a couple weeks ago since I have lots of tech, but it's made for large businesses, or multiple businesses. Technically yeah one can use it, but it's cumbersome and a bit frustrating to get started/figure things out.

I want to add a smart coffee maker? Okay I'll just get the serial and - oh I haven't entered this model before, lets add it. Oh I can't, because I haven't entered anything by Honeywell yet, time to back out and add all the details of the company. Now lets go back and enter that serial again. Now we can add the model details. Let's grab a photo. Oh, the fucking system has a known issue that it limits uploads to 2MB? And adjusting it in docker doesn't work even though it should? Let's stop the container and go into the damn host filesystem to edit the php file that has the solution you will only find on a github discussion from 5 years ago. Now start the container and add an asset and enter the serial and set the model and set the company and upload the picture and why does the warranty length box only take months and I need to mark it as ready for deployment and holy fuck it's taken 45 minutes...

And no, none of this was hyperbole. Once I know these stupid quirks, 5 minutes to grab data and enter, but shit especially the filesize issue, 5 years and no fix? Oh and guess what you'll be searching for online after watchtower pulls an update and you forgot to note that fix in the docker-compose file? Mmmhm, that fix gets overwritten with every update.

[-] shrippen@feddit.de 1 points 8 months ago

What would be a better alternative in your opinion?

[-] lud@lemm.ee 1 points 8 months ago
[-] wreckedcarzz@lemmy.world 1 points 8 months ago

I have briefly looked at homebox, but haven't put it on my server. From the description though, and the couple of pictures, is very likely a better fit.

[-] nimmo@lem.nimmog.uk 1 points 8 months ago

That sounds like a rather unpleasant experience indeed! I've never looked into it in more detail than scrolling through the lsio containers they offer, so thanks for that insight and saving me a headache in case I get around to a similar project I've also been meaning to embark upon

[-] wreckedcarzz@lemmy.world 1 points 8 months ago

I mean, I'm still using it, slowly filling the db... But yeah the first go (or 5) was super frustrating, and the UI could be more intuitive, almost wizard-like for beginners would make a huge difference. But if you want to note the warnings and proceed, it seems like a feature-rich system. Definitely aimed at the actual IT career individuals (and their businesses).

That is the container I'm using, also.

this post was submitted on 24 Feb 2024
45 points (95.9% liked)

Selfhosted

40134 readers
291 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago
MODERATORS