Yeah maybe an installing tutorial isn't a bad idea in the end. Let me look into adding that.
On Mon, Nov 30, 2015 at 5:02 PM, Stephen Mallette <[email protected]> wrote: > I'm fine with that - then you'd have something to link to, though at the > risk of a little more work perhaps making "Installing" isn't bad with > curl/unzip commands. we could have the same for Gremlin Console as i > mentioned earlier. > > On Mon, Nov 30, 2015 at 10:28 AM, Dylan Millikin <[email protected] > > > wrote: > > > Durh. No for some reason the "Connecting via console" title threw me off. > > Maybe we can separate the server installation from the console part with > > different titles (content can stay the same) > > > > - run gremlin server > > - connection via console > > - connection view rest > > - etc. > > > > What do you think? > > > > On Mon, Nov 30, 2015 at 2:28 PM, Stephen Mallette <[email protected]> > > wrote: > > > > > Well - we do explain how to "start" gremlin server: > > > > > > http://tinkerpop.apache.org/docs/3.1.0-incubating/#gremlin-server > > > > > > I guess I'd assumed that folks would know where to download it from and > > > then how to unpackage it. Similar assumptions were made for the > console > > > section in the reference docs. If you were just thinking we needed to > be > > > more explicit about that in the reference documentation then I don't > > think > > > it would hurt to add that clarifications there (but I guess i would do > so > > > for both the console and server - maybe an "Installing...." sub-section > > for > > > both). > > > > > > Were you thinking something more than that? > > > > > > > > > > > > On Mon, Nov 30, 2015 at 6:49 AM, Dylan Millikin < > > [email protected]> > > > wrote: > > > > > > > Hey guys, > > > > > > > > I've been writing a php tutorial book and I wanted to link to > > directions > > > on > > > > how to install gremlin-server but realized that there was no such > > > > documentation. > > > > So my first question is.. Should we have this somewhere, and where > > should > > > > we put it? It's own book? > > > > > > > > Second question is, what should it cover? Install + a bit of > > information > > > > regarding documentation? Any other material? > > > > > > > > > >
