If you’re updating PCRE as well as nginx, here are some commands to insert in
the appropriate places (“appropriate” being an exercise left to the reader).
gpg2 --homedir /tmp/$ --keyserver keyserver.ubuntu.com --recv-key \
45F68D54BBE23FB3039B46E59766E084FB0F43D8 # Philip Hazel's public GPG key for pcre (https://www.pcre.org/).
gpg2 --homedir /tmp/$ --verify pcre-8.*.tar.gz.sig
find packages/nginx-${VERSION} -type f -print0 | \
xargs -0 perl -pi -e \
"s/pcre-8.42/pcre-8.45/g"
bosh add-blob \
blobs/pcre-8.45.tar.gz \
pcre-8.45.tar.gz
bosh add-blob \
blobs/pcre-8.45.tar.gz.sig \
pcre-8.45.tar.gz.sig
Nginx Release
To vendor nginx package into your release, run:
The above code will add
nginxtoyour-releaseand introduce aspec.lock.Included packages:
To use the
nginxpackage at runtime in your job scripts:See jobs/nginx-test for example.
Development
To run tests
cd tests/ && BOSH_ENVIRONMENT=vbox ./run.shUpdating nginx
When determining the latest version of nginx, use the mainline branch, not the stable branch, at http://nginx.org/en/download.html.
Follow the instructions below, and make sure to set
VERSIONto the newest nginx release, andOLD_VERSIONto the current BOSH release’s nginx version:Configure
config/private.yml, (hint: LastPass, “CF Bosh Packages”), then:Commit & push:
Trigger new build: https://ci.bosh-ecosystem.cf-app.com/teams/main/pipelines/nginx-release
Optional: Bumping PCRE
If you’re updating PCRE as well as nginx, here are some commands to insert in the appropriate places (“appropriate” being an exercise left to the reader).
Optional: Sources
Addenda
A copy of the PGP signing keys is available in
keys/in the event that a key server is down or that a key’s URL has changed.