[Akkoma] - Force Mangane to use config file rather then db #531
Labels
No Label
administration
Akkoma
Android
Bare metal
bug
Communication
Community
Cryptpad
Discussion
Documentation
duplicate
enhancement
etherpad
Feature request
Feedback
finances
Fixed
forgejo
fun_project
Goal 2024
help wanted
Howto
🤔️ Investigate
ios
jitsi
lacre
Lacre Test
ldap
Lemmy
LibreTranslate
low prio
Lufi
macos
Mail
Merch
monitoring
movim
needs_refine
New Auth
Nextcloud
nice to have
on hold
proposal
question
Ready
refined
Roundcube
searX
spam-protection
Staging Server
Themes
TOR
Urgent!
Website
windows
wontfix
xmpp
Yearly Report
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: Disroot/Disroot-Project#531
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
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?
Since migrating to Akkoma and movimg from soapbox to Mangane, the forntend config file has been saved in database rather then config file. We need to force it to read config file instead since this is what we want to use.
[Akkoma] - Set profiles as public when migration is overto [Akkoma] - Force Mangane to use config file rather then dbhow would you do that?
@muppeth is that possible that you check this?
Check Disroot-Ansible/pleroma#15 especially readme. I think we can close this as I've already opened an issue in changelog so that we deploy and fix this next Tuesday.