Split out tileo specifics from docker-dronedb

splashblot / dronedb

Location Intelligence & Data Visualization tool

http://carto.com

BSD 3-Clause "New" or "Revised" License

0 stars 0 forks source link

Split out tileo specifics from docker-dronedb #23

Open jjmata opened 7 years ago

jjmata commented 7 years ago

In order to alleviate the long build times, and to better prepare for the microservices cleanup, take everything that has to do with the dronedb app (leave the Node.js apps alone for now) out into a new repo/Dockerfile.

Ideas:

[ ] Call it docker-tileo
[ ] Rename docker-dronedb to docker-dronedb-base in the future
[ ] Add back crankshaft that broke [here]()
[ ] Add dataservices-api, see here
[ ] Configure DO with some sample, relevant, files.

jjmata commented 7 years ago

/cc @apercas in case he has any other thoughts

jjmata commented 7 years ago

I can also better explain what to me is "Tileo" vs "DroneDB" over a beer (or two ...) :trollface:

apercas commented 7 years ago

Rodrigo and Rodolfo.

But right now my setup is working somehow quick. (After a rvm install && bundle install every time I docker-compose down)

jjmata commented 7 years ago

R & R ... love it!

This is not urgent at all, but it is killing me to have builds that take so long and a Docker image that is upwards of 4GB. 😢

Let's see what we learn tomorrow when we talk to @juanignaciosl about Carto Gears.

apercas commented 6 years ago

We reduced the building time from over 35' to around 18' once the cache is abled and we just update the codebase: E.g.: https://github.com/splashblot/docker-dronedb/commit/6c2b3e9f646b2a39f698a8505410be4e34de5ede