Everything you need to install, configure and run APBoard. Explained in full, even for complete beginners.
This guide explains how to install, configure, update and operate APBoard v3. It is written for people who may be using Docker, Apache, nginx or MariaDB for the first time.
Use Docker if you have your own server or VPS. Docker brings the correct PHP, Apache and MariaDB setup with it. Use the plain web server installation if you already have working hosting with Apache or nginx, PHP 8.5 and a MySQL compatible database.
APBoard runs in two containers: one app container with PHP 8.5 and Apache, and one MariaDB 10.6 database container.
The app container creates config.php, installs Composer dependencies when needed, prepares asset links and creates the first admin account.
deploy/.env as the central configuration file
APBoard is copied to a normal web space. Apache or nginx serves only the public/ directory.
The browser based setup wizard imports the database, writes config.php and creates the first admin account.
/setup/ for the first installation| Page | What it explains |
|---|---|
| Prerequisites | Server, domain, SSH, database, PHP requirements and basic terms. |
| Docker installation | Install Docker, clone APBoard, configure .env, start containers and verify the forum. |
| Plain web server installation | Install on Apache or nginx with PHP and MariaDB or MySQL, then run the web setup wizard. |
| Configuration | Every setting in .env and config.php, including SMTP, URL and database values. |
| Getting started | First login, categories, boards, legal pages, mail testing and launch checks. |
| Update APBoard | Backups, Docker updates, plain server updates and how automatic migrations work. |
| Troubleshooting | Common installation, routing, database, permission, mail and update problems. |
The APBoard source code is hosted on the project's own Forgejo server.
Docker installations usually clone the Git repository. Plain web server installations should use a release ZIP that already contains vendor/.
Never point your web server at the APBoard root directory. The public web root is always public/.
Files such as config.php, engine/, libs/ and setup/mysql/ must not be reachable in a browser.