-
Notifications
You must be signed in to change notification settings - Fork 239
allow relative urls? #1126
Comments
@tycho01 Did you ever come up with a good solution for building documentation for publishing anywhere but hackage? |
unfortunately, not yet. 😕 |
@tycho01 stack seems to generate docs with relative haddocks, although these don't link to hackage/stackage docs for external dependencies. If your dependency tree is small enough you could consider just uploading the whole thing... |
@expipiplus1 yeah, I did -- I don't super care whether it's including the docs for dependencies or would instead link to their Hackage versions. it's just that even the documentation for my own stuff just breaks as soon as it's moved/served due to the static links based on the location the docs were generated in. |
fwiw there are presently work-arounds. |
I made a similar script here: https://github.com/expipiplus1/vulkan/blob/master/gen-standalone-haddocks.sh It generates documentation with stack, copies what's needed to another directory and them fixes links. Example documentation here: http://expipiplus1.github.io/vulkan/ |
I would like to host my Haddock documentation for others to see without having to publish to Hackage (as I'm not building a library), and figured perhaps I could publish to Github Pages.
However, I found that Haddock generates absolute URLs based on the local location of the documentation folder on the system the docs were generated on.
When moving or deploying the
/doc/
folder anywhere else, such links would break.Is there some command-line option that might allow specifying the desired behavior here?
The text was updated successfully, but these errors were encountered: