Skip to content

Commit

Permalink
Fix README, add example of execution
Browse files Browse the repository at this point in the history
  • Loading branch information
thisismydesign committed Mar 11, 2017
1 parent 6e62e7e commit f3fe448
Showing 1 changed file with 5 additions and 2 deletions.
7 changes: 5 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -27,15 +27,18 @@

1, Create a local copy of [config](https://github.com/thisismydesign/poe-sniper/blob/master/config) and [input json](https://github.com/thisismydesign/poe-sniper/blob/master/input/example_input.json) files. Modify values accoding to your needs.

2, Run `ruby -e "require 'poe/sniper'; Poe::Sniper.run('<path to your config file>')"`
2, Run `ruby -e "require 'poe/sniper'; Poe::Sniper.run('< path to your config file >')"`

E.g.
`ruby -e "require 'poe/sniper'; Poe::Sniper.run('C:\poe-sniper\config')"`

3, Stop with CTRL+C

You can also try the alerting functionality with test data without actually connecting to [poe.trade](poe.trade):

1, Create a local copy of [example_socket_data.json](https://github.com/thisismydesign/poe-sniper/blob/master/spec/example_socket_data.json).

2, Run ruby -e "require 'poe/sniper'; Poe::Sniper.offline_debug('<path to your config file>', '<path to your your cope of example socket data>')"
2, Run ruby -e "require 'poe/sniper'; Poe::Sniper.offline_debug('< path to your config file >', '< path to your your cope of example socket data >')"

3, Stop with CTRL+C

Expand Down

0 comments on commit f3fe448

Please sign in to comment.