savignano/license3j-server repository overview

⁠license3j-server Docker Image

Container image for the License Server application based on license3j project⁠.

Currently designed to work with FastSpring requests only.

⁠Quick start

docker run --rm -p 8090:8090 \
  -e FASTSPRING_FULFILLMENT_USERNAME=fastspring \
  -e FASTSPRING_FULFILLMENT_PASSWORD=changeme \
  -e FASTSPRING_FULFILLMENT_PRIVATEKEY=fastspring_hashkey \
  -e FASTSPRING_WEBHOOK_SECRET=fastspring_hmac \
  -v /etc/license3j-server/secrets/license3j-signkey.txt:/run/secrets/license3j-signkey.txt:ro \
  savignano/license3j-server:latest

Health endpoint:

http://localhost:8090/health

⁠Config volume merge behavior

Image defaults from docker/context/license3j-server/config/ are baked into /opt/license3j-server/config-defaults in the container.

At startup, missing files are copied into /opt/license3j-server/config:

cp -an /opt/license3j-server/config-defaults/. /opt/license3j-server/config/

So you can mount a config directory and keep your overrides while still getting new default files:

docker run --rm -p 8090:8090 \
  -v /etc/license3j-server/config:/opt/license3j-server/config \
  savignano/license3j-server:latest

⁠Environment variables

⁠Webhook event handlers

Which webhook events trigger an email is configured in application.yml under licenseserver.webhook.event-handlers. Each handler has:

Default configuration handles two events:

• subscription.activated — sends a welcome email (template: welcome-email.vm)
• subscription.charge.completed — sends a renewal email with the license key (template: charge-completed-email.vm)

All other webhook events are logged and skipped.

⁠Custom configuration

To customize event handlers (add/remove webhook events), mount a custom application.yml next to the JAR:

docker run ... \
  -v /path/to/my-application.yml:/opt/license3j-server/app/application.yml:ro \
  savignano/license3j-server:latest

Your file only needs to contain the properties you want to override — everything else falls back to defaults.

licenseserver:
  webhook:
    event-handlers:
      - event-type: subscription.activated
        subject-template: "Welcome to $!{data.display}"
        template-name: welcome-email
        template-file: ${WELCOME_TEMPLATE_FILE:}
        recipient-path: account.contact.email
      - event-type: subscription.charge.completed
        subject-template: "Your $!{data.subscription.display} license renewal"
        template-name: charge-completed-email
        template-file: ${CHARGE_COMPLETED_TEMPLATE_FILE:}
        recipient-path: account.contact.email

⁠Velocity template variables

Both subject-template and the body template (.vm file) are rendered with Apache Velocity⁠. The following variables are available:

Common $data paths (exact fields depend on event type):

Use $!data.field (with !) to render an empty string instead of literal $data.field when the value is null.