diff --git a/Dockerfile b/Dockerfile index 538bfa3..6333f9b 100644 --- a/Dockerfile +++ b/Dockerfile @@ -13,9 +13,16 @@ COPY auth /usr/share/nginx/recovery COPY export /usr/share/nginx/export COPY import /usr/share/nginx/import +# prod EXPOSE 8080/tcp EXPOSE 8081/tcp EXPOSE 8082/tcp EXPOSE 8083/tcp +# preprod +EXPOSE 7070/tcp +EXPOSE 7071/tcp +EXPOSE 7072/tcp +EXPOSE 7073/tcp + CMD ["nginx"] diff --git a/README.md b/README.md index 5518ee0..1e586b9 100644 --- a/README.md +++ b/README.md @@ -83,7 +83,7 @@ To build: docker build . -t frames ``` -To run (mapping `[8080, 8081]` to `[18080, 18081]` because they're often busy): +To run (mapping `[8080, 8081, ...]` to `[18080, 18081, ...]` because they're often busy): ``` docker run -p18080:8080 -p18081:8081 -t frames ``` @@ -97,6 +97,9 @@ k3d cluster create frames # Deploy to it kubectl kustomize kustomize | kubectl --context k3d-frames apply -f- + +# Be able to access locally (8080 as an example) +kubectl port-forward svc/frames 8080:8080 ``` To clean things up: diff --git a/auth/index.preprod.html b/auth/index.preprod.html new file mode 100644 index 0000000..24a4cd4 --- /dev/null +++ b/auth/index.preprod.html @@ -0,0 +1,1047 @@ + + + +
+ + +This public key will be sent along with your email inside of a new INIT_USER_EMAIL_RECOVERY
or EMAIL_AUTH
activity
The credential bundle will come from your email. This bundle can then be used for email recovery or auth. We can simulate this locally: see instructions here. A credential bundle is composed of a public key and an encrypted payload. The payload is encrypted to this document's embedded key (stored in local storage and displayed above). The scheme relies on HPKE (RFC 9180).
+ +Once you've injected the credential bundle, the credential is ready to sign. A new RECOVER
activity for example. This iframe doesn't know anything about Turnkey activity however, it's a simple stamper!
Below we display a log of the messages sent / received. The forms above send messages, and the code communicates results by sending events via the postMessage
API.
This public key will be sent along with a private key ID or wallet ID inside of a new EXPORT_PRIVATE_KEY
or EXPORT_WALLET
activity
The export bundle comes from the parent page and is composed of a public key and an encrypted payload. The payload is encrypted to this document's embedded key (stored in local storage and displayed above). The scheme relies on HPKE (RFC 9180).
+ +The export bundle comes from the parent page and is composed of a public key and an encrypted payload. The payload is encrypted to this document's embedded key (stored in local storage and displayed above). The scheme relies on HPKE (RFC 9180).
+ +Below we display a log of the messages sent / received. The forms above send messages, and the code communicates results by sending events via the postMessage
API.