Skip to content
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

Add troubleshooting section for dev search docs #6933

Merged
merged 2 commits into from
Apr 21, 2020

Conversation

stsewd
Copy link
Member

@stsewd stsewd commented Apr 20, 2020

This is very common the first time search ins run

@stsewd stsewd requested a review from a team April 20, 2020 18:01
docs/development/search.rst Outdated Show resolved Hide resolved
@humitos
Copy link
Member

humitos commented Apr 20, 2020

This is very common the first time search ins run

Also, if this always happens, we may want to run this in the --init.

@stsewd
Copy link
Member Author

stsewd commented Apr 21, 2020

Also, if this always happens, we may want to run this in the --init.

I don't think that's a good idea, it will destroy the search index every time we run it with --init

@humitos
Copy link
Member

humitos commented Apr 21, 2020

That's true. Although, the --init argument is receiving another meaning now. We should use it only for init.

Currently, as the workflow is right now, it's already broken. Always, the first time that you setup your development environment, you will have to use the troubleshooting section.

@stsewd stsewd merged commit e5b81e3 into master Apr 21, 2020
@stsewd stsewd deleted the add-troubleshooting-search branch April 21, 2020 17:28
@ericholscher
Copy link
Member

@stsewd @humitos we should add the search index creation to the --init, that should stop this issue from happening.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants