You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tinkerpop.apache.org by "Florian Hockmann (JIRA)" <ji...@apache.org> on 2018/11/02 12:46:00 UTC

[jira] [Closed] (TINKERPOP-2086) Publish docs port for docker/build.sh -d

     [ https://issues.apache.org/jira/browse/TINKERPOP-2086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Florian Hockmann closed TINKERPOP-2086.
---------------------------------------
    Resolution: Not A Problem

> 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)