lebp-stack

Generic instance for web platform projects using Linux, Nginx, Bedrock, and PHP. Vagrant is used to provision a local dev VM and bootstrap it. Afterwards, Salt is launched for configuration. (In theory this makes the process more portable to a remote server or several.)

---

Setup instructions to run the first time

All commands have been developed in Mac OSX. Linux should work similarly, but Windows is un-tested. YMMV.

1. Get bedrock

To save setup time by avoiding building bedrock, download the bedrock binary from the latest lebp-stack release. Run these commands from the lebp-stack repo root, using the URL from the first command as the input to the second command.

# get github crafted url
curl -vl 'https://github.com/righdforsa/lebp-stack/releases/download/v0.1/bedrock' 2>&1 | grep 'location: ' | awk '{ print $3 }'

# get bedrock using github crafted url
curl -o bedrock.bin "<url>"

# validate (approximately) a successful download
test -s bedrock.bin && echo "Download Success" || echo "Download Failed"

# move the binary to the correct location and set permissions
vagrant ssh -c "sudo mv /vagrant/bedrock.bin /usr/sbin/bedrock && sudo chmod 755 /usr/sbin/bedrock"

• Note: "bedrock" binary downloaded above was last confirmed working under libc package version 2.31-0ubuntu9.9 and libpcre runtime files from 2:8.44-2+ubuntu20.04.1+deb.sury.org+1

Alternatively, build bedrock (takes ~20m the first time. Skip this step if you've just completed the above step.)

vagrant up
vagrant ssh -c "/vagrant/scripts/build-bedrock.sh"

2. Get php vendor libs (installed in configs/www/files/vendor-lebp-stack)

vagrant ssh -c "/vagrant/scripts/install-composer.sh"

3. Put the updated configs in the right places

vagrant ssh -c "/vagrant/scripts/run-salt.sh"

4. Run a local test to confirm basic functionality of the webserver, php environment and db

vagrant ssh -c "curl -vk https://localhost/test_bedrock.php"

Setup Complete!

---

Usage guide

How to connect to the api from the host workstation

update hosts file with the host-reachable IP from inside the vagrant vm

add the following line to /etc/hosts

10.2.2.3 lebp-stack.dev

validate the host entry with curl

curl -kv https://lebp-stack.dev:443/api.php

if the above step fails, check the IP of the VM to confirm the networking is set up in the expected way

trust the certificate (OSX)

Trust your certificate in macOS Keychain Access In order to connect to the api through the browser, (e.g. while running javascript in a web app project) you’ll need to tell your computer to trust the api webserver certificate since it’s not trusted by default.

TODO: since this is a public repo and publicly available cert, telling your system to trust it is actually a pretty big security hole. We need to find a more reliable way to manage this that is workable for the community. (e.g. create a new cert during provisioning and save it in SECRET)

• Open Keychain Access
• Highlight the System section on the left
• Open finder and navigate to the lebp-stack.dev cert in the lebp-stack repo
• drag and drop onto Keychain Access > System
• in Keychain Access, Navigate to your certificate and double click it
• In the dropdown “When using this certificate” choose “Always trust“
• Close the window to save your changes—this will prompt you for your administrator password

How to manage a lebp-stack install with project-specific configs

• Create a configs repo separate from lebp-stack.
• Check it out to /srv/project in the vm, where it will be automatically included as another source tree by the salt minion config
• Create "/overlay.sls" config files, which will be automatically included
• Run vagrant ssh -c "sudo salt-call --local state.highstate" to execute your custom states

---

Chris' legacy notes, just for him, please ignore:

Build bedrock

vagrant up
vagrant ssh -c "cd /srv/project/lebp-stack/Bedrock && make clean && make CC=gcc-9 all"
vagrant ssh -c "touch /var/tmp/bedrock.db && chmod 744 /var/tmp/bedrock.db"
vagrant ssh -c "/srv/project/lebp-stack/Bedrock/bedrock -db /var/tmp/bedrock.db" 
cat /etc/rc.local
/srv/project/lebp-stack/Bedrock/bedrock -db /var/tmp/bedrock.db -fork

initial repo creation commands

# git commands
git init lebp-stack
cd lebp-stack
git submodule add git@github.com:Expensify/Bedrock.git
# maybe not needed because Bedrock makefile inits mbedtls, but including what I actually did
cd Bedrock
git submodule update --init
cd ../

Running as a submodule in a larger project:

initial set up:

• cd lebp-stack/Bedrock && make CC=gcc-9 all
• cd lebp-stack/Bedrock-PHP && php7.4 /usr/bin/composer install
• cd lebp-stack/scripts && sudo ./place-bedrock.sh

todo list:

get bedrock to compile and run

add php folder

update Vagrantfile to be idempotent/work from scratch get bedrock php libs working

• work on passing the right config to the constructor