-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Update Comments in .env.example
#11937
Comments
This issue is stale because it has been open 45 days with no activity. |
Looks like this is still needed. I'm in favor of just using the test keys provided by DocSearch docs as a fallback.. any foreseeable issues with using this just for testing? @TylerAPfledderer Happy to assign but also don't want to assume. Pretty well defined task, opening for community in the meantime. |
@wackerow last time I tested this, I saw no issues. We can leave this open to the community for now. |
Still open for someone to take :) |
Point out here that my comment about using So no need to change the filename here! :) |
This issue is stale because it has been open 30 days with no activity. |
Hey @corwintines , would like to work on this task. Could you clarify the remaining tasks for this issue? Any additional context would be appreciated. Thanks! |
This issue is stale because it has been open 30 days with no activity. |
Add comments for the set of env variables for the Algolia search in .env.example. Either clearly define a set of keys available to use for the project when testing the functionality with content in the project or supply the test keys provided by the DocSearch docs.
Secondly, update comment to state that
.env.example
file name needs to be converted to.env.local
when in use, per NextJS requirement.The text was updated successfully, but these errors were encountered: