- Launching BuildVu
- Download the WAR file
- Install Docker
- Run Docker
- [Recommended] Enabling HTTPS
- [Optional] Define auth credentials
- [Optional] Mount volume
- Running BuildVu from different language clients
BuildVu has a Docker image available, called idrsolutions/buildvu, to make it easier to get started. Using this Docker image you can start a container that can use BuildVu to perform conversions using a simple REST API.
You can use this image from a cloud platform or server that has Docker installed. See below for instructions for using the Docker image on your own server/infrastructure.
Before getting started, you first want to download the WAR file. This is required for the image to work.
For trial users:
If you haven’t already, sign up for BuildVu trial.
Open the email you recieve when you signed up.
Follow the download link found in the Docker section.
Visit the Customer download page.
Click on ‘Download Latest Customer WAR’.
Submit your username and password.
There are many tutorials detailing how to install docker ready for use. This tutorial to Install Docker will cover everything you need.
docker run -p 80:80 --mount "source=/path/to/war/buildvu-microservice.war,target=/usr/local/tomcat/webapps/ROOT.war,type=bind" idrsolutions/buildvu
For production use, we strongly recommend enabling HTTPS encryption. The container is pre-configured to switch to HTTPS if it finds an SSL certificate, private key and certificate chain in the /opt/ssl/ directory. All you need to do is mount a directory containing files called certificate.crt, private.key and ca_bundle.crt. by adding the following to the above commands:
-p 443:443 --mount "source=/local/path/to/ssl/directory,target=/opt/ssl,type=bind,readonly"
If you wish to set a username and password for the service, you can do so by providing the following additional environment variables:
--env ACCESS_USERNAME=<username> --env ACCESS_PASSWORD=<password>
If you need more than one user, you can provide your own
tomcat-users.xml file and mount it at
If you need to access the converted files from the host machine without using the API you need two additional steps.
First create a folder for the output to be stored in.
mkdir -p /path/to/docroot/output
Second add a mount to the docker command, mounting the new directory to the containers directory.
Now that you have the docker server running you can follow the tutorials for using the API to begin your conversions.
Still need help? Send us your questions.