Thank you!

I don't want to hear what @BigDogFreedom69 from Asshat, Nebraska has to say

why did we accept a model where his opinion is given the same weight as my best friend's by default?

I want a door i can lock

Is that too much to ask for?

we know how to build doors. We just stopped prioritizing them.

For example, you can just add a valid client id and secret for Github login and simply you adding those means "Login with Github" is now enabled.

Setting grouping is already built but I haven't add the UI for that and I wanted to get an update out with the current state.

What does this unlock? A searchable and intuitive place for the vast majority of the config. Settings can be accessed on the client and on the server.

private settings (I control that flag) are very tightly locked and will never be served to the client. This can be used for server / db stuff.

I added support for text/bool/json/number and file (upload) settings

Settings can be public (client) or private (secret stuff)

The settings are saved in the db. I seed the settings from a JSON file (that you never interact with)

I can add or remove settings and a small boot script syncs your db

#4

Both are valid, but

Always start with the most basic example that I can try.
This stuff should be homepage material for any webdev software.

and then have a single funnel "get started"

From there, it's up to you.

I literally want to see the most basic example upfront.

I have so many questions.

I'd like that very much. Shot me a DM whenever

Have not had the pleasure but, hey 👋

For an admin.

Publish settings / webhooks / notifications / group permissions... all that stuff is managed in the UI (profile) for the "actor"

non-explicit stuff like some form of aggregation like you mentioned can come later