Releases: greenpeace/planet4-develop
Releases · greenpeace/planet4-develop
v0.7.2
v0.7.1
Bug fixes
- Fix semver usage for compat with
npm version
v0.7
Changes
- #24
wp-env
is now used as a local package- all
wp-env
commands should now run asnpx wp-env
- all
- #22 Update deprecated
gsutil
usage togcloud storage
- requires an up-to-date
gcloud
installation
- requires an up-to-date
- #23 PHP shell user in
npm run shell:php
is now local user by default- use
npm run shell:php:root
to getroot
- use
Bug fixes
- #21
.htaccess
should now handle wp-uploads and local bucket urls and display images properly.htaccess
was moved outside ofwp-content
- a new command
npm run env:htaccess
was added for testing purpose, it regenerates the htaccess file
- #20 Composer process timeout is not added to
composer.json
files anymore - Installation should not crash if
gcloud
is not authenticated admin
user should be created if it does not exist
Install/update guide
Clean install
-
Install NVM: https://github.com/nvm-sh/nvm#installing-and-updating
-
Install gcloud CLI: https://cloud.google.com/sdk/docs/install
- or update with
gcloud components update
- authenticate with
gcloud auth login
- or update with
-
Install environment
> git clone [email protected]:greenpeace/planet4-develop.git
> cd planet4-develop
> nvm use
> npm install
> npm run nro:install <your nro name>
# (for p4-team, please use `npm run env:install` instead, or `npm run build:repos` afterward)
Update existing install
- Stop your local environment
npm run env:stop
- Please update your
gcloud
tools if necessary !
Depending on your installation, this might be done automatically by your system (Linux usually);
but it might also depend on you doing it manually (MacOS).
This command will either update the tools or tell you if it's not necessary.> gcloud components update
- Update this repository
git fetch -v -t
git checkout v0.7
- Remove
wp-env
global installnpm -g remove @wordpress/env
- Run
npm install
- Almost done :)
- Run
npm run env:start
- Remove file in
./planet4/.htaccess
and runnpm run env:htaccess
- Run
npm run env:start
again to restart
- Run
v0.6
v0.5
- Update to @wordpress/env 8.0.0
- Fixes file permissions issues
- Has grouped containers for cli/wp/composer
- Disallow unknown config keys
- Change in content mapping and paths
- Change in functions to run wp, composer, cli commands
- wp-env version check
- unexpected version is marked with a red cross
- change config .p4-env.json to .wp-env.json merge strategy
- external config keys moved to .p4-env.json, override for both config used
composer run-script site:custom
works and runs automatically on nro:install- fix on CI E2E results export
Update instructions
- Save your work (the update process will destroy everything)
- Destroy everything
npm run env:destroy
- Update this repo
- Update wp-env package
npm -g install @wordpress/[email protected]
- Reinstall 🕺
v0.4
- Shell commands for easy access to php and mysql containers
shell:php
shell:mysql
- Elastic search container and commands
elastic:activate
elastic:deactivate
- Reverse proxy for NRO assets to gcloud bucket
- Default URL set to
http://www.planet4.test
- Prod URL detection from CI config, URL replacement with local URL on install
- Requirements debug