[ 
https://issues.apache.org/jira/browse/TINKERPOP-2098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16696308#comment-16696308
 ] 

Kelvin R. Lawrence commented on TINKERPOP-2098:
-----------------------------------------------

If it’s working as designed I think a good enhancement would be for start to 
support a yaml file being specified as the script’s help text makes no mention 
of the environment variable. Alternatively I suggest adding mention of the 
environment variables to the help text. 

> gremlin-server.sh start does not seem to work as advertised
> -----------------------------------------------------------
>
>                 Key: TINKERPOP-2098
>                 URL: https://issues.apache.org/jira/browse/TINKERPOP-2098
>             Project: TinkerPop
>          Issue Type: Improvement
>          Components: server
>    Affects Versions: 3.3.4
>            Reporter: Kelvin R. Lawrence
>            Priority: Minor
>
> This may be as simple as a documentation issue but the help text for Gremlin 
> server implies that I should be able to do:
> {code:java}
> gremlin-server.sh start conf/myyaml.yaml{code}
> However when I do that it does not seem to actually be reading my YAML file 
> or if it is it is not reading it fully as I am specifying the WsAndHttp 
> channelizer in the YAML and when the server starts the HTTP endpoint is not 
> available.
>  
> If I start the server in the terminal with
>  
> {code:java}
>  gremlin-server.sh  conf/myyaml.yaml{code}
>  
> all is fine but I want to start it in the background.
>  
> I spoke to [~pluradj] and he had me try using the environment variable to 
> specify the YAML file name and that worked with the *start* keyword.
>  
> Is *gremlin-server.sh start conf/myyaml.yam*l supposed to work?
>  
> If not it would be good to change the help text for gremlin-server.sh which 
> currently reads as follows:
>  
>  
> {code:java}
> Usage: bin/gremlin-server.sh {start|stop|restart|status|console|install 
> <group> <artifact> <version>|<conf file>}{code}
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to