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

New Issue

Open

opened 2025-07-24 14:27:26 +00:00 by aadil · 1 comment

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

Owner

Copy Link

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.

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

Owner

Copy Link

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.

No Branch/Tag Specified

Branches Tags

main

ftp

ssh

service-rename

drone

2.16.1+6.8.1

2.16.0+6.8.1

2.15.0+6.8.0

2.14.0+6.7.2

2.13.3+6.7.1

2.13.2+6.7.1

2.13.1+6.7.1

2.13.0+6.7.1

2.12.2+6.6.2

2.12.1+6.6.1

2.12.0+6.6.1

2.11.0+6.6.0

2.10.0+6.5.5

2.9.1+6.5.3

2.9.0+6.5.2

2.8.0+6.5.0

2.7.3+6.4.3

2.5.2+6.3.0

2.7.2+6.4.2

2.7.1+6.4.2

2.7.0+6.4.2

2.6.3+6.4.2

2.6.1+6.4.0

2.6.0+6.4.0

2.5.1+6.3.0

2.5.0+6.3.0

2.4.3+6.3.0

2.4.2+6.3.0

2.4.1+6.3.0

2.4.0+6.3.0

2.3.0+6.2.0

2.2.1+6.1.1

2.3.3+6.2.2

2.3.2+6.2.0

2.3.1+6.2.0

2.2.0+6.1.1

2.1.0+6.1.1

2.0.1+6.0.1

2.0.0+6.0.0

1.1.2+5.9.3

1.1.1+5.9.2

1.1.0+5.9.0

1.0.2+5.8.3

1.0.1+5.8.2

1.0.0+5.8.1

Labels

No items

No Label

Milestone

No items

No Milestone

Assignees

Clear assignees

3wordchant aadil abra-bot ammaratef45 Apfelwurm appletalk arjan basebuilder Brooke carla cas codegod100 coopcloud decentral1se fauno flancian Frando iexos javielico jmakdah2 kawaiipunk knoflook lambdabundesverband mac-chaffee marlon mayel mirsal moritz nicksellen notplants p4u1 pau renovate-bot rix sef simon sixsmith stevensting tobias trav val virtualboys wolcen wykwit xynosis yksflip

No Assignees

2 Participants

Notifications

Subscribe

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: coop-cloud/wordpress#46

No description provided.