Testing config is tough. I like the idea of treating config as data. Write it in a DB, have APIs and UIs to change it. Write tests for the functionality. Of course there are limits to this, but maybe they are further out than we often think.


New blog post, inspired by a question from

We rarely do stuff like restarting a web server on a new port once a new config event came into the DB. Maybe we should do more of that.

Sign in to participate in the conversation

Hello! is a general-topic instance. We're enthusiastic about Mastodon and aim to run a fast, up-to-date and fun Mastodon instance.