Skip to main content

Download

Either download the version you need directly from priint gitlab - click the build-image job tagged with the version you need, browse its artifacts and get the pdf-renderer-YOUR_VERSION.tar and the how-to-import-this-image.md instructions for loading and using the image.

If you have access to our container registry, registry.priint.com, you can log into it and pull the image directly from docker or podman.

Running the application

You can then run it with a command below. You can use podman instead of docker if this is how you prefer to run your containers. Note you might want to adjust:

  • --name pdf-renderer to --name HOWEVER_YOU_NEED_TO_CALL_YOUR_CONTAINER
  • 8765 to a free port on your host machine that will be used by this new container
  • Europe/Warsaw to a time zone your stack operates in (timedatectl list-timezones lists your options)
  • ./log to whatever local folder you wish to store outcome logs to. Please provide separate folders for each container you start simultaneously.
  • ./config/pdfr-config to a folder with your config, joboptions, licenses etc
  • ./media-assets to a root folder media assets are stored
  • YOUR-VERSION-TAG switch it to your specific, tagged version
docker run --name pdf-renderer \
-p 8765:8880 \
-e SPRING_PROFILES_ACTIVE=pdf-renderer \
-e TZ=Europe/Warsaw \
-v ./log:/log/pdfr \
-v ./config/pdfr-config:/lib/config \
-v ./media-assets:/pubserver/PubServer470/userdata \
registry.priint.com/dev/priint-suite/bpm/pdf-renderer:YOUR-VERSION-TAG

If you are starting a container in Windows, mounting folders in the command above can be done like this:

-v "C:\pubserver\PubServer470\userdata:/pubserver/Pubserver470/userdata"

Adjust rendering-service to use those instances

We describe how to set the rendering-service to work with stand-alone/containerized priint:pdf renderer here.