Web Usage

[jhnferraris]

Any docs for running this in the web?

[askmike]

You mean with a web interface? I'm running it in a cloud box right now (using SSH).

[jhnferraris]

Hello Mike! I mean if I want to run the "web" component of this app locally? I saw there's a web/server.js in the directory.

[askmike]

unfortunately it was never fully implemented, see #156.

It's very easy to add, but could you let me know:

What exactly would you use the webserver for? Just monitoring markets / trading advice is easy, but I imagine you actually want to configure / backtest.

[jhnferraris]

For now I just want to move the logs from the console on markets/trading advice to a simple browser log. If it is easy, maybe you can guide us through it? I think no docs written for this?

[askmike]

So if you very simply just want the same logs in your browser the easiest way would be something like this (works great on linux and os x, not 100% sure about windows):

In one terminal start gekko and pipe output to file

node gekko > log.txt

In another terminal / command prompt:

npm install -g http-server
http-server

Finally, in your browser go to: http://localhost:8080/log.txt. Note that you have to refresh every time you want to see new data.

---

The other way would be something that I tried in #156. It would be a simple plugin that starts a server and pushes new logdata over a websocket (not implemented but very simple).

[jhnferraris]

Hello Mike,

Got the simple web logger to work. Refreshing it every time is a bit of a hassle.

I've read the discussions on #156 but I don't see any walkthrough? Can you take me through on setting up this plugin?

Much appreciated!

[jhnferraris]

Hello Mike,

Got your web plugin to work but I've commented out some items. Can you please take a look at this,

jhnferraris@8513914

and check if the lines that I commented out are okay?

My next step would be to simulate a simple logger in the web browser in real-time. Hope you can guide me through this.

For starters, how do I handle the broadcastAdvice and show it in index.html?

Much appreciated!

[jhnferraris]

Made another commit, I think I mixed up ws and http in one context. I guess they are different, yes? One is for the http server and the other I guess is for the web socket?

jhnferraris@af000eb

I'm testing this out if it will show up the broadcasted advice in the html.

Comments are highly appreciated.

Thanks!

[askmike]

Hey John,

Made another commit, I think I mixed up ws and http in one context. I guess they are different, yes? One is for the http server and the other I guess is for the web socket?

Yes, the http server only serves the files for the frontend: event handling logic, the charting libraries and some html. While the ws context is used to broadcast all events (trade advice and market data) in semi realtime to the browser.

So I played around with the idea a few years ago, but never actually finished the plugin (it was working but functionality was very limited). A few things to note:

• I am pretty sure Gekko changed so much that you cannot get it working without tweaking some stuff..
• these lines at that time trading credentials were handled differently and not exposed directly. If you run the server on any network that you don't fully control and have real trading enabled: please also delete config.trader. Current Gekko does not deep copy the config so you should probably do that before the delete statement.
• broadcastSmallCandle has been renamed to broadcastCandle. It also takes a second argument, a callback function to run when you are done processing (run it after the this.broadcast). If you don't do that Gekko will buffer market data and it will looks like everything froze.

After these changes you should have a server that is able to send data to the browser. However if you look at the index.html, you see that everything is commented out. Probably better to use this version. Note that the data format Gekko uses most likely changed..

[askmike]

If you can't get it working I will try to hook it up ASAP. Unfortunately currently do not have the time to commit this.

[askmike]

I'm assuming that ws is short for "web socket".

yes, sort of. Ws is short for the websocket server. See here

[jhnferraris]

Hey Mike,

It seems that the css url in the index.html file can't be found. http://nvd3.org/src/nv.d3.css.  Is this a public url?

[askmike]

It was 3 years ago.. You can try this one.

[askmike]

@jhnferraris You can use my version, it is on the webserver branch:

https://github.com/askmike/gekko/tree/webserver

After you enable the plugin browse to http://localhost:8080. The result should look like this:

It updates in realtime when new advice and/or trade data comes in.

---

If you have any experience in webdevelopment, feel free to take it over from here and replace the raw logging with charts and/or an nice looking interface.

[jhnferraris]

Hey Mike! Thanks a lot! Saw some stuff that I've missed when I tried experimenting on my end (ie. Sending the this.advice to the websocket instead of broadcasting it).

Can you send me a PR so I can merge your webserver branch to my repo?

[askmike]

Done, I am closing this for now.

For future readers: the webserver branch has been merged into develop (and will soon be merged into stable).

@jhnferraris if you have more questions or issues, feel free to keep commenting here.

[jhnferraris]

Hello Mike,

I've been trying to deploy gekko in Heroku. However, I keep getting a crash state when running in production. Local deployment in heroku works fine though.

2016-06-27T02:52:46.365439+00:00 app[web.1]: 
2016-06-27T02:52:46.365443+00:00 app[web.1]: 
2016-06-27T02:52:46.365441+00:00 app[web.1]: Gekko version: v0.2.3
2016-06-27T02:52:46.365442+00:00 app[web.1]: Nodejs version: v5.11.1
2016-06-27T02:52:47.234284+00:00 heroku[web.1]: State changed from crashed to starting
2016-06-27T02:52:47.228584+00:00 heroku[web.1]: Process exited with status 0
2016-06-27T02:52:49.209522+00:00 heroku[web.1]: Starting process with command `node gekko.js`
2016-06-27T02:52:50.996500+00:00 app[web.1]: 
2016-06-27T02:52:50.996515+00:00 app[web.1]: 
2016-06-27T02:52:51.769011+00:00 heroku[web.1]: State changed from starting to crashed
2016-06-27T02:52:51.753364+00:00 heroku[web.1]: Process exited with status 0

My Procfile config is here:

web: node gekko.js

Am I missing something here? Are there any standing issues on deploying gekko in production?

Thanks!

[jhnferraris]

I did missed something.

Solution when deploying to Heroku:

Remove config.js in .gitignore and push it to heroku master

[listenlight]

I got the following with a similar procfile as @jhnferraris.

2016-09-21T14:42:08.168821+00:00 heroku[web.1]: Error R10 (Boot timeout) -> Web process failed to bind to $PORT within 60 seconds of launch
2016-09-21T14:42:08.168906+00:00 heroku[web.1]: Stopping process with SIGKILL
2016-09-21T14:42:08.391899+00:00 heroku[web.1]: Process exited with status 137
2016-09-21T14:42:08.420465+00:00 heroku[web.1]: State changed from starting to crashed

[askmike]

@jhnferraris @tidelake The current stable Gekko requires node 6 or higher!

[listenlight]

@askmike My node version is 6.6 iirc.

[listenlight]

I changed to my desired config file and pushed to heroku. The bot only runs for a minute before I get that message. I really appreciate your help.

[albertolive]

You have to change from web to worker, adding a file named Procfile in your root folder and adding this line of code:

worker: node gekko

Then, you have to got to Resources of your heroku project and activate it and deactivate web.

[askmike]

note that I am working on a web UI for gekko, details can be found here: #489.

[askmike]

You need to replace example.com with your own domain, if you don't have one you cannot use SSL (since it secures domains).

…

On Wed, Oct 11, 2017 at 7:47 PM, metin02oktay ***@***.***> wrote: Hello there. when I installed the gekko bot I compared it with an error like this: ***@***.***:~# certbot certonly --standalone -d example.com -d gekko.example.comSaving debug log to /var/log/letsencrypt/letsencrypt.log Obtaining a new certificate Performing the following challenges: tls-sni-01 challenge for example.com tls-sni-01 challenge for gekko.example.com Waiting for verification... Cleaning up challenges Failed authorization procedure. example.com (tls-sni-01): urn:acme:error:unauthorized :: The client lacks sufficient authorization :: Incorrect validation certificate for tls-sni-01 challenge. Requested 0bc5b2042f3a165890141f639398042c.9742e28ceba767d599a712dbc3698f7d.acme.invalid from [2606:2800:220:1:248:1893:25c8:1946]:443. Received 2 certificate(s), first certificate had names "example.com, example.edu, example.net, example.org, www.example.com, www.example.edu, www.example.net, www.example.org", gekko.example.com (tls-sni-01): urn:acme:error:connection :: The server could not connect to the client to verify the domain :: DNS problem: NXDOMAIN looking up A for gekko.example.com IMPORTANT NOTES: - The following errors were reported by the server: Domain: example.com Type: unauthorized Detail: Incorrect validation certificate for tls-sni-01 challenge. Requested 0bc5b2042f3a165890141f639398042c.9742e28ceba767d599a712dbc3698f 7d.acme.invalid from [2606:2800:220:1:248:1893:25c8:1946]:443. Received 2 certificate(s), first certificate had names "example.com, example.edu, example.net, example.org, www.example.com, www.example.edu, www.example.net, www.example.org" To fix these errors, please make sure that your domain name was entered correctly and the DNS A/AAAA record(s) for that domain contain(s) the right IP address. - The following errors were reported by the server: Domain: gekko.example.com Type: connection Detail: DNS problem: NXDOMAIN looking up A for gekko.example.com To fix these errors, please make sure that your domain name was entered correctly and the DNS A/AAAA record(s) for that domain contain(s) the right IP address. Additionally, please check that your computer has a publicly routable IP address and that no firewalls are preventing the server from communicating with the client. If you're using the webroot plugin, you should also verify that you are serving files from the webroot path you provided. ***@***.***:~# please help me :( — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#338 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AA7MD-aSeU3xwHDSZLkqDdc2m2HJR23mks5srLjxgaJpZM4I8h8y> .

-- PGP key at keybase.io/mikevanrossum <https://keybase.io/mikevanrossum/key.asc>