[
https://issues.apache.org/jira/browse/TINKERPOP-2086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16673019#comment-16673019
]
Florian Hockmann commented on TINKERPOP-2086:
---------------------------------------------
Yes, but when you're using Docker to generate the docs, then you can only
access port 80 from another container.
With publishing the port, I only meant via docker here to make it also
available on the host. We just need to add something like {{-p 8080:80}} to the
{{docker run}} command for that.
I just realized that the build already uses an environment variable
{{TINKERPOP_DOCKER_OPTS}} that allows to configure this. So, if we don't want
to publish the port by default, then we could also just add an example to the
dev docs where this environment variable is used to publish the port.
> Publish docs port for docker/build.sh -d
> ----------------------------------------
>
> Key: TINKERPOP-2086
> URL: https://issues.apache.org/jira/browse/TINKERPOP-2086
> Project: TinkerPop
> Issue Type: Improvement
> Components: build-release
> Affects Versions: 3.2.10
> Reporter: Florian Hockmann
> Priority: Minor
>
> The easiest way to generate our docs is by using Docker via
> {{./docker/build.sh -d}} which generates the docs. However, to actually
> verify that changes to the docs look as expected, one has to manually inspect
> the generated docs.
> We could simply publish port 80 (maybe to another port like 8080) to make the
> docs accessible on the host for manual inspection.
> A workaround is currently to start another container that exposes the port
> and relays to the TinkerPop container with socat:
> {code}
> docker run -p 8080:80 --link [tinkerpop_container]:target alpine/socat
> tcp-listen:80,fork,reuseaddr tcp-connect:target:80{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
