firely/server repository overview

Firely Server is Firely’s FHIR server. It was formerly named ‘Vonk’ and is the successor to our Spark server. Firely Server is the answer to the growing need for a stable server that can be used in a variety of production environments. A public sandbox is available at https://server.fire.ly⁠, which is is free to use and intended for testing and educational purposes only.

The easiest way to run a Firely Server in a Docker container is to run it with a SQLite repository. This is also the default mode.

You need a license to run a Firely Server. You can download an evaluation license file from the fire.ly⁠ website. The license file is by default named firelyserver-license.json Save this file to your working directory. You can provide the license to Firely server in two ways:

• By mounting the file to Firely Server's working directory in the container, as shown below.
• By providing the contents of the file as a single string in an environment variable, see the docs⁠. (This option is available since version 4.7.0.)

Next is to run a container. Open your favorite command line tool and navigate to your working directory and type the command:

In Powershell: $ docker run -d -p 8080:4080 --name firely.server -v ${PWD}/firelyserver-license.json:/app/firelyserver-license.json firely/server

Or when you are using a Command Prompt: $ docker run -d -p 8080:4080 --name firely.server -v %CD%/firelyserver-license.json:/app/firelyserver-license.json firely/server

This will spin up a Firely Server container. It maps the host port 8080 to the container port 4080 with the switch -p 8080:4080. It will give the container the name firely.server with the switch --name firely.server. Furthermore it mounts the license file from the host to the container. At last it will run the container in background mode with the switch -d.

Open a browser and use the address http://localhost:8080/⁠. This will show the landing page of Firely Server.

Further documentation is on the Firely Server documentation pages⁠, and specifically on the Docker deployment pages⁠.