[
https://issues.apache.org/jira/browse/TINKERPOP-1661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16188428#comment-16188428
]
ASF GitHub Bot commented on TINKERPOP-1661:
-------------------------------------------
Github user dkuppitz commented on the issue:
https://github.com/apache/tinkerpop/pull/725
@robertdale FYI: I just fixed the download in `tp32/` and `master/` and
rebased this PR. Rebuilding the images should no longer be an issue.
> Docker-built documentation does not always point locally
> --------------------------------------------------------
>
> Key: TINKERPOP-1661
> URL: https://issues.apache.org/jira/browse/TINKERPOP-1661
> Project: TinkerPop
> Issue Type: Improvement
> Components: build-release
> Affects Versions: 3.2.4
> Reporter: Robert Dale
> Assignee: Daniel Kuppitz
> Priority: Minor
>
> After performing {{docker/build.sh -d}}
> When I pull up the initial URL to look at the docs, it's local -
> http://172.17.0.2/ .
> Anchor links to the same page are also local - http://172.17.0.2/#tutorials .
> However, all links to other pages are remote! Also, you can't just replace
> the server name with the local IP, the URL is slightly different. e.g.
> http://tinkerpop.apache.org/docs/3.3.0-SNAPSHOT/reference
> must be changed to http://172.17.0.2/reference/ in order to view it locally.
> If the reviewer isn't paying attention to the url, s/he might be reviewing
> the wrong content. It would be better if it were all local and/or relative
> paths.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
