Background: I’m in an OTP installation and am trying to install the Mangane frontend. I followed the steps on their page. But now I get the Request failed with status code 500 toast message whenever I go to the Frontend page (See pic). By Frontend page, I mean pleroma/admin/#/settings/frontend
The developer for Mangane asked, “Did you activated in database configuration?” and shared the link below. Now, the guide (link below) says :
It is recommended to backup your config file now. cp config/dev.secret.exs config/dev.secret.exs.orig
Running the above at root gives me the following error message. cp: cannot stat 'config/dev.secret.exs': No such file or directory
Edit your Akkoma config to enable database configuration. config :pleroma, configurable_from_database: true
However, the following is already in my config.exs file.
Correct. That’s what confuses me. The documentation of the FE I’m trying to install is just not done well IMHO.
The FE seems to work but now whenever I go to the Frontend page on Admin FE I get the Request failed with status code 500 posted above. Not to mention all the FEs installed by default are gone - the area is blank now.
@gamerfort I actually moved from Soapbox to Mangane - what with the list of additional features that it has. List below (not my wording). But I guess it’s been quite a struggle since the documentation has been ‘confusing’ and difficult to comprehend esp the location of where to place folders etc.
[CH] Add local and fediverse timeline in thumb menu, move serach icon in top navigation (#13)
[CH] Add search Icon in tabs_bar, remove search from thumbs bar
[CH] Add local et fediverse timeline access in thumb menu
[ADD] Add multiple screen to the onboarding to explain what’s the fediverse is about
I installed it as a new subdomain to give it a try. It is a little nicer than soapbox, for sure. I am going to wait until it has more feature parity with the Pleroma-FE though since I heavily use the newer features added by Akkoma (auto-translate support, custom reaction gifs, as well as showing only replies to me, for example.)
Hopefully when the new follow hashtag feature gets pushed to the OTP release, I’ll be using that a lot as well.