Add NEXT_PUBLIC_ENABLE_NEXT_AUTH to clerk example #6309
Conversation
|
@jonassiewertsen is attempting to deploy a commit to the LobeChat Desktop Team on Vercel. A member of the Team first needs to authorize it. |
dosubot
bot
added
the
size:XS
|
Thank you for raising your pull request and contributing to our Community |
dosubot
bot
added
the
📝 Documentation
| @@ -27,6 +27,7 @@ Go to [Clerk](https://clerk.com?utm_source=lobehub\&utm_medium=docs) to register | |||
| ```shell | |||
| NEXT_PUBLIC_CLERK_PUBLISHABLE_KEY=pk_live_xxxxxxxxxxx | |||
| CLERK_SECRET_KEY=sk_live_xxxxxxxxxxxxxxxxxxxxxx | |||
| NEXT_PUBLIC_ENABLE_NEXT_AUTH=0 | |||
There was a problem hiding this comment.
I think a better way is to add a Callout to show the self-built docker image need this env? as most clerk user doesn't need to add this env
There was a problem hiding this comment.
In that case, it would be nice to clarify, when the env is needed and when it can be ignored.
The release note i provided says:
it's necessary to add NEXT_PUBLIC_ENABLE_NEXT_AUTH if self hosting with docker.
💻 变更类型 | Change Type
🔀 变更说明 | Description of Change
As written in the release notes, it's necessary to add NEXT_PUBLIC_ENABLE_NEXT_AUTH if self hosting with docker.
From the release notes:
https://github.com/lobehub/lobe-chat/releases/tag/v1.52.0
📝 补充信息 | Additional Information