Automatic Configuration from Git-Versioned .yml on Container Creation #2396

New issue

Closed

opened 2026-02-28 02:53:12 -05:00 by deekerman · 2 comments

deekerman commented

2026-02-28 02:53:12 -05:00

Owner

Originally created by @marco-carvalho on GitHub (Jul 19, 2023).

⚠️ Please verify that this feature request has NOT been suggested before.

I checked and didn't find similar feature request

🏷️ Feature Request Type

Other

🔖 Feature description

When deploying Uptime Kuma as a container, administrators often need to configure all monitors manually after the initial setup. This manual configuration can become quite tedious, especially when deploying multiple instances or recovering from backups. The ability to automatically read configurations from a .yml file upon container initialization would significantly streamline this process.

✔️ Solution

I'd like Uptime Kuma to have the ability to automatically read a .yml file located in the same folder as the container during its creation. This file should contain all the configurations for the monitors, including URLs, monitoring intervals, notification settings, etc. By doing so, when the container is initialized, Uptime Kuma should automatically set up the monitors as per the .yml file, eliminating the need for manual configuration.

Proposed format:

monitors:
  - name: "Monitor 1"
    url: "http://example1.com"
    interval: 5
    type: "http"
    ...
  - name: "Monitor 2"
    url: "http://example2.com"
    interval: 10
    type: "tcp"
    ...

❓ Alternatives

No response

📝 Additional Context

No response

Originally created by @marco-carvalho on GitHub (Jul 19, 2023). ### ⚠️ Please verify that this feature request has NOT been suggested before. - [X] I checked and didn't find similar feature request ### 🏷️ Feature Request Type Other ### 🔖 Feature description When deploying Uptime Kuma as a container, administrators often need to configure all monitors manually after the initial setup. This manual configuration can become quite tedious, especially when deploying multiple instances or recovering from backups. The ability to automatically read configurations from a `.yml` file upon container initialization would significantly streamline this process. ### ✔️ Solution I'd like Uptime Kuma to have the ability to automatically read a `.yml` file located in the same folder as the container during its creation. This file should contain all the configurations for the monitors, including URLs, monitoring intervals, notification settings, etc. By doing so, when the container is initialized, Uptime Kuma should automatically set up the monitors as per the `.yml` file, eliminating the need for manual configuration. **Proposed format**: ```yaml monitors: - name: "Monitor 1" url: "http://example1.com" interval: 5 type: "http" ... - name: "Monitor 2" url: "http://example2.com" interval: 10 type: "tcp" ... ``` ### ❓ Alternatives _No response_ ### 📝 Additional Context _No response_

deekerman

2026-02-28 02:53:12 -05:00

closed this issue
added the
feature-request
label

deekerman commented

2026-02-28 02:53:18 -05:00

Author

Owner

@chakflying commented on GitHub (Jul 20, 2023):

Configuration files have been discussed before (see #270, #1260 and #1354) and is unlikely to be implemented.

You can take a look at an alternative solution in #1260(comment).

@chakflying commented on GitHub (Jul 20, 2023): Configuration files have been discussed before (see #270, #1260 and #1354) and is unlikely to be implemented. You can take a look at an alternative solution in [#1260(comment)](https://github.com/louislam/uptime-kuma/issues/1260#issuecomment-1427660608).

deekerman commented

2026-02-28 02:53:20 -05:00

Author

Owner

@marco-carvalho commented on GitHub (Jul 20, 2023):

Thank you @chakflying

@marco-carvalho commented on GitHub (Jul 20, 2023): Thank you @chakflying