coremedia/webswing repository overview

Based on openjdk⁠, this image provides the infrastructure to start a swing application using a browser. The application will be started remotely in the docker container using webswing⁠.

⁠Specification

⁠Layout

/coremedia
    `- webswing
         |- webswing.sh
         |- webswing.config
         |- user.properties
         `- scripts

Working Directory: /coremedia/webswing

User: coremedia

Port: 8080

⁠Add your application

You should add your application below /coremedia using the --chown=coremedia:coremedia directive.

If you need to run extra initialization scripts, you can place them below /coremedia/webswing/scripts with the extension .sh. Any script found there will be picked up and executed by the webswing.sh prior to launching webswing.

⁠Example Dockerfile for the CoreMedia Sitemanager

FROM coremedia/webswing:latest

# the app retrieved by maven
COPY --chown=coremedia:coremedia target/sitemanager /coremedia/sitemanager
# local configuration overrides
COPY --chown=coremedia:coremedia src/docker/sitemanager /coremedia/sitemanager
# webswing configuration file
COPY --chown=coremedia:coremedia src/docker/webswing /coremedia/webswing

For the syntax of the webswing configuration file see Webswing Documentation⁠.

⁠Changelog

⁠1.0.6

• inital public release

⁠License

As with all Docker images, this image also contain other software which may be under other licenses (such as Bash, coreutils, etc from the base distribution, along with any direct or indirect dependencies of the primary software being contained).

• webswing 2.5.5⁠ - Apache License 2.0 (versions after 2.5.10, will be licensed under AGPL and therefore require an extra license aggreement with Webswing)

As for any pre-built image usage, it is the image user's responsibility to ensure that any use of this image complies with any relevant licenses for all software contained within.