Set Mangane config from role #15
Loading…
Reference in New Issue
No description provided.
Delete Branch "logo"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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.
when I switch to pleroma-fe I see the logo so I guess the issue is with mangane
WIP: logo issueto logo issueProblem 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!
logo issueto Set Mangane config from role