Fancy things first: I have a working folder view on the web side, meaning the database’s structure now has a graphical interface, it’s not just curl commands and massive xml files.(ignore the fact linking doesn’t quite work yet) And I award myself extra points for it not looking like dog shit, though that’s the stand-in content’s credit mostly. Next major project for the GUI side of things is hooking up all the buttons, making a front page, and setting up some OAuth2. The post on security will be quite hefty I assure you. I want to make this system as enterprise friendly as I reasonably can.
As a side note I just realised the python webserver can just serve the compiled angular app’s files. Maybe an out of the box solution is possible.
Secondly I have rewritten what few lines actually comprised the eventbus described at some length in the last real post I made. This was more of a complexity vs laziness situation where it was actually more lazy to do a bunch of work now and avoid it in the long run in the long run. Now the api is only a single python-flask server instead of two. This lowers failover capabilities but it’s far too early for that.
No pictures this time, just short and sweetness