Docker Compose with Caddy

The following guides aims at a completly fresh install of Invoice Ninja with the Caddy webserver. The is no migration scenario covered.

⚠️ We especially provide and enforce a TLS setup here, as Caddy comes with automatic HTTPS. If you do not want this or have an already working setup with TLS then this setup might not be the right choice for you.

Table of content

• Guide for Invoice Ninja 4
• Guide for Invoice Ninja 5

Prerequisites

ℹ️ Read the prerequisites section carefully as you need all of these information for a proper setup.

Additionally you need to have proper TLD (Top Level Domain) on a server that is publicly reachable (with a public IP). This is necessary for Caddy to correctly obtain the TLS certificate.
Also check the Caddy automatic https requirements.

⚠️ If you are missing either one of these additional prerequisites, then this setup does not work for you. Please check the setup with nginx instead.

Guide for Invoice Ninja 4

Guide for Invoice Ninja 5

📁 Create a new folder

First we need an empty folder where our docker files for IN 5 will reside.

Command: mkdir ~/invoiceninja5; cd ~/invoiceninja5

💻 Clone this repository

Now we need to clone this repository to get all the files necessary to corretctly configure and run IN 5 with Docker Compose.

Command: git clone https://github.com/invoiceninja/dockerfiles.git .

🔨 Configure your installation

To get the complete overview what things can be configured please check the docker-compose.yml. Each section and value that can or should be configured is commented.

Things you definately should check and change:

• APP_URL: Environmet variable where to reach your installation. This should be your valid TLD domain.
• Ports: Ports are configured for 80 and 443. Make sure they are open and not blocked by some other service.

🚀 Run your installation

After you finished the afore mentioned steps you can now run your installation.

Command: docker-compose up -d

This will run Invoice Ninja 5 with the configuration made. You should now be able to reach your installation at the APP_URL configured.