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.
Discussion
Loading...
I have two packs of Pocket Coffee to assist me on this journey. I would like to thank them in advance for the inevitable heart attack when I chug them all down within 15 seconds1 because I'm a caffeine addicted little goblin.
Lovely, I have login & logout working with the demo user!
The code is a bit messy, will have to do something about that.
The messines stems from having to ferry over the auth session extracted by the middleware to the hypertext components.
There must be a better way to do that...
Demo login deployed.
It doesn't do much, but it did let me explore some useful crates like axum-login. That's a pretty nice crate so far, and made the entire login flow quite easy to implement.
Hrm. After playing with a few mockups, I'm going to restructure the user pages a little. I do not like the /user/ path, for one, and I don't think I want a "user dashboard" to begin with.
There'll be /me/, for the user profile, and /me/services/ as a landing page for, well, services.
Also, at launch, changing one's email address will not be self-service, because that's a bit of a pain to implement. If an email needs changing, until I make that a self-service, one will have to ping me.
With that said, I'll implement email address change soon after, it's an important feature. I'm just narrowing the scope to launch with so I can keep to the schedule.
What to do, what to do...
The longer term plan is to allow people to register as many script & script configurations as they wish, and assign them to whichever hosts they want to.
I think I'll only allow one script configuration (but unlimited hosts) at launch, to make my life a little easier - and the UI less complicated.
1+ more replies (not shown)
@algernon
the color theme looks like an obituary xD