+1
-4
src/oauth_provider.rs
+1
-4
src/oauth_provider.rs
···-// {"error":"second_authentication_factor_required","error_description":"emailOtp authentication factor required (hint: 2***0@p***m)","type":"emailOtp","hint":"2***0@p***m"}"error_description": format!("emailOtp authentication factor required (hint: {})", masked_email),···-"Error during pre-auth check. This happens on the create_session endpoint when trying to decide if the user has access:\n {err}"+"Error during pre-auth check. This happens on the oauth signin endpoint when trying to decide if the user has access:\n {err}"
+5
-1
Cargo.toml
+5
-1
Cargo.toml
···+#lettre = { version = "0.11.18", default-features = false, features = ["pool", "tokio1-rustls", "smtp-transport", "hostname", "builder"] }+#lettre = { version = "0.11", default-features = false, features = ["builder", "webpki-roots", "rustls", "aws-lc-rs", "smtp-transport", "tokio1", "tokio1-rustls"] }+lettre = { version = "0.11", default-features = false, features = ["builder", "webpki-roots", "rustls", "aws-lc-rs", "smtp-transport", "tokio1", "tokio1-rustls"] }+rustls = { version = "0.23", default-features = false, features = ["tls12", "std", "logging", "aws_lc_rs"] }
+79
-15
README.md
+79
-15
README.md
···-Nothing here yet! If you are brave enough to try before full release, let me know and I'll help you set it up.+PDS Gatekeeper has 2 parts to its setup, docker compose file and a reverse proxy (Caddy in this case). I will be+found [here](https://atproto.com/guides/self-hosting), but if yours is different, or you have questions, feel free to+The pds gatekeeper container can be found on docker hub under the name `fatfingers23/pds_gatekeeper`. The container does+need access to the `/pds` root folder to access the same db's as your PDS. The part you need to add would look a bit+like below. You can find a full example of what I use for my pds at [./examples/compose.yml](./examples/compose.yml).+#This gives the container to the access to the PDS folder. Source is the location on your server of that directory+For the reverse proxy I use caddy. This part is what overwrites the endpoints and proxies them to PDS gatekeeper to add+in extra functionality. The main part is below, for a full example see [./examples/Caddyfile](./examples/Caddyfile).+If you use a cloudflare tunnel then your caddyfile would look a bit more like below with your tunnel proxying to+Every environment variable can be set in the `pds.env` and shared between PDS and gatekeeper and the PDS, with the+exception of `PDS_ENV_LOCATION`. This can be set to load the pds.env, by default it checks `/pds/pds.env` and is+recommended to mount the `/pds` folder on the server to `/pds` in the pds gatekeeper container.+`PDS_DATA_DIRECTORY` - Root directory of the PDS. Same as the one found in `pds.env` this is how pds gatekeeper knows+`GATEKEEPER_EMAIL_TEMPLATES_DIRECTORY` - The folder for templates of the emails PDS gatekeeper sends. You can find them+in [./email_templates](./email_templates). You are free to edit them as you please and set this variable to a location+in the pds gateekeper container and it will use them in place of the default ones. Just make sure ot keep the names the+`PDS_BASE_URL` - Base url of the PDS. You most likely want `https://localhost:3000` which is also the default
+29
examples/Caddyfile
+29
examples/Caddyfile
···
+51
examples/compose.yml
+51
examples/compose.yml
···+#This gives the container to the access to the PDS folder. Source is the location on your server of that directory