๐ docs: 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
|
๐ @jonassiewertsen 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.
arvinxx
changed the title
arvinxx
changed the title
NEXT_PUBLIC_ENABLE_NEXT_AUTH to clerk example
|
โค๏ธ Great PR @jonassiewertsen โค๏ธ The growth of project is inseparable from user feedback and contribution, thanks for your contribution! If you are interesting with the lobehub developer community, please join our discord and then dm @arvinxx or @canisminor1990. They will invite you to our private developer channel. We are talking about the lobe-chat development or sharing ai newsletter around the world. |
|
๐ This PR is included in version 1.69.5 ๐ The release is available on: Your semantic-release bot ๐ฆ๐ |
๐ป ๅๆด็ฑปๅ | 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