one-click-apps

one-click-apps copied to clipboard

Modifying the WordPress upload size is a very common use-case, as discussed in issue #175. I would like to suggest adding a second persistent volume;

                "volumes": [
                    "$$cap_appname-wp-data:/var/www/html",
                    "$$cap_appname-php:/usr/local/etc/php"
                ],

You can always add this volume post installation. What we try to stay away from is that there is a lot of common use cases, if we incorprate all of them, then the installation process becomes for complex for newbies.

On the other hand, experienced developers always know what they need to change and they can go ahead and modify whatever value they need to. As a general rule of thumb, as long as, the modification is possible, we don't add it to the general flow in order to keep the general flow smoother.

I agree that practically anything can be done post-installation. Perhaps allowing creation of persistent custom templates or the ability to use a standard docker-compose would alleviate the need to modify pre-defined templates.

Off topic... genuine question...

but isn't this a bad idea for security reasons?

To customize it and keep using the native Docker from WordPress you just need to access your server, create a file uploads.ini which is including your changes, and set this file as persistent, I created a file in this path below with the respective content.

Path in App: /usr/local/etc/php/conf.d/uploads.ini Path on Host: /var/lib/docker/volumes/caprover--rafael-wp-data/uploads.ini

file_uploads = On
memory_limit = 500M
upload_max_filesize = 500M
post_max_size = 500M
max_execution_time = 600

After setting it, your container will be reloaded and it's going to be like this image below.