BookStack Installation

We see installation not as 'just installing software once', but as a project: architecture & sizing consulting, choice of installation method (packages, Git/Composer, Docker, possibly Kubernetes), database setup, web server/reverse proxy with TLS, basic hardening, backup/monitoring concept and documentation. Optionally, we handle basic configuration (structure, roles, email) and support testing & go-live.

As soon as you want to keep sensitive or internal documentation (IT runbooks, process manuals, QM, project docs) structured, searchable and under your own control, self-hosting is worthwhile. Data protection, integration needs and compliance are decisive – less so the number of employees. In the initial consultation, we clarify whether your own instance or a SaaS alternative is a better fit.

BookStack requires a web server (Apache or Nginx), PHP (currently ≥ 8.1) with some standard extensions and a MySQL or MariaDB database. Installation typically takes place on a Linux server (e.g. Ubuntu/Debian) with shell access and the ability to run PHP via CLI. We plan the exact size (CPU/RAM/storage) together with you.

We work according to 'Bring Your Own Infrastructure': installation in your data center, with your hoster or in your cloud (e.g. Hetzner, AWS, Azure, GCP) is standard. Alternatively, we offer managed hosting on infrastructure maintained by us. Which variant fits depends on compliance, existing IT and desired service scope.

In practice, we rely on Linux distributions like Ubuntu/Debian with Nginx or Apache, PHP-FPM and MariaDB/MySQL, as described in official installation and community guides. Depending on the customer environment, we integrate BookStack into existing monitoring, backup and logging landscapes.

Yes. In addition to classic installation via Git/Composer or package stack, we support containerized setups with Docker or Docker Compose; for larger or highly integrated environments, Kubernetes can be useful. We check with you whether container operation fits your standards (CI/CD, security, operations team) and handle the implementation.

Yes. You can choose: project service (we install, you operate), Managed Operations (operation on your infrastructure) or Managed Hosting (operation on infrastructure provided by WZ-IT). Services range from monitoring, updates, security fixes to SLAs, 24/7 monitoring and telephone support – depending on the service level chosen.

Yes, BookStack can be operated GDPR-compliant – hosting location, access concepts, encryption, logging and deletion/retention rules are relevant. Since BookStack is self-hosted, you retain full control over infrastructure, access and data flows. WZ-IT supports the design of a setup that fits your regulatory requirements.

Typical measures include: TLS via reverse proxy, hardening of the Linux system, correct file permissions, separation of app and DB access, secure configuration of upload paths and a backup/restore concept for database and files. If needed, we add VPN/ZTNA access, logging integration (SIEM) and coordinated role/permission concepts.

BookStack can use LDAP, SAML 2.0 and OpenID Connect among others and thus connect to systems like Keycloak, Authentik, Azure AD or Okta. Additionally, there is integrated MFA support. We plan this connection as early as possible so you don't have to switch to SSO/MFA only after go-live.

Yes, we typically set up name, logo, language, basic navigation structure as well as initial role/permission models and email sending. The depth is flexible: from 'minimal basic setup' to jointly developed structure for IT documentation, processes and projects. What exactly is part of the installation package is clarified in the quote.

Yes. BookStack offers official options for LDAP, SAML 2.0 and OIDC, allowing common identity providers like AD/LDAP, Keycloak, Authentik or Azure AD to be connected. We handle configuration, mapping of groups to roles and testing – including documentation for your IT team.

Yes. Especially during introduction, migration from Confluence, Notion, MediaWiki, DokuWiki or file collections is common. We plan with you structure mapping (Spaces → Shelves/Books etc.), pilot migration, cutover strategy and fallback. Technically, we use exports, API imports or scripts – always focusing on the content that is really relevant for you.

BookStack itself is relatively lightweight; requirements depend more on user count, concurrent access and upload volume. Official guides mention PHP 8.x, MySQL/MariaDB and a standard LAMP/LEMP environment as a base, without rigid sizes. We consider ticket/document growth, upload size and desired reserves and derive concrete resource recommendations from that.

At minimum, DB contents and the BookStack file directory (uploads, configuration) must be backed up. We define with you intervals, retention times, encryption and offsite backup, set up jobs and test restores – e.g. on a staging instance to realistically practice disaster recovery scenarios.

You can do everything internally, book only occasional support (e.g. for major upgrades) or commission WZ-IT with ongoing operations. Official notes emphasize always backing up database and uploads before updates. In the managed model, we take care of monitoring, security fixes, capacity planning and documented update processes.

SaaS wikis reduce operational effort but put data location, integrations and update cycles in the hands of the provider. BookStack is open source, self-hosted and offers full infrastructure and data control with low licensing costs, but requires initial installation and ongoing operations. WZ-IT helps to realistically assess effort and risks of both approaches.

You save time, risk and internal training: We bring best practices for architecture, security, backups, updates and integrations – plus experience from other environments. Official docs cover the standard well, but don't address your specific infrastructure, compliance requirements and processes. That's exactly where we come in.

Typical process: provision server/VM, install base stack (Linux, web server, PHP, DB), set up BookStack according to official instructions via Git/Composer or install script, configure .env, set up mail & TLS, create initial users/roles, test backups, then onboard pilot users. WZ-IT can handle this process turnkey.

Official requirements mention only technology stack, no exact sizes. Experience and community examples show: A dedicated VM with multiple vCPUs, sufficient RAM and storage (incl. backups) is often sufficient, upload volume is decisive. Ongoing costs depend mainly on infrastructure price, operating model and support depth – we clarify this in the sizing call.

On-prem brings maximum physical control and can fit internal operating models. Cloud hosting scores with flexibility, quickly scalable resources and easy redundancy. Technically, BookStack runs the same in both scenarios – equipment, security and network design are decisive. WZ-IT outlines both variants with you including cost and operational differences.

Effort depends on scope, structure and integrations of your existing Confluence instance. Typical: requirements workshop, define target structure in BookStack, migrate pilot area, then gradually take over content and train teams. Technically, exports, API imports and manual follow-up are needed. WZ-IT accompanies conception, migration, training and if needed also handles ongoing operations.