When running the task build:wp, I'm seeing the following error.
/bin/bash: gsed: command not found
The command '/bin/bash -c echo '<!doctype html>' > wordpress-static/wp-includes/empty.html && gsed -E 's#srcDoc:"[^"]+"#src:"/wp-includes/empty.html"#g' -i wordpress-static/wp-includes/js/dist/block-editor.min.js && gsed -E 's#srcDoc:"[^"]+"#src:"/wp-includes/empty.html"#g' -i wordpress-static/wp-includes/js/dist/block-editor.js' returned a non-zero code: 127
It's coming from src/wordpress-playground/wordpress/Dockerfile.
RUN echo '<!doctype html>' > wordpress-static/wp-includes/empty.html && \
gsed -E 's#srcDoc:"[^"]+"#src:"/wp-includes/empty.html"#g' -i wordpress-static/wp-includes/js/dist/block-editor.min.js && \
gsed -E 's#srcDoc:"[^"]+"#src:"/wp-includes/empty.html"#g' -i wordpress-static/wp-includes/js/dist/block-editor.jsFrom a quick search, it seems gsed is GNU sed renamed by Homebrew on macOS. Inside the Docker container, I believe the above lines should be calling sed instead. If so, I'd be happy to make a little pull request.
When running the task
build:wp, I'm seeing the following error.It's coming from
src/wordpress-playground/wordpress/Dockerfile.From a quick search, it seems
gsedis GNUsedrenamed by Homebrew on macOS. Inside the Docker container, I believe the above lines should be callingsedinstead. If so, I'd be happy to make a little pull request.