Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,5 +1,18 @@ | ||
| #!/usr/bin/env bash -l | ||
| # NOTE: you should keep the above line, at line 1. Only modify if you know what you are doing. | ||
|
|
||
| # You should use npx 10up-toolkit build to build your project. When you do, there are a number of things | ||
| # you get "for free" including nvm handling and the basics of building are handled automatically. You | ||
| # only need to provide additional build routines if the default build system doesn't quite get things | ||
| # right. Adding build scripts is easy. Create as many .sh files as you need in this scripts directory. | ||
|
|
||
| # Here is an example script you can use to get you started It assumes you are using a "modern" layout. | ||
|
|
||
| # change directories to your theme or plugin | ||
| pushd . | ||
|
|
||
| # run your build commands | ||
| echo "Hello World!" | ||
|
|
||
| # return to where we were so the next build script starts off from the same place | ||
| popd |
File renamed without changes.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,13 +1,180 @@ | ||
| #!/usr/bin/env bash -l | ||
|
|
||
| # Various tasks to determine some things like what kind of project is this | ||
| # such as standard, wp-content rooted...something else? | ||
| function build:preflight { | ||
| # Check for a default, standard layout that has a wordpress directory | ||
| if [ -d wordpress ] && [ -d build ]; then # this is probably a standard setup | ||
| echo "Detected standard WordPress repository layout" | ||
| PROJECT_TYPE="standard" | ||
| WORDPRESS_BUILD_ROOT="wordpress/wp-content" | ||
| return | ||
| fi | ||
|
|
||
| # Check for a wp-content rooted style repository | ||
| if [ -d plugins ] || [ -d themes ]; then # this is probably a wp-root repo | ||
| echo "Detected wp-content rooted WordPress repository layout" | ||
| PROJECT_TYPE="wpcontent" | ||
| WORDPRESS_BUILD_ROOT="." | ||
| return | ||
| fi | ||
|
|
||
| } | ||
|
|
||
|
|
||
| # Routine to determine what version of WordPress to install | ||
| function build:version { | ||
|
|
||
| WORDPRESS_VERSION="latest" | ||
| if [ ${CI:-false} = "true" ]; then | ||
| if [ -z ${WORDPRESS_VERSION} ]; then | ||
| WORDPRESS_VERSION="latest" | ||
| fi | ||
| else | ||
| GIT_BRANCH=$(git branch --format='%(refname:short)' --show-current) | ||
| GIT_BRANCH_SLUG=$(utilities:create-gitlab-slug ${GIT_BRANCH}) | ||
| ENVIRONMENT=$(yq eval '.environments | to_entries[] | select(.value.branch == "'${GIT_BRANCH_SLUG}'") | .key' ${TENUP_CI_FILE}) | ||
|
|
||
| if [ ${ENVIRONMENT:-null} != "null" ]; then | ||
| WORDPRESS_VERSION=$(yq '.environments.'${ENVIRONMENT}'.wordpress_version' ${TENUP_CI_FILE}) | ||
| fi | ||
| fi | ||
|
|
||
| if [ "${WORDPRESS_VERSION}" == "latest" ]; then | ||
| WORDPRESS_VERSION=$(curl -s https://api.wordpress.org/core/version-check/1.7/ | jq '.offers[0].current' | tr -d '"') | ||
| fi | ||
|
|
||
| echo ${WORDPRESS_VERSION} | ||
| } | ||
|
|
||
| function build:install { | ||
| build:preflight | ||
|
|
||
| # we use command in case wp-cli is installed as an alias | ||
| if [[ -z $(command -v wp) ]]; then | ||
| echo "wp-cli is not installed or in your path but it is required" | ||
| exit 1 | ||
| fi | ||
|
|
||
| local WORDPRESS_VERSION=$(build:version) | ||
| echo "Installing WordPress version: ${WORDPRESS_VERSION}" | ||
|
|
||
| if [ ${PROJECT_TYPE} = "standard" ]; then | ||
| mkdir -p wordpress/wp-content | ||
| pushd wordpress | ||
| else | ||
| mkdir -p payload/wp-content | ||
| pushd payload | ||
| fi | ||
| wp core download --version=${WORDPRESS_VERSION} --skip-content --force | ||
| popd | ||
|
|
||
| } | ||
|
|
||
| function build:main { | ||
| set -eo pipefail | ||
|
|
||
| build:preflight | ||
|
|
||
| # don't call this script directly | ||
| if [ $(shopt -q login_shell) ]; then | ||
| echo "Please call this using build/local.sh rather than directly" | ||
| exit 1 | ||
| fi | ||
|
|
||
| # This is your "main" build file. By default, it builds a 10up/wp-scaffold style project | ||
| # but you are free to modify it as required for your project. Remember, you can also | ||
| # drop in any number of scripts and they will be run in alphabetical order AFTER main.sh | ||
|
|
||
| # detect if this is a standard layout or not | ||
|
|
||
| if [ -d wordpress/wp-content ]; then | ||
| pushd wordpress/wp-content | ||
| elif [ -d plugins ]; then | ||
| pushd . # go no where, we are already in the right spot | ||
| fi | ||
| if [ "${CI:-false}" = "true" ] && [ -f composer.json ]; then | ||
| if [ ! -f composer.lock ] && [ -f composer.json ]; then | ||
| echo "No composer.lock file detected. You should create/commit an up to date composer.lock file!" | ||
| exit 1 | ||
| else | ||
| composer install --no-dev | ||
| fi | ||
| elif [ -f composer.json ]; then | ||
| composer install | ||
| fi | ||
|
|
||
|
|
||
| if [ -f package.json ]; then | ||
| # Ensure we have the correct node version installed | ||
| nvm install | ||
| nvm use | ||
|
|
||
| if [ "${CI:-false}" = "true" ] && [ -f package.json ]; then | ||
| if [ -f package-lock.json ]; then | ||
| npm ci | ||
| else | ||
| echo "No package-lock.json file detected. You should create/commit an up to date package-lock.json file!" | ||
| exit 1 | ||
| fi | ||
| else | ||
| npm install | ||
| fi | ||
|
|
||
| npm run build | ||
| fi | ||
| popd | ||
| } | ||
|
|
||
| function build:local { | ||
| set -eo pipefail | ||
| # Create additional build scripts in the build directory with a .sh | ||
| # extension. They should do their work inside the wordpress directory. | ||
|
|
||
| # We always call main.sh first | ||
| build:main | ||
|
|
||
| # Then call any other drop in scripts next | ||
| for I in $(ls scripts/*sh) | ||
| do | ||
| . $I | ||
| done | ||
| } | ||
|
|
||
| # Perform a CI like build | ||
| function build:full { | ||
| set -eo pipefail | ||
|
|
||
| build:preflight | ||
| build:install | ||
| build:local | ||
|
|
||
| # This rsync will typically work but if you have integrated the CI Library | ||
| # into a non project template based project you should adjust it | ||
|
|
||
| # First determine if we are using a project rsync-exclude or the included one | ||
| if [ -f scripts/rsync-excludes.txt ]; then | ||
| RSYNC_EXCLUDES="scripts/rsync-excludes.txt" | ||
| fi | ||
|
|
||
| if [ ${PROJECT_TYPE} == "standard" ]; then | ||
| rsync -a --exclude-from=${RSYNC_EXCLUDES} wordpress/ payload/ | ||
| else | ||
| for I in themes mu-plugins plugins | ||
| do | ||
| if [ -d $I ]; then | ||
| rsync -a --exclude-from=${RSYNC_EXCLUDES} $I/ payload/wp-content/$I | ||
| fi | ||
| done | ||
| fi | ||
|
|
||
| } | ||
|
|
||
| # Converts a git branch to a gitlab compatible slug | ||
| function utilities:create-gitlab-slug { | ||
| local VALUE=$(echo $1 | sed 's/[^a-zA-Z0-9]/-/g' | awk '{print tolower($0)}') | ||
|
|
||
| echo ${VALUE} | ||
| } | ||
|
|
||
| eval build:$@ |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters