sdaschner

There are some points where we can improve Liberty’s developer experience, especially for beginners and less-experienced developers.

Building Liberty runtime

It’s not straightforward how to create a custom Liberty runtime with Docker (e.g. adding Postgres, custom certificates, etc.). Especially when the liberty-maven-plugin with the default configuration is being used, it’s easy that the features and config in a Dockerfile and what runs with liberty:dev diverges. We should improve that:

• We need the ability to run liberty:dev in Docker, especially Docker images defined by specific Dockerfiles (features, custom config, certs, etc.). Ideally the devs can run "the same thing" that will be contained in the production Docker image locally in dev mode.

• liberty:dev / :start should work consistently with the resulting Docker image. It should be easier to define required features for all runtime stages (local dev, staging, production).

Potential solutions should fulfil the following requirements:

sdaschner

#!/bin/bash
set -euo pipefail

echo "Creating a MonicaHQ contact"

echo -n "First name: "
read firstName

echo -n "Last name: "
read lastName