Introduce Hoogle server command line option #3941
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR introduces support for
stack hoogle --server
option to start local Hoogle server as per #2310.Here's what I did:
Added the corresponding option and its handlingIntroduced a record in the ChangeLog.md file for the changesI haven't found much info on Hoogle in the docs, so I figured no changes are necessaryThe testing was manual by issuing
stack hoogle --server
on the command line and making sure it works as expected.As a side note: besides options mentioned in the issue I added
-p 8080
to start Hoogle on a non-privileged port. This is the default Hoogle behaviour since 5.0.13 (released on 2017-07-30), but I figured that there may be older versions in the wild. As there's no way to pass options directly to Hoogle viastack hoogle
those older versions would try binding to 127.0.0.1:80 and fail without a real way to fix it apart from usingstack exec
to supply the-p
option.