[docs] Add a note about how to get the OTT on self hosted instance
This commit is contained in:
parent
2ed8429df8
commit
a9c6196142
2 changed files with 28 additions and 0 deletions
|
@ -89,6 +89,15 @@ export const sidebar = [
|
|||
},
|
||||
],
|
||||
},
|
||||
{
|
||||
text: "FAQ",
|
||||
items: [
|
||||
{
|
||||
text: "Verification code",
|
||||
link: "/self-hosting/faq/otp",
|
||||
},
|
||||
],
|
||||
},
|
||||
{
|
||||
text: "Troubleshooting",
|
||||
items: [
|
||||
|
|
19
docs/docs/self-hosting/faq/otp.md
Normal file
19
docs/docs/self-hosting/faq/otp.md
Normal file
|
@ -0,0 +1,19 @@
|
|||
---
|
||||
title: Verification code
|
||||
description: Getting the OTP for a self host Ente
|
||||
---
|
||||
|
||||
# Verification code
|
||||
|
||||
The self-hosted Ente by default does not send out emails, so you can pick the
|
||||
verification code by:
|
||||
|
||||
* Getting it from the server logs, or
|
||||
|
||||
* Reading it from the DB (otts table)
|
||||
|
||||
You can also set pre-defined hardcoded OTTs for certain users when running
|
||||
locally by creating a `museum.yaml` and adding the `internal.hardcoded-ott`
|
||||
configuration setting to it. See
|
||||
[local.yaml](https://github.com/ente-io/ente/blob/main/server/configurations/local.yaml)
|
||||
in the server source code for details about how to define this.
|
Loading…
Reference in a new issue