Fork me on GitHub
#boot
<
2019-01-26
>
flyboarder21:01:32

^ 💥 Updates and a Blog post 😉

😁 1
borkdude22:01:36

docker pull bootclj/boot is not working for me

borkdude22:01:26

@flyboarder I figure you haven’t pushed the images yet?

flyboarder22:01:20

@borkdude I pushed so many images, they are still in queue

flyboarder22:01:33

it’s all building off github

borkdude22:01:05

cool. so how does it work? when I start boot in docker, my whole app must run in docker?

flyboarder22:01:22

you can map local folders to your docker container, and this gives everyone a standardized environment for running boot

borkdude22:01:14

that’s cool. I don’t normally develop my app inside docker though. The old way will still be supported right?

flyboarder22:01:29

yes, you can still run boot on your host

flyboarder22:01:03

until graal get’s wider support for windows and macos, the docker containers are the easiest way to try the V4 builds

flyboarder22:01:36

@borkdude yes, version 3 and 4 are on dual development tracks, non-backwards compatible changes will be in V4, currently this only includes the native loader, which you can use via boot-native images

flyboarder22:01:23

version 3 has the same loader however we only compile for java aot, not graal native platform support

flyboarder22:01:51

this keeps v3 current anywhere that v2 can run

flyboarder23:01:21

How does boots version affect the changes?

flyboarder23:01:12

Supported Runtimes for boot-clj