BookStackApp/system-cli

BookStack System CLI

A simple command line interface for managing instances of BookStack. Provides the following commands:

• Init - Setup a fresh BookStack installation within a folder.
• Backup - Creates a backup of an existing BookStack installation to a single ZIP file.
• Restore - Restore a backup ZIP into an instance of BookStack.
• Update - Update an existing BookStack installation to the latest version.

This CLI is intended to be platform abstract, intended for plain installs that follow our scripts/manual instructions. This is intended to work independently of BookStack itself, so it can be used even if a BookStack instance is not available or broken, although it could be distributed with and called upon by the core BookStack codebase.

Development

This project uses composer to manage PHP dependencies. They can be installed as follows:

composer install

This project is intended to be bundled up into a single phar file for portability and separation with BookStack itself. This can be done by running the compile file:

php compile.php

Tests can be ran via PHPUnit within the docker environment as described below. It is not advised to run tests outside of this docker environment since tests are written to an expected pre-configured system environment.

Docker Environment

A docker-compose setup exists to create a clean, contained environment, which is important for this project since the CLI checks and interacts with many system-level elements.

# Build the environment container
docker compose build

# Enter the environment
docker compose run app

# From there you'll be dropped into a bash shell within the project directory.
# You could proceed to install dependencies via composer via:
composer install

# Then you can run tests via:
vendor/bin/phpunit

# To clean-up and delete the environment:
docker compose down -v --remove-orphans

Within the environment a pre-existing BookStack instance can be found at /var/www/bookstack for testing.

Contributing

I welcome issues and PRs but keep in mind that I'd like to keep the feature-set narrow to limit support/maintenance burden. Therefore, I likely won't leave issues open long, or merge PRs, for requests to add new features or for changes that increase the scope of what this script already supports.

Known Issues

mysqldump - Couldn't execute 'FLUSH TABLES'

mysqldump may produce the following:

mysqldump: Couldn't execute 'FLUSH TABLES': Access denied; you need (at least one of) the RELOAD or FLUSH_TABLES privilege(s) for this operation (1227)

This was due to 8.0.32 mysqldump, changing the required permissions, and this should be largely fixed as per 8.0.33. Temporary workaround is to provide the database user RELOAD permissions. For example:

GRANT RELOAD ON *.* TO 'bookstack'@'localhost';

mysql - Restore throws permission error

MySQL during restore can throw the following:

ERROR 1227 (42000) at line 18 in file: '/root/bookstack/restore-temp-1682771620/db.sql': Access denied; you need (at least one of) the SUPER, SYSTEM_VARIABLES_ADMIN or SESSION_VARIABLES_ADMIN privilege(s) for this operation

This is due to mysql adding replication data to the output. We could set --set-gtid-purged=value during dump but does not exist for mariadb. Alternatively, we could maybe filter these SET lines? But need to be targeted and efficient since files dump files may be large.

mysql - Only TCP connections

This assumes a database connection via a TCP connection is being used by BookStack. Socket/other type of connections could technically be used with BookStack but is not something we advise or document within our docs or env options listing, so we make this assumption for simplicity.