feat(slic-stack.yml) control the WP_HTTP_BLOCK_EXTERNAL const #173
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.
Use the SLIC_WP_HTTP_BLOCK_EXTERNAL env var.
By default
slic
will set up the embedded WordPress installation to block all outgoing HTTP requests using theWP_HTTP_BLOCK_EXTERNAL
constant.In some instances this might cause issues with projects that need to call outside APIs to work.
This PR explores the possibility of controlling that constant value using the
SLIC_WP_HTTP_BLOCK_EXTERNAL
env var.Similarly, this PR introduces control, via the
.env.slic.run
file, for theDISABLE_WP_CRON
constant defined in thewp-config.php
file.