

Just do Navidrome. It’s better anyway in a multitude of ways.
Just do Navidrome. It’s better anyway in a multitude of ways.
I use OLlama & Open-WebUI, OLlama on my gaming rig and Open-WebUI as a frontend on my server.
It’s been a really powerful combo!
Personally I just use Linkwarden. I’ve been meaning to make a PR to get the auto tagging working on PDFs, maybe someday.
Super simple, I’ve made several integrations for ntfy this way. The result is less pretty but fully workable.
Maintenance is easier than you think. I “maintain” 40+ services by simply automatically updating them. And if that makes one stop working (very rare) I get an alert and fix it when I get time.
I use ansible for that, though you could more easily accomplish much the same with Watchtower.
The best thing you can do to increase your confidence in the data reliability is to invest in backups AND doing at least RAID-1 on a reliable check-summing filesystem like ZFS, which Proxmox supports easily out of the box.
I have ZFS and cloud based backups and I’ve never lost or corrupted data in over 10 years.
And personally, I don’t back up my movies/TV shows. The volume is too high to bother and with ZFS snapshots and reliability, and the high seas being what they are, most everything is (eventually) recoverable.
Edit: or, if you’re a Jellyfin user or think you might become one: https://github.com/Fallenbagel/jellyseerr
Obsidian Live Sync plugin is a great combo of self hosted and offline/local.
Probably asking for something like the Corne keyboard. https://www.boardsource.xyz/products/Corne
Linkwarden and Wallabag are both excellent. Omnivore is up and coming, but might still be difficult to selfhost.
I guess it depends on scale.
FSearch
Recoll
TypeSense
+1 for Gitlab. As the number of developers increases the features of Gitlab will get more and more important. Only OP can say, but if they’re closer to 9 developers than 2, I think it’s a safe bet they’ll need the extra features sooner rather than later.
Its dangerous to send goalposts flying around that fast, be careful or you’ll hurt yourself.
Your response is condescending, arguing from ignorance, and arguing in bad faith. I will reply this time, because once again you’re trying to build an argument on extremely shaky ground and I don’t enjoy people spreading ignorance unchallenged. However I won’t engage any further and feed whatever you think you’re getting from this.
I haven’t suggested that people should use Obsidian over OSS solutions. I was simply pointing out your argument against Obsidian’s architecture was poorly founded.
The data you’re insinuating will be lost is pure FUD. While the format isn’t standard markdown, none of the well implemented solutions are, because as you so rightly pointed out, markdown has little to no support for most of these features.
However, obsidian’s format is well documented and well understood. There are dozens of FOSS plugins and tools for converting or directly importing obsidian data to nearly every other solution. Due to obsidian’s popularity, it’s interoperability this way is often far superior to FOSS solutions’.
Content is your notes. In obsidian this is represented by markdown files in a flat filesystem. This format is already cross platform and doesn’t need to be exported.
Metadata is extracted information from your notes that makes processing the data more efficient. Tags, links, timestamp, keywords, titles, filenames, etc are metadata, stored in the metadata database. When you search for something in obsidian, or view the graph, or list files in a tag etc obsidian only opens the metadata database to process the request. It only opens the file for read/write.
Does this help?
Tell me, are you aware of the distinction between content and metadata?
Also, what do you mean, no official export? The data is already sitting on your filesystem in markdown…?
This isn’t really the case though. Obsidian uses a database for metadata, and therefore can extremely rapidly display, search, and find the correct file to open. It generally only opens a handful of files at a time.
I’ve used obsidian notes repos with hundreds of thousands of notes with no discernable performance impact. Something LogSeq certainly couldn’t do.
The complaint in the post you’ve linked is a) anecdotal and b) about the import process itself getting slow, which makes sense as obsidian is extracting the metadata.
I’ll always champion OSS software over proprietary, but claiming this is a huge failing of the obsidian design is just completely false. A metadata database fronting a flat filesystem architecture is very robust.
Edit: adding link to benchmark. https://www.goedel.io/p/interlude-obsidian-vs-100000
KobaldCPP or LocalAI will probably be the easiest way out of the box that has both image generation and LLMs.
I personally use vllm and HuggingChat, mostly because of vllm’s efficiency and speed increase.
Oh funny I love my upper thumb. Esc/` on one side and Del on the other. So not high traffic, but close when I need them.
Ollama + OpenWebUI also can do this.