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