- User Since
- Jul 1 2018, 5:54 PM (109 w, 6 d)
Mon, Jul 20
Jun 24 2020
Jun 20 2020
LVM snapshots are another, probably more robust, way to do this that I ought to look at eventually...
Apr 28 2020
Jan 19 2020
Jan 11 2020
Dec 12 2019
Dec 11 2019
Dec 10 2019
Dec 9 2019
Dec 8 2019
Dec 7 2019
Dec 5 2019
Nov 25 2019
Nov 18 2019
Nov 16 2019
Nov 11 2019
Sep 24 2019
gist is, you've got a plane with 100 passengers, each assigned a seat. The first passenger to board is drunk and chooses a random seat assignment. Each subsequent passenger to board will choose his or her own seat if it is available, or a random seat if not. What is the probability that the final passenger to board will remain in his or her assigned seat?
Sep 8 2019
Sep 7 2019
Sep 1 2019
Aug 19 2019
Aug 18 2019
My rough plan following this diff is basically:
- Switch up how we're doing page rendering since that's kind of murky current in terms of how we distinguish between 'build a sanitized HTML element' and 'render a specific page'. That can be cleaned up pretty easily and it's probably best to do that now while the codebase is still small
- Build out the UI for the initial user registration flow. I think this will be the same deal as for a generic user registration, just with a 'this user is an admin' flag toggled
- Build out some infrastructure around password management and credential checking. This'll be a "fun" learning adventure for me.
- Build out the ORM piece so we can actually register a user and store their info to the database
This implementation is also wrong atm. Properly, I'll need to use some flask wrapper function for this since __init__ by definition can't actually return anything (the implication being that, short of raising an exception, we can't interrupt the normal course of action and say, "Return page Y instead of page X"). I'll fix this in a subsequent diff.
Redirect to the appropriate registration route
Super basic check to see if at least 1 admin account has been registered yet
So I think that for now we might want to keep the view and route folders separate, where view is more or less "How do we bring together all of the UI components on the page" and route is "What Python gets run when we go to a URL". It looks like you have all of the blueprint routing in view currently.