Between basically every process being done on paper, and most of the civil servants having no idea what an operating system is, I’m sure this will go great.

As far as I can tell this just fixes some relatively minor issues the contributor was experiencing deploying the hacky self-host stack on his Kubernetes home lab or private server. It doesn’t bring anything new to the table, and I’m not sure that a full on Kubernetes or similar distributed swarm deployment is really what the average self-hoster needs or even wants.

It could just be that Omnivore tries to do too much for it to be feasible to self host. It was also conceptualized with certain third-party backend services in mind which makes it tricky to adapt.

Maybe I’m asking for too much, but I would be looking for a two service stack, one for the app and one database service. The current and forseeable future state of Omnivore is four backend services excluding the database, and like I already pointed out you’re not even getting the full feature set.

From their blog post (linked to by the docs page) about self-hosting:

The following Omnivore features will not be included in this minimal Omnivore setup:
- The web app (we will use the iOS app from the AppStore as our client)
- Search of PDFs
- Saving URLs instead of pages (more on this below)
-Receiving newsletters via email
- Text to speech

Not only that, they use a non-self hosted elasticsearch provider.

Their example docker-compose file in the repo has no less than four containers defined, not including the database server, and you have to build them all yourself, so it’s more of a local dev environment type deployment rather than production.

Here’s their “make self-hosting more practical” Github issue, coming on two years old with no progress: https://github.com/omnivore-app/omnivore/issues/25

All of that was more than enough for me to not even bother to try to deploy my own instance. I manage with Wallabag for now, it’s not the greatest implementation either but at least it can be self-hosted. Omnivore looks slick but the backend just doesn’t keep up.

Looks like a cool app but it’s super unpractical and hacky to self host and you can’t even use a bunch of features when it’s deployed that way.

Wikipedia has already been ruined by a billionaire, namely its founder.

Because they can make more money by walling the garden.

I just use an editor and a local git repo. Write everything in Markdown. Current editor of choice is Pulsar but use what you like. Self hosted repo lets me access the notes from any device as well as keep a history of what I’ve changed.

I got a private instance going a few months ago and I really like it. It’s just a little slow cause it runs on a Pi (my only 24/7 device at the moment). The hostname rewrite feature is cool and I’ll have to check out the archive cache feature.

I also use a public instance at work and it’s way more effective than the bloated corporate search engines. Super handy for engine or language specific searches too.