Add Mangane as optional UI : setup config panel

[lapineige]

Based on this topic, it seems that installing Mangane, an alternative Pleroma and Akkoma frontend, could be automated in a rather simple way and maybe integrated in the config panel.

What do you think about that ?

That topic provide a list of step to install it manually on Yunohost, I believe it would be rather "simple" to transfer it to a config panel…

Anyone willing to try ? 🙂

[bugsysop]

I opened an issue on Mangane repo to know what's the Pleroma support of the projet... Mangane is in fact developped on Akkoma fork of Pleroma

[bugsysop]

From @Cl0v1s

Apparently, and with what I know of Akkoma / Pleroma, as long as most of the API are compatible, there is not particular issue with fixing issue for both Pleroma and Akkoma. Akkoma mostly adds features, exposing them through new API endpoints.

Moreover, Mangane already has a feature detection system allowing us to adapt the experience following what platform is used as a backend.

We are speaking about Akkoma here since we are planning to add akkoma specific features to the project without breaking any existing compatibility.

Source

[bugsysop]

Can we find somewhere documentation about custom panel for Yunohost apps? I talk about YNH admin GUI, not about Pleroma Admin FE...

[lapineige]

I don't remember if they are included in Yunohost documentation, but at least we can have a look at other packages such as Nextcloud and their config panel, to learn how to implement it…

[bugsysop]

Here is the Pleroma official documentation page about alternative frontends https://docs-develop.pleroma.social/backend/administration/CLI_tasks/frontend/

If I understand well, we can just add a value to frontends.available in the Pleroma config file to have Mangane in the list of known frontends.

In this case Mangane can be managed directly in the Admin interface of Pleroma, like all others frontends, without the need to create a Yunohost config panel.

Will try to test this next week

[lapineige]

Yunohost install of Pleroma is not 100% like official configuration setup. Here someone started a tutorial on how to install Mangane on Pleroma for Yunohost : https://forum.yunohost.org/t/installer-mangane-pour-pleroma/22641/ (same link as in my previous post). According to this tutorial, you can't let Pleroma manage frontends in Yunohost because of that particular setup. See : https://github.com/YunoHost-Apps/pleroma_ynh/issues/215

I believe it could be as simple as 1) setup a button in the config panel 2) copy-paste the content of the tutorial as this button action 3) we are done. Removing is a simple rm -r of Mangane folder.

Disclaimer : very naive proposal here :)

Or we need to "fix" Yunohost packaging of Pleroma so it could handle itself on that part.

[bugsysop]

See here for the path to static dir bug in DB

[yalh76]

As there is: https://github.com/YunoHost-Apps/akkoma_ynh , maybe we can close that topic ?

[lapineige]

Mangane is a front-end that works for both Pleroma and Akkoma (even if it's more focus on Akkoma specific features). So I would keep it, it would still be beneficial to Pleroma_ynh users 😃

For my part after learning how to install it for akkoma_ynh, I would be in favor of installing it by default : that's very simple to implement for us (one command line), quite easy to manage for the users (however we have to document it), and the extra storage space is negligible. What do you think ?