the thing is that once the database config sync comes online, the application has started up on the supervision tree and people will get confused when their uploads don’t work
to hard exit and not get overwhelmed by “why uploads no work” support messages they need to blow up the application early
also, the error message gives you the config file format, and does not tell you to put anything in the database, which I think is as clear as it could be
I know the error message/upgrade notes don’t say to put the config item in the db, but I don’t think I’m making too much of a leap when mix pleroma.config migrate_to_db says it moved the upload base url successfully leads me to think “this is a config entry that can be stored in the db and removed from my config file without causing some unforeseen issue”, the job doesn’t try to migrate other parts of my config file so I know they have to stay.
If it makes more sense to say “this config can’t be in the db to keep people from being confused” I’m cool with that, I just want the migration job to not migrate the config and some piece of documentation that says “this has to stay in the config file”, I’d even update the docs myself if I knew where to put the update.