Set Mangane config from role #15

Merged
meaz merged 7 commits from logo into main 2023-11-28 21:16:19 +01:00
Owner

I'm deploying to extra static folder as stated here https://docs.akkoma.dev/stable/configuration/static_dir/ instead of instance dir.
I've also updated default logos.
I've also added logo for PWA as explained here https://github.com/BDX-town/Mangane/blob/master/docs/customization.md

But I still have the issue that the main logo is not working. The only way is to go to https://myinstance.test/soapbox/config and manually editing the json file there.

I'm deploying to extra static folder as stated here https://docs.akkoma.dev/stable/configuration/static_dir/ instead of instance dir. I've also updated default logos. I've also added logo for PWA as explained here https://github.com/BDX-town/Mangane/blob/master/docs/customization.md But I still have the issue that the main logo is not working. The only way is to go to https://myinstance.test/soapbox/config and manually editing the json file there.
meaz added 3 commits 2023-11-25 17:22:07 +01:00
Author
Owner

when I switch to pleroma-fe I see the logo so I guess the issue is with mangane

when I switch to pleroma-fe I see the logo so I guess the issue is with mangane
meaz added 4 commits 2023-11-25 23:37:31 +01:00
meaz changed title from WIP: logo issue to logo issue 2023-11-25 23:37:44 +01:00
Author
Owner

Problem fixed! We can now set vars for mangane config.

I've also updated readme.

This could be used in prof I think, if you check readme muppeth I explain how to remove those mangane config vars from DB.

The only problem with this, is the fact that if a config is changed from website.org/soapbox/config , then we can not use the role anymore to update/change config. We need first to run that pleroma_ctl config delete command again.

Could we perhaps prevent access to soapbox/config from nginx @muppeth ? Like this we don't forget about this!

Problem fixed! We can now set vars for mangane config. I've also updated readme. This could be used in prof I think, if you check readme muppeth I explain how to remove those mangane config vars from DB. The only problem with this, is the fact that if a config is changed from website.org/soapbox/config , then we can not use the role anymore to update/change config. We need first to run that `pleroma_ctl config delete` command again. Could we perhaps prevent access to soapbox/config from nginx @muppeth ? Like this we don't forget about this!
meaz changed title from logo issue to Set Mangane config from role 2023-11-25 23:42:33 +01:00
muppeth approved these changes 2023-11-28 21:16:10 +01:00
meaz merged commit a008c07a03 into main 2023-11-28 21:16:19 +01:00
meaz deleted branch logo 2023-11-28 21:16:20 +01:00
Sign in to join this conversation.
No reviewers
No Label
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: Disroot-Ansible/pleroma#15
No description provided.