Local Development on macOS

Following these instructions will give you a local development network of Pressbooks based on roots/bedrock and roots/trellis, with the following features:

1. Dependencies

Install Homebrew:

/usr/bin/ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)"

Install Homebrew Cask:

brew tap caskroom/cask

Install Ansible:

brew install ansible

Install Virtualbox:

brew cask install virtualbox

Install Vagrant:

brew cask install vagrant

Install vagrant-bindfs:

vagrant plugin install vagrant-bindfs

Install vagrant-hostmanager:

vagrant plugin install vagrant-hostmanager

Install Composer:

brew install composer

Install Node:

brew install node

Install Yarn:

brew install yarn

2. Setup

Create a directory for your local development environment and cd there:

mkdir ~/Code/pressbooks-dev && cd ~/Code/pressbooks-dev

Clone pressbooks/trellis into ~/Code/pressbooks-dev/trellis:

git clone --depth=1 git@github.com:pressbooks/trellis.git && rm -rf trellis/.git

Clone pressbooks/bedrock into ~/Code/pressbooks-dev/site:

git clone --depth=1 git@github.com:pressbooks/bedrock.git site && rm -rf site/.git

Add pressbooks/pressbooks, pressbooks/pressbooks-publisher and pressbooks/pressbooks-book to your Bedrock dependencies (for more information on this strategy, see this post)

cd ~/Code/pressbooks-dev/site
composer require pressbooks/pressbooks:dev-dev
composer require pressbooks/pressbooks-publisher:dev-dev
composer require pressbooks/pressbooks-book:dev-dev

3. Configuration

Edit ~/Code/pressbooks-dev/trellis/group_vars/development/wordpress_sites.yml to reflect your desired local development site URL, replacing all instances of example.dev with pressbooks.dev, pressbooks.test or whatever you prefer. For example:

- canonical: pressbooks.dev
- www.pressbooks.dev
local_path: ../site # path targeting local Bedrock site directory (relative to Ansible root)
admin_email: admin@pressbooks.dev
enabled: true
subdomains: false
enabled: false
provider: self-signed
enabled: false
domain_current_site: pressbooks.dev
wp_home: http://pressbooks.dev
wp_siteurl: http://pressbooks.dev/wp

You can leave example.com as is unless you plan on setting up matching staging or production environments. In that case, you will need to update all instances of example.com in ~/Code/pressbooks-dev/trellis/group_vars/ to a consistent value. If you are interested in configuring a staging or production environment, you should consult the Trellis docs as that is outside the scope of this tutorial.

4. Launch

Change to the ~/Code/pressbooks-dev/trellis/ directory and run vagrant up:

cd ~/Code/pressbooks-dev/trellis/ && vagrant up

You will be required to enter your macOS password at a certain point in the process. Fully provisioning your development environment may take up to 30 minutes.

5. Development Tools


The default Pressbooks username:password is admin:admin


Acess and error logs are located on the VM in following directory:


Unit Testing and Coding Standards

Unit testing in the VM:

vagrant ssh
cd /srv/www/example.com/current
bin/install-wp-tests.sh pressbooks_tests pressbooks_test '' latest true
composer test

Coding standards in the VM:

vagrant ssh
cd /srv/www/example.com/current
composer standards

Asset Building

We use webpack wrapped in Laravel Mix to build plugin assets (CSS and JavaScript) for Pressbooks.

  1. At the command prompt from the Pressbooks plugin directory, e.g. ~/Code/pressbooks-dev/site/web/app/plugins/pressbooks, run yarn to install build dependencies.
  2. Then, run yarn run dev or yarn run production to build your plugin assets (yarn run production will add a version hash to the asset manifest for browser cache busting).


cd ~/Code/pressbooks-dev/site
composer update pressbooks/pressbooks --with-dependencies
composer update pressbooks/pressbooks-publisher --with-dependencies
composer update pressbooks/pressbooks-book --with-dependencies