This caught my eye and I started reading over it but my eyes glazed over after a couple of sections of setting up various docker containers in various zfs directory structures and editing toml configuration files and zzzz…
Here’s a hint: for 99.999% of potential users, including 99.9% of motivated, technically savvy users, if I need to know the directory structure of your software, then you already failed.
I appreciate that you went through all the pain and learning and effort to figure out how to set all this up AND went to the trouble to write down a how to guide.
I hope someone comes later and bundles it up into a script I can launch that will prompt me for the various config options and then set it all up for me.
I'd love to be wrong, but I suspect that it is quite a narrow niche of users that a) are willing to run their own identity and auth servers but b) aren't so persnickety about their software that they would be cool with some wizard to set it all up automagically.
Microsoft sold (maybe still sells) Home Server and Small Business Server which were turnkey solutions that included directory services, file & print sharing, and other stuff.
I very much think everyone should a person should have a personal identity server. I think it should be buried enough that the user is managing “friend” objects transparently.
I disagree, seems like a pretty standard structure of one directorz per app and inside that subfolders for configuration, secrets, opaque various data. Not complicated at all really.
Here’s a hint: for 99.999% of potential users, including 99.9% of motivated, technically savvy users, if I need to know the directory structure of your software, then you already failed.
I appreciate that you went through all the pain and learning and effort to figure out how to set all this up AND went to the trouble to write down a how to guide.
I hope someone comes later and bundles it up into a script I can launch that will prompt me for the various config options and then set it all up for me.