Discussion
Today, I will continue the adventures I were on yesterday, and do some OJF stuff.
As per usual, I'll start a new monster thread.
Today's adventures will take me back to #OnlyJunkFans land. I'll be working on some UI stuff to guide how I shape the backend later.
My hope is that by the end of the day, the deployed version will have a demo login that works.
That leaves only the forced password change as a thing I can't express as a permission. How about I deal with that later?
Holy fuck, getting permissions to be laid out nicely typed in both SQL and Rust was a colossal pain in the ass.
In hindsight, the implementation is straightforward, but figuring out how to get there... oof.
Install bonfire.cafe
Get the full app experience
So, I'm playing with permissions. And one of the things I couldn't figure out last night was the demo account with permissions only.
With the permission set laid out last night, I could express most of it, but not the "can change hosts & whatnot, but they'll have no effect" part.
How about a "services:deploy" permission? That permission is required to activate the configured services.