Add an option to add volumes for persistent custom content #46

New Issue

2025-07-24T14:27:26Z

aadil commented

2025-07-24 14:27:26 +00:00

In a couple of sites I'm running, I need to add some custom content (pdfs/static html) files to the site root. This option would also be useful if you want to hack on a custom theme and push it to the container without setting up a complicated deployment process.

3wordchant commented

2025-07-24 14:55:36 +00:00

I'm not opposed to this being added as an option, as far as I understand it could introduce complications with updates, because updating the Co-op Cloud app wouldn't update the running version of Wordpress.

In a couple of sites I'm running, I need to add some custom content (pdfs/static html) files to the site root.

For PDFs I would recommend uploading them in the WP media library, and using the "redirections" plugin to set a neater URL.

This option would also be useful if you want to hack on a custom theme and push it to the container without setting up a complicated deployment process.

I think wp-content is already in a volume, so it could be directly edited in /var/lib/docker/volumes.

I'm not opposed to this being added as an option, as far as I understand it could introduce complications with updates, because updating the Co-op Cloud app wouldn't update the running version of Wordpress. > In a couple of sites I'm running, I need to add some custom content (pdfs/static html) files to the site root. For PDFs I would recommend uploading them in the WP media library, and using the "redirections" plugin to set a neater URL. > This option would also be useful if you want to hack on a custom theme and push it to the container without setting up a complicated deployment process. I think `wp-content` is already in a volume, so it could be directly edited in `/var/lib/docker/volumes`.

Sign in to join this conversation.

2 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: coop-cloud/wordpress#46