I'm honestly not sure if there was a moment or a thing. Probably just the unending saga of one Israeli atrocity after another. At some point I just realized it wasn't a complicated situation at all. Palestinians are a colonized people, Israel is a colonizing and occupying force. We're talking about decolonization elsewhere, why not when the region in question is Palestine?
You can use the container names to address containers. Whether this is a randomly generated name (docker run... with no --name flag), the compose working dir and service name, or the compose container_name var.
I also rarely use the container command. docker is sufficient, or docker compose ... while in the working dir of a given compose stack.
The report cites ASPI (a couple defense contractors in a wallabee suit) and RFA (completely made up stories from Langley, VA). I'm gonna need a lot more than Beltway Hearsay here.
Mint on my desktop, decided to try out Tumbleweed on a cheap laptop. KDE wasn't for me / wasn't reliable enough, but I'm happy with Gnome. I haven't needed to use Flatpacks though.
Might try MicroOS on the servers, I like the idea of an immutable distro so less can go wrong during updates, and I run all services as containers anyway.
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.
1, because under the colonial-imperial "international rules based order," might equals right.
2, because the US is a settler colonial project just like Israel. The US leadership doesn't have any problem at all with the treatment of Palestinians. They just want to maintain their "landed aircraft carrier in the middle east" and making some money off it's natural resources in the process is a nice bonus.
The US also pretends it never violated the rights of the multitude of groups it's either nearly eradicated or severely oppressed (Indigenous, Black, and Chinese, just to name a few from the 19th century).
What good man would prefer a country covered with forests and ranged by a few thousand savages to our extensive Republic, studded with cities, towns, and prosperous farms, embellished with all the improvements which art can devise or industry execute, occupied by more than 12,000,000 happy people, and filled with all the blessings of liberty, civilization, and religion?
US President Andrew Jackson, talking about the Indian Removal Act of 1830
According to historian H. W. Brands, Jackson sincerely believed that his population transfer was a "wise and humane policy" that would save the Native Americans from "utter annihilation". Jackson portrayed the removal as a generous act of mercy.[34]
According to Robert M. Keeton, proponents of the bill used biblical narratives to justify the forced resettlement of Native Americans.[35]
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.
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.
So much bougie cope just in the first paragraph.