@benaryorg configuration on databases exist because admin panels and are the bane of my existence

at work we use wordpress, the api keys for stripe get stored into the database. instead of something sane like a config file (which would be different from dev to prod), we gotta use a plugin to check an env var at startup that then changes the config db (and since php, this happens at every request basically)

at work we also use drupal, drupal has configuration file exports, but the only config that counts are the ones in the db. so we need to export, commit that into git, and on every deploy or pull, import again. so often the configurations get out of sync and fighting the sea of yamls to make it work again is painful

all of this because editing text files is bad, *i guess* oh no the normies can't ever learn how to open a .txt and change it! we need clicky clicky menus!! what? it'll make having proper deploys impossible? who cares, it's not like anyone would work on a non-live wordpress site! (/s, i'm so tired of this)