As I'm working on auth related tasks for the httpserver I've found that Tiled has diverged significantly from where bluesky-httpserver and it started. I think there is some benefit to migrating the SQLAlchemy auth database changes back to bluesky-httpserver to reduce differences in auth related tasks.
@danielballan worked on this on Tiled a few years ago:
bluesky/tiled#416
Likely there have been some changes since then.
I think if we 'update' bluesky-httpserver to match Tiled's auth database we can move additional functionality from both into a common auth system for web based application development, which "should" allow us to reuse more code for less overall effort.
I'm keeping this separate from the effort I'm making in creating the common authentication repository to avoid even more scope creep.
As I'm working on auth related tasks for the httpserver I've found that Tiled has diverged significantly from where bluesky-httpserver and it started. I think there is some benefit to migrating the SQLAlchemy auth database changes back to bluesky-httpserver to reduce differences in auth related tasks.
@danielballan worked on this on Tiled a few years ago:
bluesky/tiled#416
Likely there have been some changes since then.
I think if we 'update' bluesky-httpserver to match Tiled's auth database we can move additional functionality from both into a common auth system for web based application development, which "should" allow us to reuse more code for less overall effort.
I'm keeping this separate from the effort I'm making in creating the common authentication repository to avoid even more scope creep.