-
Notifications
You must be signed in to change notification settings - Fork 4.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
wp-env: Edit PHP configuration with htaccess from .wp-env.json. #32363
Conversation
Size Change: +437 B (0%) Total Size: 1.03 MB
ℹ️ View Unchanged
|
I think based on our conversations in #28703, we don't want to expose php config to the end user. That said, I think it'd be super useful to increase the default sizes the environment uses. I don't think there is a reason for them to be so small. What do you think about just increasing those sizes without adding a config entry? Relatedly, are there actually config entries folks would need to change, or is it mostly just that the defaults aren't good? cc @ockham |
The default size is 2MB, which I think is very small. For example, this is not enough for a large jpeg image. Also, when importing data using plugins such as All-in-One WP Migration, the file size often exceeds 1GB. I think you need to set the default value to huge. I think you need to set the default value to huge. It is difficult to determine what is the right size to set. |
I came across this PR while checking for PRs that haven't been reviewed in a long time. #50490 seems to have raised the default upload size to 1GB. Additionally, you can change various settings by mapping the
{
"mappings": {
".htaccess": "./path/to/.htaccess"
}
}
Therefore, I would like to close this PR. |
Description
Closes #28703 and #29430. Related: #30377.
This PR makes it possible to edit PHP configuration via htaccess from .wp-env.json.
wp-env.json
.httacess
How has this been tested?
Types of changes
New feature
Checklist:
*.native.js
files for terms that need renaming or removal).