Closed sf52crypto closed 4 years ago
@sf52crypto That is great man! I have been quite busy lately, so I didn't have much chance to look into the application. With my foreseen plans of doing a stepping stop-loss, I do also think Linux compatibility is a must, given the majority servers running on that.
Even though the current state of the application is quite heavy on size, the only problem with sending requests is the server. So putting the server close to the BitMEX servers or just living near them is probably good enough. If you are a market maker, you should have your own proprietary tool built.
@Effanuel Sounds good. I have a server running 24/7 in my home, and setup a container to run Ubuntu and got this to install. Previously, it was running in a Windows 10 minimal VM on my laptop, so it was only available while I was on my laptop :)
While I've gotten this to run, I need to verify that it's actually working. Yesterday I tried to submit orders and it failed for an unknown reason. It MAY have been because of the small order size. BitMEX auto canceled them.
@sf52crypto When you build the application, you can set the LOG_LEVEL = debug
in the .env
file to see error more clearly, if there are any.
Yesterday I tried to submit orders and it failed for an unknown reason. It MAY have been because of the small order size. BitMEX auto canceled them.
Ye, the orders get cancelled if their cost is less than 0.0001 XBT and there are multiple of them.
I've wanted to shift this tool over to run on a linux server so it can be available 24/7 and external. In order to do that, I modified the /api/package.json and /client/package.json to remove the "SET" for NODE_ENV so it would build on Linux. The SET is needed for Windows but causes build to fail on linux.
So I created a new fork, and it's currently running. Putting this issue here as an FYI.