Docker image - #3

[vincenzobaz]

I started to hack around in your sbt config to create a dockerfile when I realized you are already using sbt-native-packager.
The plugins allows to build a docker image with minimal config.

This PR adds simple configuration to build.sbt.
To create the docker image just run sbt docker:publishLocal.
A new docker image image will be created which you can then simply run mapping a port on your host to port 8080, e.g -p 9999:8080.

Let me know if this what you had in mind for issue #3 or if you want a Dockerfile built from scratch.

[tg44]

Hy!

Thanks the contribution!
I would go closer to sth like this: https://github.com/TeamWanari/tutelar/blob/master/Dockerfile
Where the DockerFile can build an "optimal" deploy container.

[vincenzobaz]

Hello!
You're welcome :)

I created something similar to your link.

Please note that my previous PR used the native packager to create a native executable while the link you mention creates java executables, so things are a bit different

[tg44]

Some smaller things:

In general the sbt-assembly is not a good choice over the native-packager, bcs assembly is repacking all the dependencies. If you have any cryptography in your code, you probably use libs whose use apis whose need signed jar-s (for ex. bouncycastle), and when you repack, you loose the signs, and even better you got runtime exceptions at appstart... (We have no security here so its ok for this project.)
Ofc. if you want to distribute the app to end-users (like a desktop app) assembly is usually better. Users like the single file solutions.

For these reasons our general use-case is to build with native-packager and move the files to a "small" container.

One more thing: .dockerignore can be a gamechanger :) It's irrelevant here also, but a good-to-know thingy!