Re:Pleroma 2.0: a free, federated social networking server b...
by seemslegit on Monday March 09, 2020 @08:14AM
(#22524735)
Sorry, but it's true for the other steps as well with postgres being a particularly pain because it is a networked service that requires administration, security minding etc. The end result is a high-friction onboarding process and the fact that it is technically justifiable is besides the point for people who just want to use the thing not to hack on it.
The "if they can manage to run Pleroma" is not a very helpful approach to actually get more people to run Pleroma.
Re:Pleroma 2.0: a free, federated social networking server b...
by elcritch on Monday March 09, 2020 @10:41AM
(#22525721)
Haven't looked into the Plemora code myself, but it'd likely be feasible to patch it to be sqlite compatible. Unless there's a lot of Postgres specific SQL (triggers? mat views? hyperlog data types?) and the older version of Ecto the SQLite adapter uses. Still it would be fun to something like Plemora run on a RPi4 without needing Postgres. Then again, maybe Postgres would run alright... :-)
Re:Pleroma 2.0: a free, federated social networking server b...
by lainsoykaf on Monday March 09, 2020 @11:35AM
(#22526210)
It's no feasible, we use a lot of postgres specific features. Pleroma with postgres runs fine even on Raspi 2.
Really all we’re talking about here is whether or not the thing that writes the files is in-process or an adjacent process.
If they can manage to run Pleroma, they can manage to run a Postgres beside it. I think the hurdle you are describing is to self-hosting anything in general. Standing up a self-hosted postgres is actually easier/simpler/better supported than some random weird elixir app.