Hey everyone,

I'm looking for a system that:

  • I can self host
  • Is slim, because I don't have beefy hardware (Intel J5040, 32GB RAM, shared by all VMs/containers)
  • can be used to create an inventory of all the tech/hardware that I have in my house (not exclusively IT, I also wasn't to track things like warranty for my chainsaws and the like)
  • does take at least the device make/model, serial number (for insurance cases) and warranty dates
  • is not some kind of enterprise-how-many-items-of-this-article-do-i-have-in-stock-things, because that seems to be the only thing I seem to be able to find, and they neither match my use case nor do they seem to be lightweight enough.

... and honestly, I don't even know where to start looking. Do you guys have any recommendations?

Of course, I could just use a spreadsheet, but where's the fun in that?

EDIT: Thank you all so much for the engaged discussion and all the suggestions, you're the best!

you are viewing a single comment's thread
view the rest of the comments
[–] 7 points 1 year ago (5 children)

This might be an unpopular opinion/solution but even for two small size sister companies we are doing inventory in a version controlled markdown file 🫣

  • source
  • hideshow 10 child comments
  • [–] 3 points 1 year ago

    Honestly, a spreadsheet would be fine for this? I'm not super familiar with what an inventory management system does tho, so maybe it does things beyond what a spreadsheet can do.

  • source
  • parent
  • [–] [S] 3 points 1 year ago (2 children)

    Not at all, I like .md, and I'm familiar with Git. A spreadsheet is not something that I would throw into Git, but an .md...

  • source
  • parent
  • hideshow 4 child comments
  • [–] 4 points 1 year ago (1 child)

    I use markdown too, except I keep the markdown file in a self-hosted wiki (wiki.js)

    It's versioned and accepts git as a backend

  • source
  • parent
  • hideshow 2 child comments
  • [–] 2 points 1 year ago

    That is the reason Markdown and Git are used for a lot shenanigans these days. Knowledge bases, awesome-lists, documentations. You name it.

    If you got the right tools (sphinx, typora, mkdocs, …obsidian) you got a powerful toolchain.

  • source
  • parent
  • [–] 2 points 1 year ago (1 child)

    Simplest possible solution, Occam's Inventory 😄

    I use markdown extensively, but I'm honestly not fond of its tables function (which I assume you use for this purpose?). It works, but it's a bit static in my experience. Do you run up against the same, or is it actually an advantage in your use case?

  • source
  • parent
  • hideshow 2 child comments
  • [–] 1 point 1 year ago* (1 child)

    We’re using headings for different types of inventory (hardware/office items/…) and then a block of subheading, bulletpoint combination (serialnumber, date of acquisition, whereabouts,…) for each item and associated item.

    The toc is generated automatically and helps browsing through.

  • source
  • parent
  • hideshow 2 child comments