I think I'd like to have the swauth api homed at /swauth/ instead of /auth/ so it doesn't conflict with some other stuff I've got going. And that worked mostly fine using the auth_prefix setting in the proxy-server.conf's [filter:swauth] section, but broke webadmin.
Bit of sed and a reupload squared it for me, but it felt like a hack, and if I want to try and push any fixes upstream I'll have to carry this silly patch :cry: (I'm no css guru, but I wonder have you heard of the bootstrap?)
I thought of two ways that might be better and was wondering if you'd be interested in seeing either one of them.
mv index.html index.html-template and have a swauth-webadmin install command that could read the config, fill in the blanks and upload the newly rendered webadmin resource(s).
pop something into /info with register_swift_info that says the relative url of the swauth api end point and have index.html do an XHR as soon as it loads to fill in some global state?
I think I'd like to have the swauth api homed at
/swauth/
instead of/auth/
so it doesn't conflict with some other stuff I've got going. And that worked mostly fine using theauth_prefix
setting in theproxy-server.conf
's[filter:swauth]
section, but broke webadmin.Bit of sed and a reupload squared it for me, but it felt like a hack, and if I want to try and push any fixes upstream I'll have to carry this silly patch :cry: (I'm no css guru, but I wonder have you heard of the bootstrap?)
I thought of two ways that might be better and was wondering if you'd be interested in seeing either one of them.
mv index.html index.html-template
and have aswauth-webadmin install
command that could read the config, fill in the blanks and upload the newly rendered webadmin resource(s)./info
withregister_swift_info
that says the relative url of the swauth api end point and haveindex.html
do an XHR as soon as it loads to fill in some global state?