stellar-slack has quit [Remote host closed the connection]
stellar-slack has joined #stellar-dev
sv-logger has quit [Remote host closed the connection]
sv-logger has joined #stellar-dev
[7] has quit [Disconnected by services]
TheSeven has joined #stellar-dev
dobson has quit [Quit: Leaving]
dobson has joined #stellar-dev
de_henne has joined #stellar-dev
gst has quit [Remote host closed the connection]
gst has joined #stellar-dev
gst has joined #stellar-dev
de_henne has quit [Ping timeout: 264 seconds]
robinsmidsrod has joined #stellar-dev
<stellar-slack>
<sacarlson> how do I configure stellar_core_commander to control my already running localhost running stellar-core? what params where are set to do this? note my stellar-core runs with sqlite db if that makes any diff
<stellar-slack>
<sacarlson> after reading over the stellar_core_commander code and understanding parts now, I note it looks like localhost can be controled, but I don't understand the @proccess in the code and how changes to that control the stellar-core, so fail to figure it all out.
<stellar-slack>
<fredolafritte> Is 0 a valid sequence number ? Could we assert on it ?
<stellar-slack>
<sacarlson> yes in fact on one setup it did start from 0 instead of 1 and it seemed to run ok
<stellar-slack>
<sacarlson> not sure why some first started stellar-core start at 0 and some at 1
<stellar-slack>
<sacarlson> that was one of the first problems I had with ruby-stellar-base that manualy set the sequence
<stellar-slack>
<sacarlson> sequence 0 had the master account
<stellar-slack>
<sacarlson> Also what I think I might add if no one else hasn't already is to add to stellar_core_commander to also work through the Stellar horizon API interface so that can be tested and used also