cmer81/ipboard repository overview

⁠Docker Nginx image for Ipboard Invision Community

This container image includes PHP 8.1 and Nginx⁠ for Invision Community

⁠Description

PHP 8.1 available as container is a base platform for building and running various PHP 8.1 applications and frameworks.

ipboard Invision Community is not included in the container, for more information go to the website for download files Invision Community⁠.

⁠Usage

Example with local storage:

$ docker run -d --name ipboard -v "{your-ipboard-installation-files}":/app -e WEB_ALIAS_DOMAIN=mydomain.com cmer81/ipboard:latest

⁠Using an external database

By default this container does not contain the database for Ipboard. You need to use either an existing database or a database container.

The IPboard setup wizard (should appear on first run) allows connecting to an existing MySQL/MariaDB. You can also link a database container, e. g. --link my-mysql:mysql, and then use mysql as the database host on setup. More info is in the docker-compose section.

⁠Persistent data

The Ipboard installation and all data beyond what lives in the database (file uploads, etc) are stored in the unnamed docker volume⁠ volume /app. The docker daemon will store that data within the docker directory /var/lib/docker/volumes/.... That means your data is saved even if the container crashes, is stopped or deleted.

To make your data persistent to upgrading and get access for backups is using named docker volume or mount a host folder. To achieve this you need one volume for your database container and IPboard.

IPboard:

• /app folder where all IPboard data lives

$ docker run -d \
    -p 443:443 -p 80:80 \
    -v ipboard_html:/app \
    cmer81/ipboard:latest

Database:

• /var/lib/mysql MySQL / MariaDB Data

$ docker run -d \
    -v db:/var/lib/mysql \
    mariadb

⁠Build Your custom Usage

docker build --pull -t "ipboard" .

Accessing the application:

$ curl 127.0.0.1

⁠Environment variables

⁠PHP modules

As we build our images containing almost every PHP module and having it activated by default, you might want to deactivate some.

You can specify a comma-separated list of unwanted modules as dynamic env variable PHP_DISMOD, e.g. PHP_DISMOD=ioncube,redis.

⁠PHP.ini variables

You can specify eg. php.memory_limit=256M as dynamic env variable which will set memory_limit = 256M as php setting.

⁠PHP FPM variables

You can specify eg. fpm.pool.pm.max_requests=1000 as dyanmic env variable which will sets pm.max_requests = 1000 as fpm pool setting. The prefix fpm.pool is for pool settings and fpm.global for global master process settings.

⁠Web environment variables

⁠Filesystem layout