client can connect to both legacy and django servers
This works now but requires juggling env vars. It would be better and more future proof to just support both.
Also, the status quo is not production ready because the distinction between legacy and django is https versus http...
-
Fixes #2896 (closed) -
Fixes #2895 (closed) -
Fixes #2894 (closed)later-
what about command line tools? -
remove WEBPLOM variable -
defer all this -
CI updates?
-
-
Fixes #2899 (closed). -
remove --webplomoption from client -
autodetects instead -
client split the validate and login into two buttons. -
"login" should do all auth so that we can (later) move get_spec() to auth'd only
-
-
ensure the SSL handling (popup dialogs etc) still work -
but are hopefully a bit more maintainable
-
-
split API versions legacy vs new -
logout button Issue #2905 (closed)later
Edited by Colin Macdonald