Public | Automated Build

Last pushed: 2 years ago
Short Description
Dockerized InvoicePlane Setup
Full Description

Docker container for a stand-alone InvoicePlane.


This container is based on php7-apache. In php7 the mysql database driver is
deprecated and the mysqli driver shoudl be used.


I recommend to persist at least the

  • /var/www/html/application/config/config.php
  • /var/www/html/application/config/database.php
  • .htaccess

files. So configuration won't be lost over recreation.
(But you can also run without and modify the files in the container.)

The apache server is reachable throw http(80), this is ok for local use.
If you want a remote setup use an reverse proxy with a https connection.
In this case invoiceplane protocol detection won't work, because the local
connection (from the apache to the php interpreter) is unencrypted and the php
variable $_SERVER['https'] is not set. This will cause most browsers to unload
javascript/css. You should edit the config.php.

//$config['protocol'] = (isset($_SERVER['HTTPS']) && $_SERVER['HTTPS'] == 'on' ? 'https://' : 'http://');
$config['protocol'] =  'https://';


You need to link a database container.

Persistet Volumes

To persist files to the host, the image extracts the invoiceplane installation
to /usr/src and copies them to /var/www/html on container run.

  • cp -Ru holdes the files last modified.
  • VOLUME /var/www/html makes all invoiceplane files mappable.
Docker Pull Command
Source Repository