Everything you need to install, configure and run APBoard. Explained in full, even for complete beginners.
APBoard is running. Now you should log in, create your first forum structure, review settings and prepare the legal and mail parts before inviting users.
Open your forum URL and go to /login/.
Use the administrator email and password you set during installation.
In Docker, these are APBOARD_FIRST_ADMIN_EMAIL and APBOARD_FIRST_ADMIN_PASSWORD from deploy/.env.
After login, open the admin area from the navigation. Change the admin password if you used a temporary password during setup.
APBoard organizes discussions in two levels. A category is a group. A board is the place where users create topics.
Start with a small structure. Empty forums with too many boards look abandoned.
Community
Introductions
General discussion
Support
Questions
Bug reports
News
Announcements In the admin area, review the forum title, short title, description, default language, default style, registration settings, upload limits and public visibility. These values affect what visitors see and how search engines understand your forum.
If you want a private test forum, disable indexing in the settings before you share the URL. APBoard uses that setting for robots and sitemap behavior.
Public forums usually need legal and privacy information. APBoard provides admin managed legal pages. Open the legal pages section in the admin area and replace placeholders with your real information.
This documentation cannot replace legal advice. If your forum is public, especially in Germany or the European Union, use proper legal text for your situation.
APBoard needs SMTP for registration confirmation, password reset and notifications. Create a normal test user with another email address. If the registration mail arrives, the basic mail path works.
If no email arrives, check the SMTP settings, spam folder and provider rules. Many providers require an app password instead of the normal account password.
Before real users arrive, create your first backup and make sure you know how to restore it.
A useful backup contains the database, config.php or deploy/.env, and public/shared/uploads/.