-
Notifications
You must be signed in to change notification settings - Fork 67
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Feature Request]: Using Clerk Management Authentication #524
Comments
Thank you for creating this issue! 🎉 We'll look into it as soon as possible. In the meantime, please make sure to provide all the necessary details and context. If you have any questions or additional information, feel free to add them here. Your contributions are highly appreciated! 😊 You can also check our CONTRIBUTING.md for guidelines on contributing to this project. |
Are there any secrets on the client side? As with the current deployment approach we cannot pass any secrets or env variables to the client side. |
Yus there is but we can create an env example file that can go through the deployment the client would have to use their credentials (we can specify in comments or in documentation where to find the necessary credentials). So in their local computer, they can change the values in env.example file but then they need to create an env file and replace this with the content. At the end, they should remove the env file. Do note that documentation for this might be updated as well. |
If we add env variables in .env for deployment then we will have to commit it to GitHub which is not a solution I think. |
Is there any other way since we are serving build of react app via express server |
As far as I know this is the only way to work with clerk through the .env file |
Hello @lolpanda2004! Your issue #524 has been closed. Thank you for your contribution! |
Is there an existing issue for this?
Feature Description
By using clerk authentication, its easier to create customized log in page and sign up page (including form validation) and other options to login in through google, github etc. Thus it will enhance like validation and easy for users to log in via other options rather than manually typing it out.
Use Case
By using clerk authentication, its easier to create customized log in page and sign up page (including form validation) and other options to login in through google, github etc. I would consider this as an alternative to the already existing page.
Benefits
It would be much more easier to save the data in the free trial version of it and secure the users data. Easier for the users to log in via multiple options as well.
Add ScreenShots
No response
Priority
Low
Record
The text was updated successfully, but these errors were encountered: