We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
E.g. http://haddock.stackage.org/lts-2.13/BlastHTTP ➡️ http://haddock.stackage.org/lts-2.13/BlastHTTP-1.0.1/Bio-BlastHTTP.html
Or even! http://haddock.stackage.org/package/BlastHTTP ➡️ latest snapshot and version.
I see this already works for the package link (https://www.stackage.org/lts-2.13/package/BlastHTTP), but the haddocks would be very handy. I've hit the 404 a bunch of times out of wishful thinking.
The text was updated successfully, but these errors were encountered:
This is difficult to do with S3, but stackage.org already has this kind of thing set up:
Sorry, something went wrong.
Popping down as enhancement.
Haha, I have the oldest open issue on stackage-server! 🏆
Closing now since I totally forgot all about it and never missed it. The direct Haddock url is an implementation detail.
No branches or pull requests
E.g. http://haddock.stackage.org/lts-2.13/BlastHTTP ➡️ http://haddock.stackage.org/lts-2.13/BlastHTTP-1.0.1/Bio-BlastHTTP.html
Or even! http://haddock.stackage.org/package/BlastHTTP ➡️ latest snapshot and version.
I see this already works for the package link (https://www.stackage.org/lts-2.13/package/BlastHTTP), but the haddocks would be very handy. I've hit the 404 a bunch of times out of wishful thinking.
The text was updated successfully, but these errors were encountered: