||3 years ago|
|.github||4 years ago|
|app||3 years ago|
|bootstrap||3 years ago|
|database||3 years ago|
|dev/docker||3 years ago|
|public||3 years ago|
|resources||3 years ago|
|routes||3 years ago|
|storage||5 years ago|
|tests||3 years ago|
|themes||5 years ago|
|.env.example||4 years ago|
|.env.example.complete||3 years ago|
|.gitattributes||7 years ago|
|.gitignore||5 years ago|
|.travis.yml||5 years ago|
|LICENSE||5 years ago|
|artisan||5 years ago|
|composer.json||4 years ago|
|composer.lock||4 years ago|
|docker-compose.yml||3 years ago|
|package-lock.json||3 years ago|
|package.json||3 years ago|
|phpcs.xml||5 years ago|
|phpunit.xml||3 years ago|
|readme.md||3 years ago|
|server.php||7 years ago|
|version||3 years ago|
|webpack.config.js||3 years ago|
A platform for storing and organising information and documentation. General information and documentation for BookStack can be found at https://www.bookstackapp.com/.
📚 Project Definition
BookStack is an opinionated wiki system that provides a pleasant and simple out of the box experience. New users to an instance should find the experience intuitive and only basic word-processing skills should be required to get involved in creating content on BookStack. The platform should provide advanced power features to those that desire it but they should not interfere with the core simple user experience.
BookStack is not designed as an extensible platform to be used for purposes that differ to the statement above.
In regards to development philosophy, BookStack has a relaxed, open & positive approach. At the end of the day this is free software developed and maintained by people donating their own free time.
🛣️ Road Map
Below is a high-level road map view for BookStack to provide a sense of direction of where the project is going. This can change at any point and does not reflect many features and improvements that will also be included as part of the journey along this road map. For more granular detail of what will be included in upcoming releases you can review the project milestones as defined in the "Release Process" section below.
- Platform REST API (In Design)
- A REST API covering, at minimum, control of core content models (Books, Chapters, Pages) for automation and platform extension.
- Editor Alignment & Review
- Review the page editors with goal of achieving increased interoperability & feature parity while also considering collaborative editing potential.
- Permission System Review
- Improvement in how permissions are applied and a review of the efficiency of the permission & roles system.
- Installation & Deployment Process Revamp
- Creation of a streamlined & secure process for users to deploy & update BookStack with reduced development requirements (No git or composer requirement).
🚀 Release Versioning & Process
BookStack releases are each assigned a version number, such as "v0.25.2", in the format
v<phase>.<feature>.<patch>. A change only in the
patch number indicates a fairly minor release that mainly contains fixes and therefore is very unlikely to cause breakages upon update. A change in the
feature number indicates a release which will generally bring new features in addition to fixes and enhancements. These releases have a small chance of introducing breaking changes upon update so it's worth checking for any notes in the update guide. A change in the
phase indicates a much large change in BookStack that will likely incur breakages requiring manual intervention.
Each BookStack release will have a milestone created with issues & pull requests assigned to it to define what will be in that release. Milestones are built up then worked through until complete at which point, after some testing and documentation updates, the release will be deployed.
For feature releases, and some patch releases, the release will be accompanied by a post on the BookStack blog which will provide additional detail on features, changes & updates otherwise the GitHub release page will show a list of changes. You can sign up to be alerted to new BookStack blogs posts (once per week maximum) at this link.
🛠️ Development & Testing
All development on BookStack is currently done on the master branch. When it's time for a release the master branch is merged into release with built & minified CSS & JS then tagged at its version. Here are the current development requirements:
- Node.js v10.0+
# Install NPM Dependencies npm install # Build assets for development npm run build # Build and minify assets for production npm run production # Build for dev (With sourcemaps) and watch for changes npm run dev
BookStack has many integration tests that use Laravel's built-in testing capabilities which makes use of PHPUnit. There is a
mysql_testing database defined within the app config which is what is used by PHPUnit. This database is set with the database name, user name and password all defined as
bookstack-test. You will have to create that database and that set of credentials before testing.
The testing database will also need migrating and seeding beforehand. This can be done with the following commands:
php artisan migrate --database=mysql_testing php artisan db:seed --class=DummyContentSeeder --database=mysql_testing
Once done you can run
php vendor/bin/phpunit in the application root directory to run all tests.
📜 Code Standards
PHP code within BookStack is generally to PSR-2 standards. From the BookStack root folder you can run
./vendor/bin/phpcs to check code is formatted correctly and
./vendor/bin/phpcbf to auto-fix non-PSR-2 code.
🐋 Development using Docker
This repository ships with a Docker Compose configuration intended for development purposes. It'll build a PHP image with all needed extensions installed and start up a MySQL server and a Node image watching the UI assets.
To get started, make sure you meet the following requirements:
- Docker and Docker Compose are installed
- Your user is part of the
If all the conditions are met, you can proceed with the following steps:
- Install PHP/Composer dependencies with
docker-compose run app composer install(first time can take a while because the image has to be built).
APP_KEYto a random 32 char string.
- Make sure port 8080 is unused or else change
DEV_PORTto a free port on your host.
chgrp -R docker storage. The development container will chown the
storagedirectory to the
www-datauser inside the container so BookStack can write to it. You need to change the group to your host's
dockergroup here to not lose access to the
docker-compose upand wait until all database migrations have been done.
- You can now login with
passwordas password on
localhost:8080(or another port if specified).
If needed, You'll be able to run any artisan commands via docker-compose like so:
docker-compose run app php artisan list
The docker-compose setup runs an instance of MailHog and sets environment variables to redirect any BookStack-sent emails to MailHog. You can view this mail via the MailHog web interface on
localhost:8025. You can change the port MailHog is accessible on by setting a
DEV_MAIL_PORT environment variable.
All text strings can be found in the
resources/lang folder where each language option has its own folder. To add a new language you should copy the
en folder to an new folder (eg.
fr for french) then go through and translate all text strings in those files, leaving the keys and file-names intact. If a language string is missing then the
en translation will be used. To show the language option in the user preferences language drop-down you will need to add your language to the options found at the bottom of the
resources/lang/en/settings.php file. A system-wide language can also be set in the
.env file like so:
You will also need to add the language to the
locales array in the
There is a script available which compares translation content to
en files to see what items are missing or redundant. This can be ran like so from your BookStack install folder:
# Syntax php resources/lang/check.php <lang> # Examples php resources/lang/check.php fr php resources/lang/check.php pt_BR
Some strings have colon-prefixed variables in such as
:userName. Leave these values as they are as they will be replaced at run-time.
🎁 Contributing, Issues & Pull Requests
Feel free to create issues to request new features or to report bugs & problems. Just please follow the template given when creating the issue.
Pull requests are welcome. Unless a small tweak or language update, It may be best to open the pull request early or create an issue for your intended change to discuss how it will fit in to the project and plan out the merge. Pull requests should be created from the
master branch since they will be merged back into
master once done. Please do not build from or request a merge into the
resources/assets. Any CSS or JS files within
public are built from these source files and therefore should not be edited directly.
The project's code of conduct can be found here.
Security information for administering a BookStack instance can be found on the documentation site here.
If you'd like to be notified of new potential security concerns you can sign-up to the BookStack security mailing list.
If you would like to report a security concern in a more confidential manner than via a GitHub issue, You can directly email the lead maintainer ssddanbrown. You will need to login to be able to see the email address on the GitHub profile page. Alternatively you can send a DM via twitter to @ssddanbrown.
We want BookStack to remain accessible to as many people as possible. We aim for at least WCAG 2.1 Level A standards where possible although we do not strictly test this upon each release. If you come across any accessibility issues please feel free to open an issue.
🖥️ Website, Docs & Blog
The website which contains the project docs & Blog can be found in the BookStackApp/website repo.
The BookStack source is provided under the MIT License. The libraries used by, and included with, BookStack are provided under their own licenses.
The great people that have worked to build and improve BookStack can be seen here.
These are the great open-source projects used to help build BookStack: