std VS jib

Newcomer here. Could anyone tell if std [0] is a good way to bring more sanity into flake design, esp. in avoiding ivory towery custom approaches? Using devenv.sh is another option, but I liked emphasis on having a common mental picture and focus on SLDC that std provides.

[0] https://std.divnix.com

Agreed on the experience, hard to onboard. I looked at devenv.sh as easier way to get going. Implemented all with Nix, less lock-in. Just found std [0] and that quote looks promising too.

[0] https://std.divnix.com/

std/paisano for large projects.

You need to build Docker images for each app. This is specific to the JHipster application used in this tutorial which uses Jib to build the images. Make sure you are logged into Docker using docker login. Navigate to each app folder (store, invoice, product) and run the following command:

JIB

It is pretty easy to do with https://github.com/GoogleContainerTools/jib.

Save yourself the dockerfile and use jib: https://github.com/GoogleContainerTools/jib/tree/master/jib-maven-plugin

I first learned about Distroless because it was the default option in Google's Jib. Jib is a Maven plugin to create Docker containers without dependency on Docker. Note that the default has changed now.

Optimize your Dockerfile by using a small base Java Image, use either Spring Boot's layers tools or Google Jib to build your docker file, and increase CPU/Memory requests and limits if you can.

In this section, we will setup the automated generation and deployment of a Docker container image. You will need a Docker Hub account and the Jib Gradle Plugin.

If you don't want to hack on your own scripts to package your app into a container, I can recommend the JIB maven plugin. A gradle version is also available.