Include CORS proxy with website builds #1880
Merged
Add this suggestion to a batch that can be applied as a single commit. This suggestion is invalid because no changes were made to the code. Suggestions cannot be applied while the pull request is closed. Suggestions cannot be applied while viewing a subset of changes. Only one suggestion per line can be applied in a batch. Add this suggestion to a batch that can be applied as a single commit. Applying suggestions on deleted lines is not supported. You must change the existing code in this line in order to create a valid suggestion. Outdated suggestions cannot be applied. This suggestion has been applied or marked resolved. Suggestions cannot be applied from pending reviews. Suggestions cannot be applied on multi-line comments. Suggestions cannot be applied while the pull request is queued to merge. Suggestion cannot be applied right now. Please check back later.
Motivation for the change, related issues
This PR updates the Playground website build to include the CORS proxy.
The proxy is not quite ready for broad use yet. The following issues need to be addressed:
But, @adamziel, if desired and if you are comfortable with the risk, you could merge this and deploy the CORS proxy now to enable initial testing.
Implementation details
This updates nx project descriptions to include php-cors-proxy scripts with the Playground website builds.
Testing Instructions (or ideally a Blueprint)
npx nx build playground-website
ls dist/packages/playground/wasm-wordpress-net/ | grep cors-proxy
and confirmcors-proxy.php
andcors-proxy-functions.php
are present.