Deploy onepw branch somewhere

[dannycoates]

onepw is functional (but slow). Since I wrote this code in haste I didn't make it backward compatible with the old api so we should set up another dev server so client implementations can test with it.

[rfk]

A wild awsbox appears! https://api-accounts-onepw.dev.lcip.org/

Testing it out with @warner's demo client now.

[rfk]

OK, basic functionality seems to be working. Verification emails don't work since we don't have a corresponding instance of the fxa-content-server that speaks the new API. Has the verification API changed, or will it work if I just stand up a copy of the existing fxa-content-server codebase and point it at the new server?

[dannycoates]

Awesome, thanks @rfk! 🍻

Verification hasn't changed but, I'm not sure yet what content-server will need to change to work against this API.

[ckarlof]

Verification hasn't changed but, I'm not sure yet what content-server will need to change to work against this API.

They need to support it. :)

I haven't spoken with anyone from the FxA Web team since I've gotten back (still out of town maybe?) and @warner is still finalizing the API design. Early next week is the soonest we can expect to see FxA Web changes.

[rfk]

ok, I'll see if I can stand up something that will at least let the verification emails go through.

[rfk]

woot, https://accounts-onepw.dev.lcip.org suffices to make the verification emails work. The hosted UI is obviously busted, but this lets you use the demo-client.py script to interact with the https://api-accounts-onepw.dev.lcip.org successfully.

[rfk]

@dannycoates please close if this is sufficient for now

[dannycoates]

solid 👍