Differences

This shows you the differences between two versions of the page.

--- omv7:omv7_plugins:docker_compose [2024/10/16 15:49] – [Create] chente
+++ omv7:omv7_plugins:docker_compose [2025/07/17 13:42] (current) – [Create] chente
@@ Line 639: / Line 639: @@
     * If you want to have several versioned backups over time, you must make a copy later with another specialized application for this purpose.
   * The containers that were running when the process started are started again. Those who were detained will continue to be detained.
+  * A copy of the global environment variables file will be added to the backup. This file will be located in the folder defined for the backup and is named ''global.env''
 The update task performs the following process:
   * Download the container images included in the compose file.
@@ Line 652: / Line 653: @@
 === Create ===
-{{ :omv6:omv6_plugins:compose9.jpg?direct&400|Schedule}}
+{{ :omv7:omv7_plugins:compose9.jpg?direct&400|Schedule}}
 Opens a dialog box to schedule container backup and/or update jobs.
@@ Line 661: / Line 662: @@
       * Filter can be a partial match with use of wildcard (*). e.g. asd* or *asd* or *asd.
       * You can add multiple filters separated by commas.
+    * File excludes: Files defined in this field will be excluded from the scheduled action to be performed. Multiple exclusions can be defined, separated by a comma.
   * **Action Type**
-    * Backup: If enabled, a backup task will be executed.
+    * Maintenance: It gives access to the maintenance options and they are the following:
-    * Update: If enabled, an update task will be executed for the selected containers. If the backup task is also checked, the backup will be performed first and then the update. Will recreate containers after update if running.
+      * Backup: If enabled, a backup task will be executed.
-    * Prune: If enabled, prune all dangling images. It does not use a filter, so all existing dangling images will be removed. Will run the ''docker image prune -f'' command.
+      * Update: If enabled, an update task will be executed for the selected containers. If the backup task is also checked, the backup will be performed first and then the update. Will recreate containers after update if running.
+      * Prune: If enabled, prune all dangling images. It does not use a filter, so all existing dangling images will be removed. Will run the ''docker image prune -f'' command.
+    * Container state: Provides access to functions to stop or start one or more containers on a scheduled basis.
+      * Start: Starts the execution of containers included in the compose files defined in the scheduled task.
+      * Stop: Stops the execution of containers included in the compose files defined in the scheduled task.
+  * **Scripts** (Only active if maintenance mode is selected)
     * Pre-backup script field: Allows you to set the path of a custom script that will be executed before the execution of the scheduled task.
     * Post-backup script field: Allows you to set the path of a custom script that will be executed after the execution of the scheduled task.
@@ Line 670: / Line 677: @@
     * Schedule the time of execution using the date and time options.
       * For example, the attached screenshot will backup all containers on Sundays at 8:36 AM. and will send an email with the result of the backup.
-    * Select if you want to receive an email with the output of the work, the header will show what you write in the Comment field.
+    * Send command output via email: Select if you want to receive an email with the output of the work.
+    * Verbose: Select whether you want the email output to be detailed.
+    * Comment: The header will show what you write in the Comment field.
 ----