joeldg
Using separate docker container
Hi @joeldg, nice project you created!
I was wondering if you have a vision about separating the app, webserver and db into separate docker containers? We might be able to simplify a few things by then using a a docker-compose file or even create deployment definitions to run this on Kubernetes.
I'm the kind of user that is never going to install all deps locally. I will be running everything from inside docker. But I can image that not everybody is an advanced docker user. What is the target audience of this repo?
If you like I can help with putting components in their own container. I've just forked your project and I'm going to play now!
Cheers
Hey man.. this was really just for people to get a local copy running to follow along. I am working (as I can) on doing some rewrites and will be releasing some different setups.
- A docker you can fire up locally for basic testing
- an AMI on AWS for people who have been having issues
- Some other things which I will publicly discuss later..
- Some changes that will be needed for the ML additions, using Sagemaker or SparklingWater (Spark+h2O)
Another thing, I am probably going to be making a cached exchange ticker service for this where I have a server in the cloud which can be queried for use with Bowhead on most of the major ones, that way you can get up and going on all the exchanges and set up arbitrage right out of the gate without having to sign up on tons of services just to try it out.
Lot and lots happening
-joel
On Wed, Dec 27, 2017 at 10:44 AM, Dino Hensen [email protected] wrote:
Hi @joeldg https://github.com/joeldg, nice project you created!
I was wondering if you have a vision about separating the app, webserver and db into separate docker containers? We might be able to simplify a few things by then using a a docker-compose file or even create deployment definitions to run this on Kubernetes.
I'm the kind of user that is never going to install all deps locally. I will be running everything from inside docker. But I can image that not everybody is an advanced docker user. What is the target audience of this repo?
If you like I can help with putting components in their own container. I've just forked your project and I'm going to play now!
Cheers
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/joeldg/bowhead/issues/68, or mute the thread https://github.com/notifications/unsubscribe-auth/AOT1lQs4DPKxHpsAH_jAINeowquQ6MdKks5tEmXJgaJpZM4RNmIo .
-- Joel De Gan Vice President of Technology
Mobile: (646) 724-0451 Email: [email protected] Skype: joel-dg
2320 Abbot Kinney Blvd, Suite A Venice, CA 90291 www.RxMG.com http://www.rxmg.com/
Hi,
I could help with a multi-service definition to be used with docker-compose if you are interested. I have plenty of experience with dockerizing applications (check my profile).
Having a microservices oriented architecture has many advantages, adding to the mentioned ones:
- It's easier to update component versions without affecting the whole application
- It's easier to setup HA scenarios for the database or web server
- It's possible to deploy the application in a distributed platform like swarm, kubernetes, rancher, etc.
Let me know and I'll start working on a PR ASAP.
