Docker volumes are filling up disk
-
@joseph I don't know if this can help, but I added to Wp cron this command:
55 1,13 * * * rm -rf /app/data/public/wp-content/cache/* > /dev/null 2>&1You can extend this also to /tmp folders.
I added this line to save space before backup. You can edit this according to backup scheduled times
-
Is it related to a plugin? I know that by default wp-cron jobs were not always running in WP so I had to force create a cron job to run wp-cron on a schedule
It is supposed to be the reponsibility of WP Plugins to cleanup after them, by using the wp-cron, but it is by default disabled afaik. So what I have scheduled for a long time in Cloudron is*/30 * * * * wget -q -O - https://wp.xxx.xxx/wp-cron.php?doing_wp_cron >/dev/null 2>&1 -
Is it related to a plugin? I know that by default wp-cron jobs were not always running in WP so I had to force create a cron job to run wp-cron on a schedule
It is supposed to be the reponsibility of WP Plugins to cleanup after them, by using the wp-cron, but it is by default disabled afaik. So what I have scheduled for a long time in Cloudron is*/30 * * * * wget -q -O - https://wp.xxx.xxx/wp-cron.php?doing_wp_cron >/dev/null 2>&1@SansGuidon Cloudron cron jobs works perfectly with Wordpress...
@archos Keep us posted
-
@SansGuidon Cloudron cron jobs works perfectly with Wordpress...
@archos Keep us posted
@p44 said in Docker volumes are filling up disk:
@SansGuidon Cloudron cron jobs works perfectly with Wordpress...
@archos Keep us posted
Glad it works for you. WP would constantly complaining those WP-cron jobs were disabled (see Cloudron docs, they mention wp-cron is disabled https://docs.cloudron.io/packages/wordpress-managed/ ), so I came with the fix I mention to get rid of the warnings/errors shown in my WP instance
maybe my solution is outdated yet it runs for so long now. -
@p44 said in Docker volumes are filling up disk:
@SansGuidon Cloudron cron jobs works perfectly with Wordpress...
@archos Keep us posted
Glad it works for you. WP would constantly complaining those WP-cron jobs were disabled (see Cloudron docs, they mention wp-cron is disabled https://docs.cloudron.io/packages/wordpress-managed/ ), so I came with the fix I mention to get rid of the warnings/errors shown in my WP instance
maybe my solution is outdated yet it runs for so long now.@SansGuidon Mentioned guide also say "To add custom cron events, use Cloudron's built-in cron or use a plugin like WP Crontrol." And it works like a sharm...
Before Cloudron I had a lot of problems publishing scheduled posts because WP Cron is activated only when user visits the website. Cloudron guide say "WordPress' built-in cron task schedule wp-cron is disabled since it is not effective for low traffic websites."
-
@SansGuidon Mentioned guide also say "To add custom cron events, use Cloudron's built-in cron or use a plugin like WP Crontrol." And it works like a sharm...
Before Cloudron I had a lot of problems publishing scheduled posts because WP Cron is activated only when user visits the website. Cloudron guide say "WordPress' built-in cron task schedule wp-cron is disabled since it is not effective for low traffic websites."
@p44 said in Docker volumes are filling up disk:
@SansGuidon Mentioned guide also say "To add custom cron events, use Cloudron's built-in cron or use a plugin like WP Crontrol." And it works like a sharm...
Before Cloudron I had a lot of problems publishing scheduled posts because WP Cron is activated only when user visits the website. Cloudron guide say "WordPress' built-in cron task schedule wp-cron is disabled since it is not effective for low traffic websites."
Interesting to know, however what I remember is that my site would appear non healthy without forcing some cron jobs to trigger, so I guess that's why I had to add this line in my cron tab, despite Cloudron is supposed to make that not necessary. Weird. Anyway if that works like a charm for everyone but me, I guess I might have different needs
-
@p44 said in Docker volumes are filling up disk:
@SansGuidon Mentioned guide also say "To add custom cron events, use Cloudron's built-in cron or use a plugin like WP Crontrol." And it works like a sharm...
Before Cloudron I had a lot of problems publishing scheduled posts because WP Cron is activated only when user visits the website. Cloudron guide say "WordPress' built-in cron task schedule wp-cron is disabled since it is not effective for low traffic websites."
Interesting to know, however what I remember is that my site would appear non healthy without forcing some cron jobs to trigger, so I guess that's why I had to add this line in my cron tab, despite Cloudron is supposed to make that not necessary. Weird. Anyway if that works like a charm for everyone but me, I guess I might have different needs
@SansGuidon It still does not work for you?
-
The cron job is working perfectly, temporary files are no longer accumulating. Many thanks to everyone for the advice.
-
The cron job is working perfectly, temporary files are no longer accumulating. Many thanks to everyone for the advice.
