poloniex | Sample poloniex client in go | REST library

The problem is in your "we don't have enough money" path. In that case, the amount you can buy does not depend on the amount that was offered.

I think this does what you want.

The problem was that i called my file worker.exs instead of worker.ex sorry for the misunderstanding in the question where i did put worker.ex

For this situation two options come to mind:

1. You can try setting up client certificates from here https://code.kx.com/q/kb/ssl/#tls-client-mode

2. You can try setting the variable SSL_VERIFY_SERVER to NO before launching your q session by doing export SSL_VERIFY_SERVER=NO. To view your current TLS settings which contains this, use -26!() in your q process to display the settings.

It's probably better to do 1) and set up the certificates if possible. This just means that you check the SSL certificate for HTTPS connections and ensures you are sending the request to your intended location.

The above link goes into more detail about SSL/TSL knowledge which might prove useful for you.

Create a prepared request; you can add headers to that after the body has been created:

I don't know the two APIs you are accessing, so I can't really judge whether your code from poloniex.js or cctx.js is good - I assume you can tell through console.logs, etc, that you are getting the API data you require from each separately.

But I can see some logic problems in your scheduler.js file:

1. In getAllTickers, your .forEach loop overwrites res every iteration, so only the last result will be visible.
2. Since it's an async function, getAllTickers returns a promise. You'll need to use .then or something similar on what it returns.
3. The console.log and return in runScheduler complete before the setInterval has a chance to execute, even once, so no data from there is available.

I think the following setup may be what you want:

You could try to use getattr():

You can fetch the latest rows first then group the collection later.

You don't need the Express code because in this case the server you want to talk to is on the cryptocompare server -- not a local server. This is captured in your code when you initialize the io object in the HTML file.

Of course, you could still use Node to talk to the cryptocompare websockets API if you're more comfortable with Node. But then you wouldn't need the in-browser JavaScript. Either way, what you need is to create some kind of client in any runtime that speaks websockets and can talk to the cryptocompare websockets API.

With regard to the code being skipped over -- you're right! It is. socket.io is an event driven WebSockets framework. This means that clients register their interest in certain kinds of events/messages, and when those are triggered special functions known as callbacks are called.

If it helps, you can think of those events like channels in a chat room -- if you're not in the right room, you won't see the messages for that room. So you'll need to know what messages you should be listening for, register your interest in those, and register callback functions for each one.

Thankfully cryptocompare has provided client code examples that should help you get an idea for the kinds of messages you should be listening for. See here