Blallo

@ael-code (cc @boyska) I'd like to clarish my idea: I fundamentally was thinking of your second point > Development environment I'm actually using docker-compose to locally run libreant and make...

Hi, as I wrote in #338, I'd close this issue and concentrate on modernizing this webapp.

I realized that my understanding of docker at the time was crap. I made a `modern-docker` [branch](https://github.com/leophys/libreant/tree/modern-docker) in my fork to use docker-compose. I'd divert this issue to one of...

@boyska , i wasn't thinking about docker images for production, but for testing 😊 > you said: >> We ship a Dockerfile that allows one to build and run a...

Dear @ael-code 😊 At last we meet again (ok, cinematic but not very appropriate 😄). As I stated in the issue #317, I do like docker as a tool to...

>> Blallo: >> +# docker run --privileged --rm -ti libreant-box Because we have to launch the services via >> ```service elasticsearch start``` and ```service libreantd start```. > so what? is...

To clear up my point of view: I don't like Docker as a mean to let people forget how to install and deploy a server. The compose approach that @ael-code...

> Blallo, I think I am missing something. Specifically, I understand well that you want to provide a Dockerfile as a developer tool, not as a deployment tool. That's fine....

Hi @ael-code > I think that the best approach to use containers to run tests is to use still two separate imaages for libreant and Elasticsearch and a simple bash...

I agree. At this point I'd investigate (also as a mean to learn a little bit of travis) if it is possible to restructure the Dockerfile in this PR to...