Add jsonschema

.devcontainer/README.md

@@ -0,0 +1,28 @@
+# Codespaces
+
+You can modifiy Uptime Kuma in your browser without setting up a local development.
+
+![image](https://github.com/louislam/uptime-kuma/assets/1336778/31d9f06d-dd0b-4405-8e0d-a96586ee4595)
+
+1. Click `Code` -> `Create codespace on master`
+2. Wait a few minutes until you see there are two exposed ports
+3. Go to the `3000` url, see if it is working
+
+![image](https://github.com/louislam/uptime-kuma/assets/1336778/909b2eb4-4c5e-44e4-ac26-6d20ed856e7f)
+
+## Frontend
+
+Since the frontend is using [Vite.js](https://vitejs.dev/), all changes in this area will be hot-reloaded.
+You don't need to restart the frontend, unless you try to add a new frontend dependency.
+
+## Backend
+
+The backend does not automatically hot-reload.
+You will need to restart the backend after changing something using these steps:
+
+1. Click `Terminal`
+2. Click `Codespaces: server-dev` in the right panel
+3. Press `Ctrl + C` to stop the server
+4. Press `Up` to run `npm run start-server-dev`
+
+![image](https://github.com/louislam/uptime-kuma/assets/1336778/e0c0a350-fe46-4588-9f37-e053c85834d1)

.devcontainer/devcontainer.json

@@ -0,0 +1,23 @@
+{
+    "image": "mcr.microsoft.com/devcontainers/javascript-node:dev-18-bookworm",
+    "features": {
+        "ghcr.io/devcontainers/features/github-cli:1": {}
+    },
+    "updateContentCommand": "npm ci",
+    "postCreateCommand": "",
+    "postAttachCommand": {
+        "frontend-dev": "npm run start-frontend-devcontainer",
+        "server-dev": "npm run start-server-dev",
+        "open-port": "gh codespace ports visibility 3001:public -c $CODESPACE_NAME"
+    },
+    "customizations": {
+        "vscode": {
+            "extensions": [
+				"streetsidesoftware.code-spell-checker",
+				"dbaeumer.vscode-eslint",
+				"GitHub.copilot-chat"
+			]
+        }
+    },
+    "forwardPorts": [3000, 3001]
+}

.dockerignore

@@ -1,6 +1,7 @@
 /.idea
 /node_modules
 /data*
+/cypress
 /out
 /test
 /kubernetes
@@ -17,6 +18,7 @@ README.md
 .vscode
 .eslint*
 .stylelint*
+/.devcontainer
 /.github
 yarn.lock
 app.json
@@ -28,16 +30,14 @@ SECURITY.md
 tsconfig.json
 .env
 /tmp
+/babel.config.js
 /ecosystem.config.js
 /extra/healthcheck.exe
 /extra/healthcheck
 /extra/exe-builder
+/extra/push-examples
 /extra/uptime-kuma-push
 
-# Comment the following line if you want to rebuild the healthcheck binary
-/extra/healthcheck-armv7
-
-
 ### .gitignore content (commented rules are duplicated)
 
 #node_modules

.eslintrc.js

@@ -1,5 +1,10 @@
 module.exports = {
-    ignorePatterns: ["test/*.js", "server/modules/*", "src/util.js"],
+    ignorePatterns: [
+        "test/*.js",
+        "test/cypress",
+        "server/modules/apicache/*",
+        "src/util.js"
+    ],
     root: true,
     env: {
         browser: true,
@@ -11,101 +16,153 @@ module.exports = {
         "eslint:recommended",
         "plugin:vue/vue3-recommended",
         "plugin:jsdoc/recommended-error",
-        "prettier", // Disables ESLint formatting rules that conflict with Prettier
     ],
     parser: "vue-eslint-parser",
     parserOptions: {
-        parser: "@typescript-eslint/parser",
+        parser: "@babel/eslint-parser",
         sourceType: "module",
         requireConfigFile: false,
     },
-    plugins: ["jsdoc", "@typescript-eslint"],
+    plugins: [
+        "jsdoc"
+    ],
     rules: {
-        yoda: "error",
+        "yoda": "error",
-        eqeqeq: ["warn", "smart"],
+        eqeqeq: [ "warn", "smart" ],
-        camelcase: [
+        "linebreak-style": [ "error", "unix" ],
-            "warn",
+        "camelcase": [ "warn", {
+            "properties": "never",
+            "ignoreImports": true
+        }],
+        "no-unused-vars": [ "warn", {
+            "args": "none"
+        }],
+        indent: [
+            "error",
+            4,
             {
-                properties: "never",
+                ignoredNodes: [ "TemplateLiteral" ],
-                ignoreImports: true,
+                SwitchCase: 1,
-            },
-        ],
-        "no-unused-vars": [
-            "warn",
-            {
-                args: "none",
             },
         ],
+        quotes: [ "error", "double" ],
+        semi: "error",
+        "vue/html-indent": [ "error", 4 ], // default: 2
         "vue/max-attributes-per-line": "off",
         "vue/singleline-html-element-content-newline": "off",
         "vue/html-self-closing": "off",
-        "vue/require-component-is": "off", // not allow is="style" https://github.com/vuejs/eslint-plugin-vue/issues/462#issuecomment-430234675
+        "vue/require-component-is": "off",      // not allow is="style" https://github.com/vuejs/eslint-plugin-vue/issues/462#issuecomment-430234675
-        "vue/attribute-hyphenation": "off", // This change noNL to "no-n-l" unexpectedly
+        "vue/attribute-hyphenation": "off",     // This change noNL to "no-n-l" unexpectedly
         "vue/multi-word-component-names": "off",
-        curly: "error",
+        "no-multi-spaces": [ "error", {
+            ignoreEOLComments: true,
+        }],
+        "array-bracket-spacing": [ "warn", "always", {
+            "singleValue": true,
+            "objectsInArrays": false,
+            "arraysInArrays": false
+        }],
+        "space-before-function-paren": [ "error", {
+            "anonymous": "always",
+            "named": "never",
+            "asyncArrow": "always"
+        }],
+        "curly": "error",
+        "object-curly-spacing": [ "error", "always" ],
+        "object-curly-newline": "off",
+        "object-property-newline": "error",
+        "comma-spacing": "error",
+        "brace-style": "error",
         "no-var": "error",
-        "no-throw-literal": "error",
+        "key-spacing": "warn",
-        "no-constant-condition": [
+        "keyword-spacing": "warn",
-            "error",
+        "space-infix-ops": "error",
-            {
+        "arrow-spacing": "warn",
-                checkLoops: false,
+        "no-trailing-spaces": "error",
-            },
+        "no-constant-condition": [ "error", {
-        ],
+            "checkLoops": false,
-        //"no-console": "warn",
+        }],
+        "space-before-blocks": "warn",
+        //'no-console': 'warn',
         "no-extra-boolean-cast": "off",
+        "no-multiple-empty-lines": [ "warn", {
+            "max": 1,
+            "maxBOF": 0,
+        }],
+        "lines-between-class-members": [ "warn", "always", {
+            exceptAfterSingleLine: true,
+        }],
         "no-unneeded-ternary": "error",
-        //"prefer-template": "error",
+        "array-bracket-newline": [ "error", "consistent" ],
-        "no-empty": [
+        "eol-last": [ "error", "always" ],
-            "error",
+        //'prefer-template': 'error',
-            {
+        "comma-dangle": [ "warn", "only-multiline" ],
-                allowEmptyCatch: true,
+        "no-empty": [ "error", {
-            },
+            "allowEmptyCatch": true
-        ],
+        }],
         "no-control-regex": "off",
-        "one-var": ["error", "never"],
+        "one-var": [ "error", "never" ],
-        "max-statements-per-line": ["error", { max: 1 }],
+        "max-statements-per-line": [ "error", { "max": 1 }],
         "jsdoc/check-tag-names": [
             "error",
             {
-                definedTags: ["link"],
+                "definedTags": [ "link" ]
-            },
+            }
         ],
         "jsdoc/no-undefined-types": "off",
-        "jsdoc/no-defaults": ["error", { noOptionalParamNames: true }],
+        "jsdoc/no-defaults": [
+            "error",
+            { "noOptionalParamNames": true }
+        ],
         "jsdoc/require-throws": "warn",
         "jsdoc/require-jsdoc": [
             "error",
             {
-                require: {
+                "require": {
-                    FunctionDeclaration: true,
+                    "FunctionDeclaration": true,
-                    MethodDefinition: true,
+                    "MethodDefinition": true,
-                },
+                }
-            },
+            }
         ],
         "jsdoc/no-blank-block-descriptions": "error",
         "jsdoc/require-returns-description": "warn",
-        "jsdoc/require-returns-check": ["error", { reportMissingReturnForUndefinedTypes: false }],
+        "jsdoc/require-returns-check": [
+            "error",
+            { "reportMissingReturnForUndefinedTypes": false }
+        ],
         "jsdoc/require-returns": [
             "warn",
             {
-                forceRequireReturn: true,
+                "forceRequireReturn": true,
-                forceReturnsWithAsync: true,
+                "forceReturnsWithAsync": true
-            },
+            }
         ],
         "jsdoc/require-param-type": "warn",
-        "jsdoc/require-param-description": "warn",
+        "jsdoc/require-param-description": "warn"
     },
-    overrides: [
+    "overrides": [
-        // Override for TypeScript
         {
-            files: ["**/*.ts"],
+            "files": [ "src/languages/*.js", "src/icon.js" ],
-            extends: ["plugin:@typescript-eslint/recommended"],
+            "rules": {
-            rules: {
+                "comma-dangle": [ "error", "always-multiline" ],
-                "jsdoc/require-returns-type": "off",
+            }
-                "jsdoc/require-param-type": "off",
-                "@typescript-eslint/no-explicit-any": "off",
-                "prefer-const": "off",
-            },
         },
-    ],
+
+        // Override for jest puppeteer
+        {
+            "files": [
+                "**/*.spec.js",
+                "**/*.spec.jsx"
+            ],
+            env: {
+                jest: true,
+            },
+            globals: {
+                page: true,
+                browser: true,
+                context: true,
+                jestPuppeteer: true,
+            },
+        }
+    ]
 };

.github/ISSUE_TEMPLATE/ask-for-help.yaml

@@ -0,0 +1,74 @@
+name: "❓ Ask for help"
+description: "Submit any question related to Uptime Kuma"
+#title: "[Help] "
+labels: [help]
+body:
+  - type: checkboxes
+    id: no-duplicate-issues
+    attributes:
+      label: "⚠️ Please verify that this bug has NOT been raised before."
+      description: "Search in the issues sections by clicking [HERE](https://github.com/louislam/uptime-kuma/issues?q=)"
+      options:
+        - label: "I checked and didn't find similar issue"
+          required: true
+  - type: checkboxes
+    attributes:
+      label: "🛡️ Security Policy"
+      description: Please review the security policy before reporting security related issues/bugs.
+      options:
+        - label: I agree to have read this project [Security Policy](https://github.com/louislam/uptime-kuma/security/policy)
+          required: true
+  - type: textarea
+    id: steps-to-reproduce
+    validations:
+      required: true
+    attributes:
+      label: "📝 Describe your problem"
+      description: "Please walk us through it step by step."
+      placeholder: "Describe what are you asking for..."
+  - type: textarea
+    id: error-msg
+    validations:
+      required: false
+    attributes:
+      label: "📝 Error Message(s) or Log"
+  - type: input
+    id: uptime-kuma-version
+    attributes:
+      label: "🐻 Uptime-Kuma Version"
+      description: "Which version of Uptime-Kuma are you running? Please do NOT provide the docker tag such as latest or 1"
+      placeholder: "Ex. 1.10.0"
+    validations:
+      required: true
+  - type: input
+    id: operating-system
+    attributes:
+      label: "💻 Operating System and Arch"
+      description: "Which OS is your server/device running on? (For Replit, please do not report this bug)"
+      placeholder: "Ex. Ubuntu 20.04 x86"
+    validations:
+      required: true
+  - type: input
+    id: browser-vendor
+    attributes:
+      label: "🌐 Browser"
+      description: "Which browser are you running on? (For Replit, please do not report this bug)"
+      placeholder: "Ex. Google Chrome 95.0.4638.69"
+    validations:
+      required: true
+  - type: input
+    id: docker-version
+    attributes:
+      label: "🐋 Docker Version"
+      description: "If running with Docker, which version are you running?"
+      placeholder: "Ex. Docker 20.10.9 / K8S / Podman"
+    validations:
+      required: false
+  - type: input
+    id: nodejs-version
+    attributes:
+      label: "🟩 NodeJS Version"
+      description: "If running with Node.js? which version are you running?"
+      placeholder: "Ex. 14.18.0"
+    validations:
+      required: false

.github/ISSUE_TEMPLATE/ask_for_help.yml

@@ -1,123 +0,0 @@
----
-name: ❓ Ask for help
-description: |
-  Submit any question related to Uptime Kuma
-#title: "[Help]"
-labels: ["help"]
-body:
-  - type: markdown
-    attributes:
-      value: |
-        🚫 **We kindly ask you to refrain from pinging maintainers unless absolutely necessary. Pings are reserved for critical/urgent issues that require immediate attention.**
-
-  - type: checkboxes
-    id: no-duplicate-question
-    attributes:
-      label: ⚠️ Please verify that your question has not already been reported
-      description: |
-        To avoid duplicate reports, please search for any existing issues before submitting a new one.
-        You can find the list of existing issues **[HERE](https://github.com/louislam/uptime-kuma/issues?q=is%3Aissue%20sort%3Acreated-desc%20)**.
-      options:
-        - label: |
-            I have searched the [existing issues](https://github.com/louislam/uptime-kuma/issues?q=is%3Aissue%20sort%3Acreated-desc%20) and found no similar reports.
-          required: true
-
-  - type: checkboxes
-    id: security-policy
-    attributes:
-      label: 🛡️ Security Policy
-      description: |
-        Please review and acknowledge the Security Policy before reporting any security-related issues or bugs.
-        You can find the full Security Policy **[HERE](https://github.com/louislam/uptime-kuma/security/policy)**.
-      options:
-        - label: |
-            I have read and agree to Uptime Kuma's [Security Policy](https://github.com/louislam/uptime-kuma/security/policy).
-          required: true
-
-  - type: textarea
-    id: steps-to-reproduce
-    validations:
-      required: true
-    attributes:
-      label: 📝 Describe your problem
-      description: |
-        Please walk us through it step by step.
-        Include all important details and add screenshots where appropriate.
-      placeholder: |
-        Describe what are you asking for ...
-
-  - type: textarea
-    id: error-msg
-    attributes:
-      label: 📝 Error Message(s) or Log
-      description: |
-        Please copy and paste any relevant log output.
-        This will be automatically formatted into code, so no need for backticks.
-      render: bash session
-    validations:
-      required: false
-
-  - type: input
-    id: uptime-kuma-version
-    attributes:
-      label: 🐻 Uptime-Kuma Version
-      description: |
-        What version of Uptime-Kuma are you running?
-        Please do not provide Docker tags like `latest` or `1`.
-      placeholder: |
-        e.g., 1.23.16 or 2.0.0-beta.2
-    validations:
-      required: true
-
-  - type: input
-    id: operating-system
-    attributes:
-      label: 💻 Operating System and Arch
-      description: |
-        Which OS is your server/device running on? (For Replit, please do not report this bug)
-      placeholder: |
-        e.g., Ubuntu Server 24.04.2 LTS (GNU/Linux 6.8.0-55-generic x86_64)
-    validations:
-      required: true
-
-  - type: input
-    id: browser-vendor
-    attributes:
-      label: 🌐 Browser
-      description: |
-        Which browser are you running on? (For Replit, please do not report this bug)
-      placeholder: |
-        e.g., Google Chrome 134.0.6998.183 (Official Build) (64-bit)
-    validations:
-      required: true
-
-  - type: textarea
-    id: deployment-info
-    attributes:
-      label: 🖥️ Deployment Environment
-      description: |
-        Provide details about the deployment environment, including runtime components, databases, and storage configurations. This will
-        help assess the infrastructure and identify any potential compatibility requirements.
-
-        **Remove any fields that do not apply to your setup.**
-      value: |
-        - **Runtime Environment**:
-          - Docker: Version `X.X.X` (Build `Y.Y.Y`)
-          - Docker Compose: Version `X.X.X`
-          - Portainer (BE/CE): Version `X.X.X` (LTS: Yes/No)
-          - MariaDB: Version `X.X.X` (LTS: Yes/No)
-          - Node.js: Version `X.X.X` (LTS: Yes/No)
-          - Kubernetes (K3S/K8S): Version `X.X.X` (LTS: Yes/No, via `[method/tool]`)
-        - **Database**:
-          - SQLite: Embedded
-          - MariaDB: Embedded/External
-        - **Database Storage**:
-          - **Filesystem**:
-            - Linux: ext4/XFS/Btrfs/ZFS/F2FS
-            - macOS: APFS/ HFS+
-            - Windows: NTFS/ReFS
-          - **Storage Medium**: HDD/eMMC/SSD/NVMe
-        - **Uptime Kuma Setup**:
-          - Number of monitors: `X`
-    validations:
-      required: true

.github/ISSUE_TEMPLATE/bug_report.yaml

@@ -0,0 +1,99 @@
+name: "🐛 Bug Report"
+description: "Submit a bug report to help us improve"
+#title: "[Bug] "
+labels: [bug]
+body:
+  - type: checkboxes
+    id: no-duplicate-issues
+    attributes:
+      label: "⚠️ Please verify that this bug has NOT been raised before."
+      description: "Search in the issues sections by clicking [HERE](https://github.com/louislam/uptime-kuma/issues?q=)"
+      options:
+        - label: "I checked and didn't find similar issue"
+          required: true
+  - type: checkboxes
+    attributes:
+      label: "🛡️ Security Policy"
+      description: Please review the security policy before reporting security related issues/bugs.
+      options:
+        - label: I agree to have read this project [Security Policy](https://github.com/louislam/uptime-kuma/security/policy)
+          required: true
+  - type: textarea
+    id: description
+    validations:
+      required: false
+    attributes:
+      label: "Description"
+      description: "You could also upload screenshots"
+  - type: textarea
+    id: steps-to-reproduce
+    validations:
+      required: true
+    attributes:
+      label: "👟 Reproduction steps"
+      description: "How do you trigger this bug? Please walk us through it step by step."
+      placeholder: "..."
+  - type: textarea
+    id: expected-behavior
+    validations:
+      required: true
+    attributes:
+      label: "👀 Expected behavior"
+      description: "What did you think would happen?"
+      placeholder: "..."
+  - type: textarea
+    id: actual-behavior
+    validations:
+      required: true
+    attributes:
+      label: "😓 Actual Behavior"
+      description: "What actually happen?"
+      placeholder: "..."
+  - type: input
+    id: uptime-kuma-version
+    attributes:
+      label: "🐻 Uptime-Kuma Version"
+      description: "Which version of Uptime-Kuma are you running? Please do NOT provide the docker tag such as latest or 1"
+      placeholder: "Ex. 1.10.0"
+    validations:
+      required: true
+  - type: input
+    id: operating-system
+    attributes:
+      label: "💻 Operating System and Arch"
+      description: "Which OS is your server/device running on? (For Replit, please do not report this bug)"
+      placeholder: "Ex. Ubuntu 20.04 x64 "
+    validations:
+      required: true
+  - type: input
+    id: browser-vendor
+    attributes:
+      label: "🌐 Browser"
+      description: "Which browser are you running on?"
+      placeholder: "Ex. Google Chrome 95.0.4638.69"
+    validations:
+      required: true
+  - type: input
+    id: docker-version
+    attributes:
+      label: "🐋 Docker Version"
+      description: "If running with Docker, which version are you running?"
+      placeholder: "Ex. Docker 20.10.9 / K8S / Podman"
+    validations:
+      required: false
+  - type: input
+    id: nodejs-version
+    attributes:
+      label: "🟩 NodeJS Version"
+      description: "If running with Node.js? which version are you running?"
+      placeholder: "Ex. 14.18.0"
+    validations:
+      required: false
+  - type: textarea
+    id: logs
+    attributes:
+      label: "📝 Relevant log output"
+      description: Please copy and paste any relevant log output. This will be automatically formatted into code, so no need for backticks.
+      render: shell
+    validations:
+      required: false

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -1,152 +0,0 @@
----
-name: 🐛 Bug Report
-description: |
-  Submit a bug report to help us improve
-#title: "[Bug]"
-labels: ["bug"]
-body:
-  - type: markdown
-    attributes:
-      value: |
-        🚫 **We kindly ask you to refrain from pinging maintainers unless absolutely necessary. Pings are reserved for critical/urgent issues that require immediate attention.**
-
-  - type: textarea
-    id: related-issues
-    validations:
-      required: true
-    attributes:
-      label: 📑 I have found these related issues/pull requests
-      description: |
-        Please search for related **[ISSUES](https://github.com/louislam/uptime-kuma/issues?q=is%3Aissue%20sort%3Acreated-desc)**
-        and **[PULL REQUESTS](https://github.com/louislam/uptime-kuma/pulls?q=is%3Apr+sort%3Acreated-desc+)**.
-        Explain the differences between them or clarify if you were unable to find any related issues/pull requests.
-      placeholder: |
-        Example: This relates to issue #1, which also affects the ... system. It should not be merged because ...
-
-  - type: checkboxes
-    id: security-policy
-    attributes:
-      label: 🛡️ Security Policy
-      description: |
-        Please review and acknowledge the Security Policy before reporting any security-related issues or bugs. You can find the full Security Policy **[HERE](https://github.com/louislam/uptime-kuma/security/policy)**.
-      options:
-        - label: |
-            I have read and agree to Uptime Kuma's [Security Policy](https://github.com/louislam/uptime-kuma/security/policy).
-          required: true
-
-  - type: textarea
-    id: description
-    validations:
-      required: false
-    attributes:
-      label: 📝 Description
-      description: |
-        You could also upload screenshots
-
-  - type: textarea
-    id: steps-to-reproduce
-    validations:
-      required: true
-    attributes:
-      label: 👟 Reproduction steps
-      description: |
-        How do you trigger this bug? Please walk us through it step by step. Include all important details and add screenshots where appropriate
-      placeholder: |
-        ...
-
-  - type: textarea
-    id: expected-behavior
-    validations:
-      required: true
-    attributes:
-      label: 👀 Expected behavior
-      description: |
-        What did you think would happen?
-      placeholder: |
-        ...
-
-  - type: textarea
-    id: actual-behavior
-    validations:
-      required: true
-    attributes:
-      label: 😓 Actual Behavior
-      description: |
-        What actually happen?
-      placeholder: |
-        ...
-
-  - type: input
-    id: uptime-kuma-version
-    attributes:
-      label: 🐻 Uptime-Kuma Version
-      description: |
-        What version of Uptime-Kuma are you running? Please do not provide Docker tags like `latest` or `1`.
-      placeholder: |
-        e.g., 1.23.16 or 2.0.0-beta.2
-    validations:
-      required: true
-
-  - type: input
-    id: operating-system
-    attributes:
-      label: 💻 Operating System and Arch
-      description: |
-        Which OS is your server/device running on? (For Replit, please do not
-        report this bug)
-      placeholder: |
-        e.g., Ubuntu Server 24.04.2 LTS (GNU/Linux 6.8.0-55-generic x86_64)
-    validations:
-      required: true
-
-  - type: input
-    id: browser-vendor
-    attributes:
-      label: 🌐 Browser
-      description: |
-        Which browser are you running on?
-      placeholder: |
-        e.g., Google Chrome 134.0.6998.183 (Official Build) (64-bit)
-    validations:
-      required: true
-
-  - type: textarea
-    id: deployment-info
-    attributes:
-      label: 🖥️ Deployment Environment
-      description: |
-        Provide details about the deployment environment, including runtime components, databases, and storage configurations. This will
-        help assess the infrastructure and identify any potential compatibility requirements.
-
-        **Remove any fields that do not apply to your setup.**
-      value: |
-        - **Runtime Environment**:
-          - Docker: Version `X.X.X` (Build `Y.Y.Y`)
-          - Docker Compose: Version `X.X.X`
-          - Portainer (BE/CE): Version `X.X.X` (LTS: Yes/No)
-          - MariaDB: Version `X.X.X` (LTS: Yes/No)
-          - Node.js: Version `X.X.X` (LTS: Yes/No)
-          - Kubernetes (K3S/K8S): Version `X.X.X` (LTS: Yes/No, via `[method/tool]`)
-        - **Database**:
-          - SQLite: Embedded
-          - MariaDB: Embedded/External
-        - **Database Storage**:
-          - **Filesystem**:
-            - Linux: ext4/XFS/Btrfs/ZFS/F2FS
-            - macOS: APFS/ HFS+
-            - Windows: NTFS/ReFS
-          - **Storage Medium**: HDD/eMMC/SSD/NVMe
-        - **Uptime Kuma Setup**:
-          - Number of monitors: `X`
-    validations:
-      required: true
-
-  - type: textarea
-    id: logs
-    attributes:
-      label: 📝 Relevant log output
-      description: |
-        Please copy and paste any relevant log output. This will be automatically formatted into code, so no need for backticks.
-      render: bash session
-    validations:
-      required: false

.github/ISSUE_TEMPLATE/config.yml

@@ -1,2 +0,0 @@
----
-blank_issues_enabled: false

.github/ISSUE_TEMPLATE/feature_request.yaml

@@ -0,0 +1,59 @@
+name: 🚀 Feature Request
+description: "Submit a proposal for a new feature"
+#title: "[Feature] "
+labels: [feature-request]
+body:
+  - type: checkboxes
+    id: no-duplicate-issues
+    attributes:
+      label: "⚠️ Please verify that this feature request has NOT been suggested before."
+      description: "Search in the issues sections by clicking [HERE](https://github.com/louislam/uptime-kuma/issues?q=)"
+      options:
+        - label: "I checked and didn't find similar feature request"
+          required: true
+  - type: dropdown
+    id: feature-area
+    attributes:
+      label: "🏷️ Feature Request Type"
+      description: "What kind of feature request is this?"
+      multiple: true
+      options:
+        - API
+        - New Notification
+        - New Monitor
+        - UI Feature
+        - Other
+    validations:
+      required: true
+  - type: textarea
+    id: feature-description
+    validations:
+      required: true
+    attributes:
+      label: "🔖 Feature description"
+      description: "A clear and concise description of what the feature request is."
+      placeholder: "You should add ..."
+  - type: textarea
+    id: solution
+    validations:
+      required: true
+    attributes:
+      label: "✔️ Solution"
+      description: "A clear and concise description of what you want to happen."
+      placeholder: "In my use-case, ..."
+  - type: textarea
+    id: alternatives
+    validations:
+      required: false
+    attributes:
+      label: "❓ Alternatives"
+      description: "A clear and concise description of any alternative solutions or features you've considered."
+      placeholder: "I have considered ..."
+  - type: textarea
+    id: additional-context
+    validations:
+      required: false
+    attributes:
+      label: "📝 Additional Context"
+      description: "Add any other context or screenshots about the feature request here."
+      placeholder: "..."

.github/ISSUE_TEMPLATE/feature_request.yml

@@ -1,70 +0,0 @@
----
-name: 🚀 Feature Request
-description: |
-  Submit a proposal for a new feature
-# title: "[Feature]"
-labels: ["feature-request"]
-body:
-  - type: markdown
-    attributes:
-      value: |
-        ### 🚫 Please Avoid Unnecessary Pinging of Maintainers
-
-        We kindly ask you to refrain from pinging maintainers unless absolutely necessary.
-        Pings are for critical/urgent pull requests that require immediate attention.
-  - type: textarea
-    id: related-issues
-    validations:
-      required: true
-    attributes:
-      label: 📑 I have found these related issues/pull requests
-      description: |
-        Please search for related **[ISSUES](https://github.com/louislam/uptime-kuma/issues?q=is%3Aissue%20sort%3Acreated-desc)**
-        and **[PULL REQUESTS](https://github.com/louislam/uptime-kuma/pulls?q=is%3Apr+sort%3Acreated-desc+)**.
-        Explain the differences between them or clarify if you were unable to find any related issues/pull requests.
-      placeholder: |
-        Example: This relates to issue #1, which also affects the ... system. It should not be merged because ...
-
-  - type: textarea
-    id: feature-description
-    validations:
-      required: true
-    attributes:
-      label: 🔖 Feature description
-      description: |
-        A clear and concise description of what the feature request is.
-      placeholder: |
-        You should add ...
-
-  - type: textarea
-    id: solution
-    validations:
-      required: true
-    attributes:
-      label: ✔️ Solution
-      description: |
-        A clear and concise description of what you want to happen.
-      placeholder: |
-        In my use-case, ...
-
-  - type: textarea
-    id: alternatives
-    validations:
-      required: false
-    attributes:
-      label: ❓ Alternatives
-      description: |
-        A clear and concise description of any alternative solutions or features you've considered.
-      placeholder: |
-        I have considered ...
-
-  - type: textarea
-    id: additional-context
-    validations:
-      required: false
-    attributes:
-      label: 📝 Additional Context
-      description: |
-        Add any other context or screenshots about the feature request here.
-      placeholder: |
-        ...

.github/ISSUE_TEMPLATE/security.md

@@ -0,0 +1,17 @@
+---
+
+name: "Security Issue"
+about: "Just for alerting @louislam, do not provide any details here"
+title: "Security Issue"
+ref: "main"
+labels:
+
+- security
+
+---
+
+DO NOT PROVIDE ANY DETAILS HERE. Please privately report to https://github.com/louislam/uptime-kuma/security/advisories/new.
+
+Why need this issue? It is because GitHub Advisory do not send a notification to @louislam, it is a workaround to do so.
+
+Your GitHub Advisory URL:

.github/ISSUE_TEMPLATE/security_issue.yml

@@ -1,54 +0,0 @@
----
-name: 🛡️ Security Issue
-description: |
-  Notify Louis Lam about a security concern. Please do NOT include any sensitive details in this issue.
-# title: "Security Issue"
-labels: ["security"]
-assignees: [louislam]
-body:
-  - type: markdown
-    attributes:
-      value: |
-        ## ❗ IMPORTANT: DO NOT SHARE VULNERABILITY DETAILS HERE
-
-        ## Please do not open issues for upstream dependency scan results.
-
-        Automated security tools often report false-positive issues that are not exploitable in the context of Uptime Kuma.
-        Reviewing these without concrete impact does not scale for us.
-
-        If you can demonstrate that an upstream issue is actually exploitable in Uptime Kuma (e.g. with a PoC or reproducible steps), we’re happy to take a look.
-
-        ### ⚠️ Report a Security Vulnerability
-
-        **If you have discovered a security vulnerability, please report it securely using the GitHub Security Advisory.**
-
-        **Note**: This issue is only for notifying the maintainers of the repository, as the GitHub Security Advisory does not automatically send notifications.
-
-        - **Confidentiality**: The information you provide in the GitHub Security Advisory will initially remain confidential. However, once the vulnerability is addressed, the advisory will be publicly disclosed on GitHub.
-        - **Access and Visibility**: Until the advisory is published, it will only be visible to the maintainers of the repository and invited collaborators.
-        - **Credit**: You will be automatically credited as a contributor for identifying and reporting the vulnerability. Your contribution will be reflected in the MITRE Credit System.
-        - **Important Reminder**: **Do not include any sensitive or detailed vulnerability information in this issue.** This issue is only for sharing the advisory URL to notify the maintainers of the repository, not for discussing the vulnerability itself.
-
-        **Thank you for helping us keep Uptime Kuma secure!**
-
-        ## **Step 1: Submit a GitHub Security Advisory**
-
-        Right-click the link below and select `Open link in new tab` to access the page.
-        This will keep the security issue open, allowing you to easily return and paste the Advisory URL here later.
-
-        ➡️ [Create a New Security Advisory](https://github.com/louislam/uptime-kuma/security/advisories/new)
-
-        ## **Step 2: Share the Advisory URL**
-
-        Once you've created your advisory, please share the URL below.
-        This will notify Louis Lam and enable them to take the appropriate action.
-
-  - type: textarea
-    id: github-advisory-url
-    validations:
-      required: true
-    attributes:
-      label: GitHub Advisory URL for @louislam
-      placeholder: |
-        Please paste the GitHub Advisory URL here. Only the URL is required.
-        Example: https://github.com/louislam/uptime-kuma/security/advisories/GHSA-8h5r-7t6l-q3kz

.github/PULL_REQUEST_TEMPLATE.md

@@ -1,45 +1,34 @@
-# Summary
+⚠️⚠️⚠️ Since we do not accept all types of pull requests and do not want to waste your time. Please be sure that you have read pull request rules:
+https://github.com/louislam/uptime-kuma/blob/master/CONTRIBUTING.md#can-i-create-a-pull-request-for-uptime-kuma
 
-In this pull request, the following changes are made:
+Tick the checkbox if you understand [x]:
+- [ ] I have read and understand the pull request rules.
 
-- Foobar was changed to FooFoo, because ...
+# Description
 
-<!--Please link any GitHub issues or tasks that this pull request addresses-->
+Fixes #(issue)
 
-- Relates to #issue-number <!--this links related the issue-->
+## Type of change
-- Resolves #issue-number <!--this auto-closes the issue-->
 
-<details>
+Please delete any options that are not relevant.
-<summary>Please follow this checklist to avoid unnecessary back and forth (click to expand)</summary>
 
-- [ ] ⚠️ If there are Breaking change (a fix or feature that alters existing functionality in a way that could cause issues) I have called them out
+- Bug fix (non-breaking change which fixes an issue)
-- [ ] 🧠 I have disclosed any use of LLMs/AI in this contribution and reviewed all generated content.
+- User interface (UI)
-      I understand that I am responsible for and able to explain every line of code I submit.
+- New feature (non-breaking change which adds functionality)
-- [ ] 🔍 Any UI changes adhere to visual style of this project.
+- Breaking change (fix or feature that would cause existing functionality to not work as expected)
-- [ ] 🛠️ I have self-reviewed and self-tested my code to ensure it works as expected.
+- Other
-- [ ] 📝 I have commented my code, especially in hard-to-understand areas (e.g., using JSDoc for methods).
+- This change requires a documentation update
-- [ ] 🤖 I added or updated automated tests where appropriate.
-- [ ] 📄 Documentation updates are included (if applicable).
-- [ ] 🧰 Dependency updates are listed and explained.
-- [ ] ⚠️ CI passes and is green.
 
-</details>
+## Checklist
 
-## Screenshots for Visual Changes
+- [ ] My code follows the style guidelines of this project
+- [ ] I ran ESLint and other linters for modified files
+- [ ] I have performed a self-review of my own code and tested it
+- [ ] I have commented my code, particularly in hard-to-understand areas
+  (including JSDoc for methods)
+- [ ] My changes generate no new warnings
+- [ ] My code needed automated testing. I have added them (this is optional task)
 
-<!--
+## Screenshots (if any)
-If this pull request introduces visual changes, please provide the following details.
-If not, remove this section.
 
-Please upload the image directly here by pasting it or dragging and dropping.
+Please do not use any external image service. Instead, just paste in or drag and drop the image here, and it will be uploaded automatically.
--->
-
-- **UI Modifications**: Highlight any changes made to the user interface.
-- **Before & After**: Include screenshots or comparisons (if applicable).
-
-| Event              | Before                | After                |
-| ------------------ | --------------------- | -------------------- |
-| `UP`               | ![Before](image-link) | ![After](image-link) |
-| `DOWN`             | ![Before](image-link) | ![After](image-link) |
-| Certificate-expiry | ![Before](image-link) | ![After](image-link) |
-| Testing            | ![Before](image-link) | ![After](image-link) |

.github/REVIEW_GUIDELINES.md

@@ -1,224 +0,0 @@
-# Uptime Kuma Review Guidelines
-
-> [!NOTE]
-> These review guidelines are a work in progress, and are frequently
-> updated and improved, so please check back frequently for the latest version.
-
-## Preparing for a PR Review
-
-### Read the PR description carefully
-
-Make sure you understand what the PR is trying to solve or implement. This could
-be a bug fix, a new feature, or a refactor.
-
-### Check the linked issues
-
-If the PR has a linked issue, read it to better understand the context and the
-reason for the change.
-
-### Check the test coverage
-
-Make sure relevant tests have been added or modified. If the PR adds new
-functionality, there should be tests covering the change.
-
-## General Review
-
-### Code formatting and style
-
-Check if the code adheres to the style guidelines of the project. Make sure
-there are no unused imports, variables, `console.log` for debugging in the PR.
-
-- [Project Style](../CONTRIBUTING.md#project-styles)
-- [Coding Style](../CONTRIBUTING.md#coding-styles)
-
-### Readability and maintainability
-
-Is the code easy to understand for other developers? Make sure complex parts are
-explained with comments about **_why_** something is done, and use clear names
-to show **_how_**. Are variables and functions well-named, and is there a
-consistent naming style? Also, check if the code is maintainable:
-
-- Is it unnecessarily complex? Could it be simplified?
-- Does it follow the **[Single Responsibility Principle (SRP)]**?
-
-[Single Responsibility Principle (SRP)]: https://www.geeksforgeeks.org/single-responsibility-in-solid-design-principle/
-
-### Documentation
-
-Is the PR well documented? Check if the descriptions of functions, parameters,
-and return values are present. Are there any changes needed to the README or
-other documentation, for example, if new features or configurations are
-introduced?
-
-## Functional Review
-
-### Testing
-
-Ensure that the new code is properly tested. This includes unit tests,
-integration tests, and if necessary, end-to-end tests.
-
-### Test results
-
-Did all tests pass in the CI pipeline (e.g., GitHub Actions, Travis, CircleCI)?
-
-### Testing in different environments
-
-If the changes depend on certain environments or configurations, verify that the
-code has been tested in various environments (e.g., local development, staging,
-production).
-
-- [How to test Pull Requests](https://github.com/louislam/uptime-kuma/wiki/Test-Pull-Requests)
-
-### Edge cases and regressions
-
-- Are there test cases for possible edge cases?
-- Could this change introduce regressions in other parts of the system?
-
-## Security
-
-### Security issues
-
-Check for potential security problems, such as SQL injection, XSS attacks, or
-unsafe API calls. Are there passwords, tokens, or other sensitive data left in
-the code by mistake?
-
-### Authentication and authorization
-
-Is access to sensitive data or functionality properly secured? Check that the
-correct authorization and authentication mechanisms are in place.
-
-### Security Best Practices
-
-- Ensure that the code is free from common vulnerabilities like **SQL
-  injection**, **XSS attacks**, and **insecure API calls**.
-- Check for proper encryption of sensitive data, and ensure that **passwords**
-  or **API tokens** are not hardcoded in the code.
-
-## Performance
-
-### Performance impact
-
-Check if the changes negatively impact performance. This can include factors
-like load times, memory usage, or other performance aspects.
-
-### Use of external libraries
-
-- Have the right libraries been chosen?
-- Are there unnecessary dependencies that might reduce performance or increase
-  code complexity?
-- Are these dependencies actively maintained and free of known vulnerabilities?
-
-### Performance Best Practices
-
-- **Measure performance** using tools like Lighthouse or profiling libraries.
-- **Avoid unnecessary dependencies** that may bloat the codebase.
-- Ensure that the **code does not degrade the user experience** (e.g., by
-  increasing load times or memory consumption).
-
-## Compliance and Integration
-
-### Alignment with the project
-
-Are the changes consistent with the project goals and requirements? Ensure the
-PR aligns with the architecture and design principles of the project.
-
-### Integration
-
-If the PR depends on other PRs or changes, verify that they integrate well with
-the rest of the project. Ensure the code does not cause conflicts with other
-active PRs.
-
-### Backward compatibility
-
-Does the change break compatibility with older versions of the software or
-dependencies? If so, is there a migration plan in place?
-
-## Logging and Error Handling
-
-### Proper error handling
-
-- Are errors properly caught and handled instead of being silently ignored?
-- Are exceptions used appropriately?
-
-### Logging
-
-- Is sufficient logging included for debugging and monitoring?
-- Is there excessive logging that could affect performance?
-
-## Accessibility (for UI-related changes)
-
-If the PR affects the user interface, ensure that it meets accessibility
-standards:
-
-- Can users navigate using only the keyboard?
-- Are screen readers supported?
-- Is there proper color contrast for readability?
-- Are there **WCAG** (Web Content Accessibility Guidelines) compliance issues?
-- Use tools like **Axe** or **Lighthouse** to evaluate accessibility.
-
-## Providing Feedback
-
-### Constructive feedback
-
-Provide clear, constructive feedback on what is good and what can be improved.
-If improvements are needed, be specific about what should change.
-
-### Clarity and collaboration
-
-Ensure your feedback is friendly and open, so the team member who submitted the
-PR feels supported and motivated to make improvements.
-
-<details><summary><b>For Maintainers only</b> (click to expand)</summary>
-<p>
-
-## Go/No-Go Decision
-
-### Go
-
-If the code has no issues and meets the project requirements, approve it (and
-possibly merge it).
-
-### No-Go
-
-If there are significant issues, such as missing tests, security
-vulnerabilities, or performance problems, request the necessary changes before
-the PR can be approved. Some examples of **significant issues** include:
-
-- Missing tests for new functionality.
-- Identified **security vulnerabilities**.
-- Code changes that break **backward compatibility** without a proper migration
-  plan.
-- Code that causes **major performance regressions** (e.g., high CPU/memory
-  usage).
-
-## After the Review
-
-### Reordering and merging
-
-Once the necessary changes have been made and the PR is approved, the code can
-be merged into the main branch (e.g., `main` or `master`).
-
-### Testing after merging
-
-Ensure that the build passes after merging the PR, and re-test the functionality
-in the production environment if necessary.
-
-## Follow-up
-
-### Communication with team members
-
-If the PR has long-term technical or functional implications, communicate the
-changes to the team.
-
-### Monitoring
-
-Continue monitoring the production environment for any unexpected issues that
-may arise after the code has been merged.
-
-</p>
-</details>
-
----
-
-This process ensures that PRs are systematically and thoroughly reviewed,
-improving overall code quality.

.github/copilot-instructions.md

@@ -1,176 +0,0 @@
-# Copilot Instructions for Uptime Kuma
-
-## Copilot's Goals/Tasks
-
-- Check spelling
-- Do not show "Pull Request Overview"
-- You do not have to reply if there are no issues
-
-## Repository Overview
-
-**Uptime Kuma** is a self-hosted monitoring tool for HTTP(s), TCP, DNS, Docker, etc. Built with Vue 3 (frontend) and Node.js/Express (backend), using Socket.IO for real-time communication.
-
-- **Languages**: JavaScript, Vue 3, TypeScript (limited), HTML, CSS/SCSS
-- **Backend**: Node.js >= 20.4, Express.js, Socket.IO, SQLite
-- **Frontend**: Vue 3, Vite, Bootstrap 5, Chart.js
-- **Package Manager**: npm with `legacy-peer-deps=true` (.npmrc)
-
-## Build & Validation Commands
-
-### Prerequisites
-
-- Node.js >= 20.4.0, npm >= 9.3, Git
-
-### Essential Command Sequence
-
-1. **Install Dependencies**:
-
-   ```bash
-   npm ci  # Use npm ci NOT npm install (~60-90 seconds)
-   ```
-
-2. **Linting** (required before committing):
-
-   ```bash
-   npm run lint         # Both linters (~15-30 seconds)
-   npm run lint:prod    # For production (zero warnings)
-   ```
-
-3. **Build Frontend**:
-
-   ```bash
-   npm run build  # Takes ~90-120 seconds, builds to dist/
-   ```
-
-4. **Run Tests**:
-   ```bash
-   npm run test-backend  # Backend tests (~50-60 seconds)
-   npm test              # All tests
-   ```
-
-### Development Workflow
-
-```bash
-npm run dev  # Starts frontend (port 3000) and backend (port 3001)
-```
-
-## Project Architecture
-
-### Directory Structure
-
-```
-/
-├── server/              Backend source code
-│   ├── model/          Database models (auto-mapped to tables)
-│   ├── monitor-types/  Monitor type implementations
-│   ├── notification-providers/  Notification integrations
-│   ├── routers/        Express routers
-│   ├── socket-handlers/  Socket.IO event handlers
-│   ├── server.js       Server entry point
-│   └── uptime-kuma-server.js  Main server logic
-├── src/                Frontend source code (Vue 3 SPA)
-│   ├── components/     Vue components
-│   ├── pages/          Page components
-│   ├── lang/          i18n translations
-│   ├── router.js      Vue Router configuration
-│   └── main.js        Frontend entry point
-├── db/                 Database related
-│   ├── knex_migrations/  Knex migration files
-│   └── kuma.db        SQLite database (gitignored)
-├── test/               Test files
-│   ├── backend-test/  Backend unit tests
-│   └── e2e/           Playwright E2E tests
-├── config/             Build configuration
-│   ├── vite.config.js    Vite build config
-│   └── playwright.config.js  Playwright test config
-├── dist/               Frontend build output (gitignored)
-├── data/               App data directory (gitignored)
-├── public/             Static frontend assets (dev only)
-├── docker/             Docker build files
-└── extra/              Utility scripts
-```
-
-### Key Configuration Files
-
-- **package.json**: Scripts, dependencies, Node.js version requirement
-- **.eslintrc.js**: ESLint rules (4 spaces, double quotes, unix line endings, JSDoc required)
-- **.stylelintrc**: Stylelint rules (4 spaces indentation)
-- **.editorconfig**: Editor settings (4 spaces, LF, UTF-8)
-- **tsconfig-backend.json**: TypeScript config for backend (only src/util.ts)
-- **.npmrc**: `legacy-peer-deps=true` (required for dependency resolution)
-- **.gitignore**: Excludes node_modules, dist, data, tmp, private
-
-### Code Style (strictly enforced by linters)
-
-- 4 spaces indentation, double quotes, Unix line endings (LF), semicolons required
-- **Naming**: JavaScript/TypeScript (camelCase), SQLite (snake_case), CSS/SCSS (kebab-case)
-- JSDoc required for all functions/methods
-
-## CI/CD Workflows
-
-**auto-test.yml** (runs on PR/push to master/1.23.X):
-
-- Linting, building, backend tests on multiple OS/Node versions (15 min timeout)
-- E2E Playwright tests
-
-**validate.yml**: Validates JSON/YAML files, language files, knex migrations
-
-**PR Requirements**: All linters pass, tests pass, code follows style guidelines
-
-## Common Issues
-
-1. **npm install vs npm ci**: Always use `npm ci` for reproducible builds
-2. **TypeScript errors**: `npm run tsc` shows 1400+ errors - ignore them, they don't affect builds
-3. **Stylelint warnings**: Deprecation warnings are expected, ignore them
-4. **Test failures**: Always run `npm run build` before running tests
-5. **Port conflicts**: Dev server uses ports 3000 and 3001
-6. **First run**: Server shows "db-config.json not found" - this is expected, starts setup wizard
-
-## Translations
-
-- Managed via Weblate. Add keys to `src/lang/en.json` only
-- Don't include other languages in PRs
-- Use `$t("key")` in Vue templates
-
-## Database
-
-- Primary: SQLite (also supports MariaDB/MySQL)
-- Migrations in `db/knex_migrations/` using Knex.js
-- Filename format validated by CI: `node ./extra/check-knex-filenames.mjs`
-
-## Testing
-
-- **Backend**: Node.js test runner, fast unit tests
-- **E2E**: Playwright (requires `npx playwright install` first time)
-- Test data in `data/playwright-test`
-
-## Adding New Features
-
-### New Notification Provider
-
-Files to modify:
-
-1. `server/notification-providers/PROVIDER_NAME.js` (backend logic)
-2. `server/notification.js` (register provider)
-3. `src/components/notifications/PROVIDER_NAME.vue` (frontend UI)
-4. `src/components/notifications/index.js` (register frontend)
-5. `src/components/NotificationDialog.vue` (add to list)
-6. `src/lang/en.json` (add translation keys)
-
-### New Monitor Type
-
-Files to modify:
-
-1. `server/monitor-types/MONITORING_TYPE.js` (backend logic)
-2. `server/uptime-kuma-server.js` (register monitor type)
-3. `src/pages/EditMonitor.vue` (frontend UI)
-4. `src/lang/en.json` (add translation keys)
-
-## Important Notes
-
-1. **Trust these instructions** - based on testing. Search only if incomplete/incorrect
-2. **Dependencies**: 5 known vulnerabilities (3 moderate, 2 high) - acknowledged, don't fix without discussion
-3. **Git Branches**: `master` (v2 development), `1.23.X` (v1 maintenance)
-4. **Node Version**: >= 20.4.0 required
-5. **Socket.IO**: Most backend logic in `server/socket-handlers/`, not REST
-6. **Never commit**: `data/`, `dist/`, `tmp/`, `private/`, `node_modules/`

.github/dependabot.yml

@@ -1,22 +0,0 @@
-# Dependabot configuration for Uptime Kuma
-# See: https://docs.github.com/en/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file
-
-version: 2
-updates:
-  # Enable version updates for GitHub Actions
-  - package-ecosystem: "github-actions"
-    directory: "/"
-    schedule:
-      interval: "weekly"
-      day: "monday"
-    # Group all GitHub Actions updates into a single PR
-    groups:
-      github-actions:
-        patterns:
-          - "*"
-    open-pull-requests-limit: 5
-    commit-message:
-      prefix: "chore"
-      include: "scope"
-    cooldown:
-      default-days: 7

.github/workflows/auto-test.yml

@@ -1,144 +1,110 @@
-name: Auto Test
+# This workflow will do a clean install of node dependencies, build the source code and run tests across different versions of node
+# For more information see: https://help.github.com/actions/language-and-framework-guides/using-nodejs-with-github-actions
 
-concurrency:
+name: Auto Test
-  group: ${{ github.workflow }}-${{ github.event.pull_request.number || github.ref }}-server
-  cancel-in-progress: true
 
 on:
   push:
-    branches: [master, 1.23.X, 3.0.0]
+    branches: [ master ]
+    paths-ignore:
+      - '*.md'
   pull_request:
-permissions: {}
+    branches: [ master, 2.0.X ]
+    paths-ignore:
+      - '*.md'
 
 jobs:
   auto-test:
+    needs: [ check-linters ]
     runs-on: ${{ matrix.os }}
-    permissions:
+    timeout-minutes: 15
-      contents: read
 
     strategy:
-      fail-fast: false
       matrix:
-        os: [macos-latest, ubuntu-22.04, windows-latest, ubuntu-22.04-arm]
+        os: [macos-latest, ubuntu-latest, windows-latest, ARM64]
+        node: [ 14, 20.5 ]
         # See supported Node.js release schedule at https://nodejs.org/en/about/releases/
-        node: [20, 24]
-        # Also test non-LTS, but only on Ubuntu.
-        include:
-          - os: ubuntu-22.04
-            node: 25
 
     steps:
-      - run: git config --global core.autocrlf false # Mainly for Windows
+    - run: git config --global core.autocrlf false  # Mainly for Windows
-      - uses: actions/checkout@8e8c483db84b4bee98b60c0593521ed34d9990e8 # v6.0.1
+    - uses: actions/checkout@v3
-        with: { persist-credentials: false }
 
-      - name: Cache/Restore node_modules
+    - name: Use Node.js ${{ matrix.node }}
-        uses: actions/cache@9255dc7a253b0ccc959486e2bca901246202afeb # v5.0.1
+      uses: actions/setup-node@v3
-        id: node-modules-cache
+      with:
-        with:
+        node-version: ${{ matrix.node }}
-          path: node_modules
+    - run: npm install npm@9 -g
-          key: node-modules-${{ runner.os }}-node${{ matrix.node }}-${{ hashFiles('**/package-lock.json') }}
+    - run: npm install
-
+    - run: npm run build
-      - name: Use Node.js ${{ matrix.node }}
+    - run: npm test
-        uses: actions/setup-node@395ad3262231945c25e8478fd5baf05154b1d79f # v6.1.0
+      env:
-        with:
+        HEADLESS_TEST: 1
-          node-version: ${{ matrix.node }}
+        JUST_FOR_TEST: ${{ secrets.JUST_FOR_TEST }}
-      - run: npm clean-install --no-fund
-
-      - name: Rebuild native modules for ARM64
-        if: matrix.os == 'ubuntu-22.04-arm'
-        run: npm rebuild @louislam/sqlite3
-
-      - run: npm run build
-      - run: npm run test-backend
-        env:
-          HEADLESS_TEST: 1
-          JUST_FOR_TEST: ${{ secrets.JUST_FOR_TEST }}
 
   # As a lot of dev dependencies are not supported on ARMv7, we have to test it separately and just test if `npm ci --production` works
   armv7-simple-test:
-    runs-on: ubuntu-latest
+    needs: [ check-linters ]
-    permissions:
+    runs-on: ${{ matrix.os }}
-      contents: read
+    timeout-minutes: 15
+
     strategy:
-      fail-fast: false
       matrix:
-        node: [20, 22]
+        os: [ ARMv7 ]
+        node: [ 14, 20 ]
         # See supported Node.js release schedule at https://nodejs.org/en/about/releases/
 
     steps:
-      - uses: actions/checkout@8e8c483db84b4bee98b60c0593521ed34d9990e8 # v6.0.1
+      - run: git config --global core.autocrlf false  # Mainly for Windows
-        with: { persist-credentials: false }
+      - uses: actions/checkout@v3
 
-      - name: Set up QEMU
+      - name: Use Node.js ${{ matrix.node }}
-        uses: docker/setup-qemu-action@c7c53464625b32c7a7e944ae62b3e17d2b600130 # v3.7.0
+        uses: actions/setup-node@v3
         with:
-          platforms: linux/arm/v7
+          node-version: ${{ matrix.node }}
-
+      - run: npm install npm@9 -g
-      - name: Set up Docker Buildx
+      - run: npm ci --production
-        uses: docker/setup-buildx-action@988b5a0280414f521da01fcc63a27aeeb4b104db # v3.6.1
-
-      - name: Test on ARMv7 using Docker with QEMU
-        run: |
-          docker run --rm --platform linux/arm/v7 \
-            -v $PWD:/workspace \
-            -w /workspace \
-            arm32v7/node:${{ matrix.node }} \
-            npm clean-install --no-fund --production
 
   check-linters:
     runs-on: ubuntu-latest
-    permissions:
-      contents: read
 
     steps:
-      - run: git config --global core.autocrlf false # Mainly for Windows
+    - run: git config --global core.autocrlf false  # Mainly for Windows
-      - uses: actions/checkout@8e8c483db84b4bee98b60c0593521ed34d9990e8 # v6.0.1
+    - uses: actions/checkout@v3
-        with: { persist-credentials: false }
 
-      - name: Cache/Restore node_modules
+    - name: Use Node.js 20
-        uses: actions/cache@9255dc7a253b0ccc959486e2bca901246202afeb # v5.0.1
+      uses: actions/setup-node@v3
-        id: node-modules-cache
+      with:
-        with:
+        node-version: 20
-          path: node_modules
+    - run: npm install
-          key: node-modules-${{ runner.os }}-node${{ matrix.node }}-${{ hashFiles('**/package-lock.json') }}
+    - run: npm run lint
 
-      - name: Use Node.js 20
+# TODO: Temporarily disable, as it cannot pass the test in 2.0.0 yet
-        uses: actions/setup-node@395ad3262231945c25e8478fd5baf05154b1d79f # v6.1.0
+#  e2e-tests:
-        with:
+#    needs: [ check-linters ]
-          node-version: 20
+#    runs-on: ubuntu-latest
-      - run: npm clean-install --no-fund
+#    steps:
-      - run: npm run lint:prod
+#    - run: git config --global core.autocrlf false  # Mainly for Windows
+#    - uses: actions/checkout@v3
+#
+#    - name: Use Node.js 14
+#      uses: actions/setup-node@v3
+#      with:
+#        node-version: 14
+#    - run: npm install
+#    - run: npm run build
+#    - run: npm run cy:test
 
-  e2e-test:
+  frontend-unit-tests:
-    runs-on: ubuntu-22.04-arm
+    needs: [ check-linters ]
-    permissions:
+    runs-on: ubuntu-latest
-      contents: read
-    env:
-      PLAYWRIGHT_VERSION: ~1.39.0
     steps:
-      - run: git config --global core.autocrlf false # Mainly for Windows
+    - run: git config --global core.autocrlf false  # Mainly for Windows
-      - uses: actions/checkout@8e8c483db84b4bee98b60c0593521ed34d9990e8 # v6.0.1
+    - uses: actions/checkout@v3
-        with: { persist-credentials: false }
 
-      - name: Cache/Restore node_modules
+    - name: Use Node.js 14
-        uses: actions/cache@9255dc7a253b0ccc959486e2bca901246202afeb # v5.0.1
+      uses: actions/setup-node@v3
-        id: node-modules-cache
+      with:
-        with:
+        node-version: 14
-          path: node_modules
+    - run: npm install
-          key: node-modules-${{ runner.os }}-node${{ matrix.node }}-${{ hashFiles('**/package-lock.json') }}
+    - run: npm run build
-
+    - run: npm run cy:run:unit
-      - name: Setup Node.js
-        uses: actions/setup-node@395ad3262231945c25e8478fd5baf05154b1d79f # v6.1.0
-        with:
-          node-version: 22
-      - run: npm clean-install --no-fund
-
-      - name: Rebuild native modules for ARM64
-        run: npm rebuild @louislam/sqlite3
-
-      - name: Install Playwright ${{ env.PLAYWRIGHT_VERSION }}
-        run: npx playwright@${{ env.PLAYWRIGHT_VERSION }} install
-
-      - run: npm run build
-      - run: npm run test-e2e

.github/workflows/autofix.yml

@@ -1,53 +0,0 @@
-name: autofix.ci
-
-on:
-  push:
-    branches: ["master", "1.23.X"]
-  pull_request:
-permissions: {}
-
-jobs:
-  autofix:
-    runs-on: ubuntu-latest
-    permissions:
-      contents: read
-    steps:
-      - uses: actions/checkout@8e8c483db84b4bee98b60c0593521ed34d9990e8 # v6.0.1
-        with: { persist-credentials: false }
-
-      - name: Cache/Restore node_modules
-        uses: actions/cache@9255dc7a253b0ccc959486e2bca901246202afeb # v5.0.1
-        id: node-modules-cache
-        with:
-          path: node_modules
-          key: node-modules-${{ runner.os }}-${{ hashFiles('**/package-lock.json') }}
-
-      - name: Setup Node.js
-        uses: actions/setup-node@395ad3262231945c25e8478fd5baf05154b1d79f # v6.1.0
-        with:
-          node-version: 20
-
-      - name: Install dependencies
-        run: npm ci
-
-      - name: Update RDAP DNS data from IANA
-        run: wget -O server/model/rdap-dns.json https://data.iana.org/rdap/dns.json
-        continue-on-error: true
-
-      - name: Auto-fix JavaScript/Vue linting issues
-        run: npm run lint-fix:js
-        continue-on-error: true
-
-      - name: Auto-fix CSS/SCSS linting issues
-        run: npm run lint-fix:style
-        continue-on-error: true
-
-      - name: Auto-format code with Prettier
-        run: npm run fmt
-        continue-on-error: true
-
-      - name: Compile TypeScript
-        run: npm run tsc
-        continue-on-error: true
-
-      - uses: autofix-ci/action@635ffb0c9798bd160680f18fd73371e355b85f27

.github/workflows/beta-release.yml

@@ -1,93 +0,0 @@
-name: Beta Release
-
-on:
-  workflow_dispatch:
-    inputs:
-      version:
-        description: "Beta version number (e.g., 2.1.0-beta.2)"
-        required: true
-        type: string
-      previous_version:
-        description: "Previous version tag for changelog (e.g., 2.1.0-beta.1)"
-        required: true
-        type: string
-      dry_run:
-        description: "Dry Run (The docker image will not be pushed to registries. PR will still be created.)"
-        required: false
-        type: boolean
-        default: false
-
-permissions:
-  contents: write
-  pull-requests: write
-
-jobs:
-  beta-release:
-    runs-on: ubuntu-latest
-    timeout-minutes: 120
-
-    steps:
-      - uses: actions/checkout@8e8c483db84b4bee98b60c0593521ed34d9990e8 # v6.0.1
-        with:
-          ref: master
-          persist-credentials: true
-          fetch-depth: 0 # Fetch all history for changelog generation
-
-      - name: Set up Node.js
-        uses: actions/setup-node@395ad3262231945c25e8478fd5baf05154b1d79f # v6.1.0
-        with:
-          node-version: 24
-
-      - name: Create release branch
-        env:
-          VERSION: ${{ inputs.version }}
-          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-        run: |
-          git config user.name "github-actions[bot]"
-          git config user.email "github-actions[bot]@users.noreply.github.com"
-          git remote set-url origin "https://x-access-token:${GITHUB_TOKEN}@github.com/${{ github.repository }}.git"
-          # Delete remote branch if it exists
-          git push origin --delete "release-${VERSION}" || true
-          # Delete local branch if it exists
-          git branch -D "release-${VERSION}" || true
-          # For testing purpose
-          # git checkout beta-workflow
-          git checkout -b "release-${VERSION}"
-
-      - name: Install dependencies
-        run: npm clean-install --no-fund
-
-      - name: Set up Docker Buildx
-        uses: docker/setup-buildx-action@988b5a0280414f521da01fcc63a27aeeb4b104db # v3.6.1
-
-      - name: Set up QEMU
-        uses: docker/setup-qemu-action@c7c53464625b32c7a7e944ae62b3e17d2b600130 # v3.7.0
-
-      - name: Login to Docker Hub
-        uses: docker/login-action@9780b0c442fbb1117ed29e0efdff1e18412f7567 # v3.3.0
-        with:
-          username: ${{ secrets.DOCKERHUB_USERNAME }}
-          password: ${{ secrets.DOCKERHUB_TOKEN }}
-
-      - name: Login to GitHub Container Registry
-        uses: docker/login-action@9780b0c442fbb1117ed29e0efdff1e18412f7567 # v3.3.0
-        with:
-          registry: ghcr.io
-          username: ${{ secrets.GHCR_USERNAME }}
-          password: ${{ secrets.GHCR_TOKEN }}
-
-      - name: Run release-beta
-        env:
-          RELEASE_BETA_VERSION: ${{ inputs.version }}
-          RELEASE_PREVIOUS_VERSION: ${{ inputs.previous_version }}
-          DRY_RUN: ${{ inputs.dry_run }}
-          GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-          GITHUB_RUN_ID: ${{ github.run_id }}
-        run: npm run release-beta
-
-      - name: Upload dist.tar.gz as artifact
-        uses: actions/upload-artifact@b4b15b8c7c6ac21ea08fcf65892d2ee8f75cf882 # v4.4.3
-        with:
-          name: dist-${{ inputs.version }}
-          path: ./tmp/dist.tar.gz
-          retention-days: 90

.github/workflows/build-docker-base.yml

@@ -1,48 +0,0 @@
-name: Build Docker Base Images
-
-on:
-  workflow_dispatch: # Allow manual trigger
-
-permissions: {}
-
-jobs:
-  build-docker-base:
-    runs-on: ubuntu-latest
-    timeout-minutes: 120
-    permissions:
-      contents: read
-      packages: write
-
-    steps:
-      - uses: actions/checkout@8e8c483db84b4bee98b60c0593521ed34d9990e8 # v6.0.1
-        with: { persist-credentials: false }
-
-      - name: Set up QEMU
-        uses: docker/setup-qemu-action@c7c53464625b32c7a7e944ae62b3e17d2b600130 # v3.7.0
-
-      - name: Set up Docker Buildx
-        uses: docker/setup-buildx-action@988b5a0280414f521da01fcc63a27aeeb4b104db # v3.6.1
-
-      - name: Login to Docker Hub
-        uses: docker/login-action@9780b0c442fbb1117ed29e0efdff1e18412f7567 # v3.3.0
-        with:
-          username: ${{ secrets.DOCKERHUB_USERNAME }}
-          password: ${{ secrets.DOCKERHUB_TOKEN }}
-
-      - name: Login to GitHub Container Registry
-        uses: docker/login-action@9780b0c442fbb1117ed29e0efdff1e18412f7567 # v3.3.0
-        with:
-          registry: ghcr.io
-          username: ${{ secrets.GHCR_USERNAME }}
-          password: ${{ secrets.GHCR_TOKEN }}
-
-      - name: Use Node.js 20
-        uses: actions/setup-node@395ad3262231945c25e8478fd5baf05154b1d79f # v6.1.0
-        with:
-          node-version: 20
-
-      - name: Build and push base2-slim image
-        run: npm run build-docker-base-slim
-
-      - name: Build and push base2 image
-        run: npm run build-docker-base

.github/workflows/close-incorrect-issue.yml

@@ -3,29 +3,23 @@ name: Close Incorrect Issue
 on:
   issues:
     types: [opened]
-permissions: {}
 
 jobs:
   close-incorrect-issue:
     runs-on: ${{ matrix.os }}
-    permissions:
-      issues: write
 
     strategy:
       matrix:
         os: [ubuntu-latest]
-        node-version: [20]
+        node-version: [16]
 
     steps:
-      - uses: actions/checkout@8e8c483db84b4bee98b60c0593521ed34d9990e8 # v6.0.1
+    - uses: actions/checkout@v3
-        with: { persist-credentials: false }
 
-      - name: Use Node.js ${{ matrix.node-version }}
+    - name: Use Node.js ${{ matrix.node-version }}
-        uses: actions/setup-node@395ad3262231945c25e8478fd5baf05154b1d79f # v6.1.0
+      uses: actions/setup-node@v3
-        with:
+      with:
-          node-version: ${{ matrix.node-version }}
+        node-version: ${{ matrix.node-version }}
-      - run: npm ci
+        cache: 'npm'
-      - name: Close incorrect issue
+    - run: npm ci
-        run: node extra/close-incorrect-issue.js ${{ secrets.GITHUB_TOKEN }} ${{ github.event.issue.number }} "$ISSUE_USER_LOGIN"
+    - run: node extra/close-incorrect-issue.js ${{ secrets.GITHUB_TOKEN }} ${{ github.event.issue.number }} ${{ github.event.issue.user.login }}
-        env:
-          ISSUE_USER_LOGIN: ${{ github.event.issue.user.login }}

.github/workflows/codeql-analysis.yml

@@ -1,55 +0,0 @@
-name: "CodeQL"
-
-on:
-  push:
-    branches: ["master", "1.23.X"]
-  pull_request:
-    branches: ["master", "1.23.X"]
-  schedule:
-    - cron: "16 22 * * 0"
-
-jobs:
-  analyze:
-    name: Analyze
-    runs-on: ubuntu-latest
-    timeout-minutes: 360
-
-    permissions:
-      actions: read
-      contents: read
-      security-events: write
-
-    strategy:
-      fail-fast: false
-      matrix:
-        language: ["go", "javascript-typescript"]
-
-    steps:
-      - uses: actions/checkout@8e8c483db84b4bee98b60c0593521ed34d9990e8 # v6.0.1
-        with: { persist-credentials: false }
-
-      # Initializes the CodeQL tools for scanning.
-      - name: Initialize CodeQL
-        uses: github/codeql-action/init@5d4e8d1aca955e8d8589aabd499c5cae939e33c7 # v4.31.9
-        with:
-          languages: ${{ matrix.language }}
-
-      - name: Autobuild
-        uses: github/codeql-action/autobuild@5d4e8d1aca955e8d8589aabd499c5cae939e33c7 # v4.31.9
-
-      - name: Perform CodeQL Analysis
-        uses: github/codeql-action/analyze@5d4e8d1aca955e8d8589aabd499c5cae939e33c7 # v4.31.9
-        with:
-          category: "/language:${{matrix.language}}"
-  zizmor:
-    runs-on: ubuntu-latest
-    permissions:
-      security-events: write
-      contents: read
-      actions: read
-    steps:
-      - name: Checkout repository
-        uses: actions/checkout@8e8c483db84b4bee98b60c0593521ed34d9990e8 # v6.0.1
-        with: { persist-credentials: false }
-      - name: Run zizmor
-        uses: zizmorcore/zizmor-action@e639db99335bc9038abc0e066dfcd72e23d26fb4 # v0.3.0

.github/workflows/conflict-labeler.yml

@@ -1,30 +0,0 @@
-name: Merge Conflict Labeler
-
-# pull_request_target is safe here because:
-# 1. Only uses a pinned trusted action (by SHA)
-# 2. Has minimal permissions (contents: read, pull-requests: write)
-# 3. Doesn't checkout or execute any untrusted code from PRs
-# 4. Only adds/removes labels based on merge conflict status
-on: # zizmor: ignore[dangerous-triggers]
-  push:
-    branches:
-      - master
-  pull_request_target:
-    branches:
-      - master
-    types: [synchronize]
-
-jobs:
-  label:
-    name: Labeling
-    runs-on: ubuntu-latest
-    if: ${{ github.repository == 'louislam/uptime-kuma' }}
-    permissions:
-      contents: read
-      pull-requests: write
-    steps:
-      - name: Apply label
-        uses: eps1lon/actions-label-merge-conflict@1df065ebe6e3310545d4f4c4e862e43bdca146f0 # v3.0.3
-        with:
-          dirtyLabel: "needs:resolve-merge-conflict"
-          repoToken: "${{ secrets.GITHUB_TOKEN }}"

.github/workflows/json-yaml-validate.yml

@@ -0,0 +1,27 @@
+name: json-yaml-validate
+on:
+  push:
+    branches:
+      - master
+  pull_request:
+    branches:
+      - master
+      - 2.0.X
+  workflow_dispatch:
+
+permissions:
+  contents: read
+  pull-requests: write # enable write permissions for pull request comments
+
+jobs:
+  json-yaml-validate:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v3
+
+      - name: json-yaml-validate
+        id: json-yaml-validate
+        uses: GrantBirki/json-yaml-validate@v1.3.0
+        with:
+          comment: "true" # enable comment mode
+          exclude_file: ".github/config/exclude.txt" # gitignore style file for exclusions

.github/workflows/mark-as-draft-on-requesting-changes.yml

@@ -1,65 +0,0 @@
-name: Mark PR as draft when changes are requested
-
-# pull_request_target is safe here because:
-# 1. Does not use any external actions; only uses the GitHub CLI via run commands
-# 2. Has minimal permissions
-# 3. Doesn't checkout or execute any untrusted code from PRs
-# 4. Only adds/removes labels or changes the draft status
-on: # zizmor: ignore[dangerous-triggers]
-  pull_request_target:
-    types:
-      - review_submitted
-      - labeled
-      - ready_for_review
-
-permissions: {}
-
-jobs:
-  mark-draft:
-    runs-on: ubuntu-latest
-    permissions:
-      pull-requests: write
-    if: |
-      (
-        github.event.action == 'review_submitted' &&
-        github.event.review.state == 'changes_requested'
-      ) || (
-        github.event.action == 'labeled' &&
-        github.event.label.name == 'pr:please address review comments'
-      )
-    steps:
-      - name: Add label on requested changes
-        if: github.event.review.state == 'changes_requested'
-        env:
-          GH_TOKEN: ${{ github.token }}
-        run: |
-          gh issue edit "${{ github.event.pull_request.number }}" \
-            --repo "${{ github.repository }}" \
-            --add-label "pr:please address review comments"
-
-      - name: Mark PR as draft
-        env:
-          GH_TOKEN: ${{ github.token }}
-        run: |
-          gh pr ready "${{ github.event.pull_request.number }}" \
-            --repo "${{ github.repository }}" \
-            --undo || true
-          # || true to ignore the case where the pr is already a draft
-
-  ready-for-review:
-    runs-on: ubuntu-latest
-    permissions:
-      pull-requests: write
-    if: github.event.action == 'ready_for_review'
-    steps:
-      - name: Update labels for review
-        env:
-          GH_TOKEN: ${{ github.token }}
-        run: |
-          gh issue edit "${{ github.event.pull_request.number }}" \
-            --repo "${{ github.repository }}" \
-            --remove-label "pr:please address review comments" || true
-
-          gh issue edit "${{ github.event.pull_request.number }}" \
-            --repo "${{ github.repository }}" \
-            --add-label "pr:needs review"

.github/workflows/new-contributor-pr.yml

@@ -1,40 +0,0 @@
-name: New contributor message
-
-on:
-  # Safety
-  # This workflow uses pull_request_target so it can run with write permissions on first-time contributor PRs.
-  # It is safe because it does not check out or execute any code from the pull request and
-  # only uses the pinned, trusted plbstl/first-contribution action
-  pull_request_target: # zizmor: ignore[dangerous-triggers]
-    types: [opened, closed]
-    branches:
-      - master
-
-permissions:
-  pull-requests: write
-
-jobs:
-  build:
-    if: github.repository == 'louislam/uptime-kuma'
-    name: Hello new contributor
-    runs-on: ubuntu-latest
-    timeout-minutes: 60
-    steps:
-      - uses: plbstl/first-contribution@4b2b042fffa26792504a18e49aa9543a87bec077 # v4.1.0
-        with:
-          pr-reactions: rocket
-          pr-opened-msg: >
-            Hello and thanks for lending a paw to Uptime Kuma! 🐻👋
-
-            As this is your first contribution, please be sure to check out our [Pull Request guidelines](https://github.com/louislam/uptime-kuma/blob/master/CONTRIBUTING.md#can-i-create-a-pull-request-for-uptime-kuma).
-
-            In particular:
-            - Mark your PR as Draft while you’re still making changes
-            - Mark it as Ready for review once it’s fully ready
-
-            If you have any design or process questions, feel free to ask them right here in this pull request - unclear documentation is a bug too.
-          pr-merged-msg: >
-            @{fc-author} congrats on your first contribution to Uptime Kuma! 🐻
-
-            We hope you enjoy contributing to our project and look forward to seeing more of your work in the future!
-            If you want to see your contribution in action, please see our [nightly builds here](https://hub.docker.com/layers/louislam/uptime-kuma/nightly2).

.github/workflows/nightly-release.yml

@@ -1,58 +0,0 @@
-name: Nightly Release
-
-on:
-  schedule:
-    # Runs at 2:00 AM UTC every day
-    - cron: "0 2 * * *"
-  workflow_dispatch: # Allow manual trigger
-
-permissions: {}
-
-jobs:
-  release-nightly:
-    runs-on: ubuntu-latest
-    timeout-minutes: 120
-    permissions:
-      contents: read
-      packages: write
-
-    steps:
-      - uses: actions/checkout@8e8c483db84b4bee98b60c0593521ed34d9990e8 # v6.0.1
-        with: { persist-credentials: false }
-
-      - name: Set up QEMU
-        uses: docker/setup-qemu-action@c7c53464625b32c7a7e944ae62b3e17d2b600130 # v3.7.0
-
-      - name: Set up Docker Buildx
-        uses: docker/setup-buildx-action@988b5a0280414f521da01fcc63a27aeeb4b104db # v3.6.1
-
-      - name: Login to Docker Hub
-        uses: docker/login-action@9780b0c442fbb1117ed29e0efdff1e18412f7567 # v3.3.0
-        with:
-          username: ${{ secrets.DOCKERHUB_USERNAME }}
-          password: ${{ secrets.DOCKERHUB_TOKEN }}
-
-      - name: Login to GitHub Container Registry
-        uses: docker/login-action@9780b0c442fbb1117ed29e0efdff1e18412f7567 # v3.3.0
-        with:
-          registry: ghcr.io
-          username: ${{ secrets.GHCR_USERNAME }}
-          password: ${{ secrets.GHCR_TOKEN }}
-
-      - name: Use Node.js 20
-        uses: actions/setup-node@395ad3262231945c25e8478fd5baf05154b1d79f # v6.1.0
-        with:
-          node-version: 20
-
-      - name: Cache/Restore node_modules
-        uses: actions/cache@9255dc7a253b0ccc959486e2bca901246202afeb # v5.0.1
-        id: node-modules-cache
-        with:
-          path: node_modules
-          key: node-modules-${{ runner.os }}-node20-${{ hashFiles('**/package-lock.json') }}
-
-      - name: Install dependencies
-        run: npm clean-install --no-fund
-
-      - name: Run release-nightly
-        run: npm run release-nightly

.github/workflows/pr-title.yml

@@ -1,31 +0,0 @@
-name: "PR Metadata"
-# if someone opens a PR, edits it, or reopens it we want to validate the title
-# This is separate from the rest of the CI as the title may change without code changes
-
-on:
-  # SECURITY: pull_request_target is used here to allow validation of PRs from forks.
-  # This is safe because:
-  # 1. No code from the PR is checked out
-  # 2. Permissions are restricted to pull-requests: read
-  # 3. Only a trusted third-party action is used to validate the PR title
-  # 4. No user-controlled code is executed
-  pull_request_target: # zizmor: ignore[dangerous-triggers]
-    types:
-      - opened
-      - edited
-      - reopened
-      - synchronize
-
-permissions:
-  pull-requests: read
-
-jobs:
-  pr-title:
-    name: Validate PR title follows https://conventionalcommits.org
-    runs-on: ubuntu-latest
-    permissions:
-      pull-requests: read
-    steps:
-      - uses: amannn/action-semantic-pull-request@48f256284bd46cdaab1048c3721360e808335d50 # v6.1.1
-        env:
-          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

.github/workflows/prevent-file-change.yml

@@ -2,18 +2,16 @@ name: prevent-file-change
 
 on:
   pull_request:
-permissions: {}
 
 jobs:
   check-file-changes:
     runs-on: ubuntu-latest
-    permissions:
-      pull-requests: read
     steps:
       - name: Prevent file change
-        uses: xalvarez/prevent-file-change-action@004d9f17c2e4a7afa037cda5f38dc55a5e9c9c06 # v1.9.1
+        uses: xalvarez/prevent-file-change-action@v1
         with:
           githubToken: ${{ secrets.GITHUB_TOKEN }}
           # Regex, /src/lang/*.json is not allowed to be changed, except for /src/lang/en.json
           pattern: '^(?!src/lang/en\.json$)src/lang/.*\.json$'
           trustedAuthors: UptimeKumaBot
+

.github/workflows/stale-bot.yml

@@ -1,45 +1,22 @@
-name: "Automatically close stale issues"
+name: 'Automatically close stale issues and PRs'
 on:
   workflow_dispatch:
   schedule:
-    - cron: "0 */6 * * *"
+    - cron: '0 */6 * * *'
 #Run every 6 hours
-permissions: {}
 
 jobs:
   stale:
     runs-on: ubuntu-latest
-    permissions:
-      actions: write
-      issues: write
     steps:
-      - uses: actions/stale@997185467fa4f803885201cee163a9f38240193d # v10.1.1
+      - uses: actions/stale@v7
         with:
-          stale-issue-message: |-
+          stale-issue-message: 'We are clearing up our old issues and your ticket has been open for 3 months with no activity. Remove stale label or comment or this will be closed in 2 days.'
-            We are clearing up our old `help`-issues and your issue has been open for 60 days with no activity.
+          close-issue-message: 'This issue was closed because it has been stalled for 2 days with no activity.'
-            If no comment is made and the stale label is not removed, this issue will be closed in 7 days.
+          days-before-stale: 90
-          days-before-stale: 60
+          days-before-close: 2
-          days-before-close: 7
+          days-before-pr-stale: 999999999
-          days-before-pr-stale: -1
+          days-before-pr-close: 1
-          days-before-pr-close: -1
+          exempt-issue-labels: 'News,Medium,High,discussion,bug,doc,feature-request'
-          exempt-issue-labels: "News,discussion,bug,doc,feature-request"
+          exempt-issue-assignees: 'louislam'
-          exempt-issue-assignees: "louislam"
-          operations-per-run: 200
-      - uses: actions/stale@997185467fa4f803885201cee163a9f38240193d # v10.1.1
-        with:
-          stale-issue-message: |-
-            This issue was marked as `cannot-reproduce` by a maintainer.
-            If an issue is non-reproducible, we cannot fix it, as we do not know what the underlying issue is.
-            If you have any ideas how we can reproduce this issue, we would love to hear them.
-
-            We don't have a good way to deal with truely unreproducible issues and are going to close this issue in a month.
-            If think there might be other differences in our environment or in how we tried to reproduce this, we would appreciate any ideas.
-          close-issue-message: |-
-            This issue will be closed as no way to reproduce it has been found.
-            If you/somebody finds a way how to (semi-reliably) reproduce this, we can reopen this issue. ^^
-          days-before-stale: 180
-          days-before-close: 30
-          days-before-pr-stale: -1
-          days-before-pr-close: -1
-          any-of-issue-labels: "cannot-reproduce"
           operations-per-run: 200

.github/workflows/validate.yml

@@ -1,47 +0,0 @@
-name: validate
-on:
-  push:
-    branches:
-      - master
-  pull_request:
-    branches:
-      - master
-      - 1.23.X
-  workflow_dispatch:
-permissions: {}
-
-jobs:
-  json-yaml-validate:
-    runs-on: ubuntu-latest
-    permissions:
-      contents: read
-      pull-requests: write # enable write permissions for pull request comments
-    steps:
-      - uses: actions/checkout@8e8c483db84b4bee98b60c0593521ed34d9990e8 # v6.0.1
-        with: { persist-credentials: false }
-
-      - name: json-yaml-validate
-        id: json-yaml-validate
-        uses: GrantBirki/json-yaml-validate@9bbaa8474e3af4e91f25eda8ac194fdc30564d96 # v4.0.0
-        with:
-          comment: "true" # enable comment mode
-          exclude_file: ".github/config/exclude.txt" # gitignore style file for exclusions
-
-  # General validations
-  validate:
-    runs-on: ubuntu-latest
-    permissions:
-      contents: read
-    steps:
-      - uses: actions/checkout@8e8c483db84b4bee98b60c0593521ed34d9990e8 # v6.0.1
-        with: { persist-credentials: false }
-      - name: Use Node.js 20
-        uses: actions/setup-node@395ad3262231945c25e8478fd5baf05154b1d79f # v6.1.0
-        with:
-          node-version: 20
-
-      - name: Validate language JSON files
-        run: node ./extra/check-lang-json.js
-
-      - name: Validate knex migrations filename
-        run: node ./extra/check-knex-filenames.mjs

.gitignore

@@ -15,6 +15,9 @@ dist-ssr
 /tmp
 .env
 
+cypress/videos
+cypress/screenshots
+
 /extra/healthcheck.exe
 /extra/healthcheck
 /extra/healthcheck-armv7

.prettierignore

@@ -1,2 +0,0 @@
-# language files
-src/lang/*.json

.prettierrc.js

@@ -1,65 +0,0 @@
-/**
- * Prettier Configuration for Uptime Kuma
- *
- * Usage:
- *   npm run fmt              - Format all files (auto-runs in CI via autofix workflow)
- *   npm run fmt -- --check   - Check formatting without making changes
- *
- * TIP: This formatter is automatically run in CI, so no need to worry about it
- */
-module.exports = {
-    // Core formatting options - matching original ESLint rules
-    semi: true,
-    singleQuote: false,
-    trailingComma: "es5",
-    printWidth: 120,
-    tabWidth: 4,
-    useTabs: false,
-    endOfLine: "lf",
-    arrowParens: "always",
-    bracketSpacing: true,
-    bracketSameLine: false,
-
-    // Vue-specific settings
-    vueIndentScriptAndStyle: false,
-    singleAttributePerLine: false,
-    htmlWhitespaceSensitivity: "ignore", // More forgiving with whitespace in HTML
-
-    // Override settings for specific file types
-    overrides: [
-        {
-            files: "*.vue",
-            options: {
-                parser: "vue",
-            },
-        },
-        {
-            files: ["*.json"],
-            options: {
-                tabWidth: 4,
-                trailingComma: "none",
-            },
-        },
-        {
-            files: ["*.yml", "*.yaml"],
-            options: {
-                tabWidth: 2,
-                trailingComma: "none",
-            },
-        },
-        {
-            files: ["src/icon.js"],
-            options: {
-                trailingComma: "all",
-            },
-        },
-        {
-            files: ["*.md"],
-            options: {
-                printWidth: 100,
-                proseWrap: "preserve",
-                tabWidth: 2,
-            },
-        },
-    ],
-};

.stylelintrc

@@ -1,11 +1,10 @@
 {
-    "extends": [
+    "extends": "stylelint-config-standard",
-        "stylelint-config-standard",
-        "stylelint-config-prettier"
-    ],
     "customSyntax": "postcss-html",
     "rules": {
+        "indentation": 4,
         "no-descending-specificity": null,
+        "selector-list-comma-newline-after": null,
         "declaration-empty-line-before": null,
         "alpha-value-notation": "number",
         "color-function-notation": "legacy",

CODE_OF_CONDUCT.md

@@ -6,8 +6,8 @@ We as members, contributors, and leaders pledge to make participation in our
 community a harassment-free experience for everyone, regardless of age, body
 size, visible or invisible disability, ethnicity, sex characteristics, gender
 identity and expression, level of experience, education, socio-economic status,
-nationality, personal appearance, race, caste, color, religion, or sexual
+nationality, personal appearance, race, religion, or sexual identity
-identity and orientation.
+and orientation.
 
 We pledge to act and interact in ways that contribute to an open, welcoming,
 diverse, inclusive, and healthy community.
@@ -17,23 +17,23 @@ diverse, inclusive, and healthy community.
 Examples of behavior that contributes to a positive environment for our
 community include:
 
-- Demonstrating empathy and kindness toward other people
+* Demonstrating empathy and kindness toward other people
-- Being respectful of differing opinions, viewpoints, and experiences
+* Being respectful of differing opinions, viewpoints, and experiences
-- Giving and gracefully accepting constructive feedback
+* Giving and gracefully accepting constructive feedback
-- Accepting responsibility and apologizing to those affected by our mistakes,
+* Accepting responsibility and apologizing to those affected by our mistakes,
   and learning from the experience
-- Focusing on what is best not just for us as individuals, but for the overall
+* Focusing on what is best not just for us as individuals, but for the
-  community
+  overall community
 
 Examples of unacceptable behavior include:
 
-- The use of sexualized language or imagery, and sexual attention or advances of
+* The use of sexualized language or imagery, and sexual attention or
-  any kind
+  advances of any kind
-- Trolling, insulting or derogatory comments, and personal or political attacks
+* Trolling, insulting or derogatory comments, and personal or political attacks
-- Public or private harassment
+* Public or private harassment
-- Publishing others' private information, such as a physical or email address,
+* Publishing others' private information, such as a physical or email
-  without their explicit permission
+  address, without their explicit permission
-- Other conduct which could reasonably be considered inappropriate in a
+* Other conduct which could reasonably be considered inappropriate in a
   professional setting
 
 ## Enforcement Responsibilities
@@ -52,7 +52,7 @@ decisions when appropriate.
 
 This Code of Conduct applies within all community spaces, and also applies when
 an individual is officially representing the community in public spaces.
-Examples of representing our community include using an official email address,
+Examples of representing our community include using an official e-mail address,
 posting via an official social media account, or acting as an appointed
 representative at an online or offline event.
 
@@ -60,8 +60,8 @@ representative at an online or offline event.
 
 Instances of abusive, harassing, or otherwise unacceptable behavior may be
 reported to the community leaders responsible for enforcement at
-<uptime@kuma.pet>. All complaints will be reviewed and investigated promptly and
+uptime@kuma.pet.
-fairly.
+All complaints will be reviewed and investigated promptly and fairly.
 
 All community leaders are obligated to respect the privacy and security of the
 reporter of any incident.
@@ -82,15 +82,15 @@ behavior was inappropriate. A public apology may be requested.
 
 ### 2. Warning
 
-**Community Impact**: A violation through a single incident or series of
+**Community Impact**: A violation through a single incident or series
-actions.
+of actions.
 
 **Consequence**: A warning with consequences for continued behavior. No
 interaction with the people involved, including unsolicited interaction with
 those enforcing the Code of Conduct, for a specified period of time. This
 includes avoiding interactions in community spaces as well as external channels
-like social media. Violating these terms may lead to a temporary or permanent
+like social media. Violating these terms may lead to a temporary or
-ban.
+permanent ban.
 
 ### 3. Temporary Ban
 
@@ -109,24 +109,20 @@ Violating these terms may lead to a permanent ban.
 standards, including sustained inappropriate behavior, harassment of an
 individual, or aggression toward or disparagement of classes of individuals.
 
-**Consequence**: A permanent ban from any sort of public interaction within the
+**Consequence**: A permanent ban from any sort of public interaction within
-community.
+the community.
 
 ## Attribution
 
 This Code of Conduct is adapted from the [Contributor Covenant][homepage],
-version 2.1, available at
+version 2.0, available at
-[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
+https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
 
 Community Impact Guidelines were inspired by [Mozilla's code of conduct
-enforcement ladder][Mozilla CoC].
+enforcement ladder](https://github.com/mozilla/diversity).
-
-For answers to common questions about this code of conduct, see the FAQ at
-[https://www.contributor-covenant.org/faq][FAQ]. Translations are available at
-[https://www.contributor-covenant.org/translations][translations].
 
 [homepage]: https://www.contributor-covenant.org
-[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
+
-[Mozilla CoC]: https://github.com/mozilla/diversity
+For answers to common questions about this code of conduct, see the FAQ at
-[FAQ]: https://www.contributor-covenant.org/faq
+https://www.contributor-covenant.org/faq. Translations are available at
-[translations]: https://www.contributor-covenant.org/translations
+https://www.contributor-covenant.org/translations.

CONTRIBUTING.md

@@ -1,303 +1,95 @@
 # Project Info
 
-First of all, I want to thank everyone who has submitted issues or shared pull
+First of all, I want to thank everyone who made pull requests for Uptime Kuma. I never thought the GitHub Community would be so nice! Because of this, I also never thought that other people would actually read and edit my code. It is not very well structured or commented, sorry about that.
-requests for Uptime Kuma. I never thought the GitHub community would be so nice!
-Because of this, I also never thought that other people would actually read and
-edit my code. Parts of the code are not very well-structured or commented, sorry
-about that.
 
-Before you start, please read our [Code of Conduct](CODE_OF_CONDUCT.md) to understand our community standards.
+The project was created with vite.js (vue3). Then I created a subdirectory called "server" for the server part. Both frontend and backend share the same package.json.
 
-The project was created with `vite` and is written in `vue3`. Our backend
+The frontend code builds into "dist" directory. The server (express.js) exposes the "dist" directory as the root of the endpoint. This is how production is working.
-lives in the `server`-directory and mostly communicates via websockets.
-Both frontend and backend share the same `package.json`.
 
-For production, the frontend is built into the `dist`-directory and the server
+## Key Technical Skills
-(`express.js`) exposes the `dist` directory as the root of the endpoint. For
+
-development, we run vite in development mode on another port.
+- Node.js (You should know about promise, async/await and arrow function etc.)
+- Socket.io
+- SCSS
+- Vue.js
+- Bootstrap
+- SQLite
 
 ## Directories
 
-- `config` (dev config files)
+- config (dev config files)
-- `data` (App data)
+- data (App data)
-- `db` (Base database and migration scripts)
+- db (Base database and migration scripts)
-- `dist` (Frontend build)
+- dist (Frontend build)
-- `docker` (Dockerfiles)
+- docker (Dockerfiles)
-- `extra` (Extra useful scripts)
+- extra (Extra useful scripts)
-- `public` (Frontend resources for dev only)
+- public (Frontend resources for dev only)
-- `server` (Server source code)
+- server (Server source code)
-- `src` (Frontend source code)
+- src (Frontend source code)
-- `test` (unit test)
+- test (unit test)
 
-## Can I Create a Pull Request for Uptime Kuma?
+## Can I create a pull request for Uptime Kuma?
 
-Whether or not you can create a pull request depends on the nature of your
+Yes or no, it depends on what you will try to do. Since I don't want to waste your time, be sure to **create an empty draft pull request or open an issue, so we can have a discussion first**. Especially for a large pull request or you don't know if it will be merged or not.
-contribution. We value both your time and our maintainers' time, so we want to
-make sure it's spent efficiently.
 
-If you're unsure about any process or step, you're probably not the only one
+Here are some references:
-with that question—please feel free to ask. We're happy to help!
 
-Different types of pull requests (PRs) may have different guidelines, so be sure
+### ✅ Usually accepted
-to review the appropriate one for your contribution.
 
-- <details><summary><b>Security Fixes</b> (click to expand)</summary>
+- Bug fix
-  <p>
+- Security fix
+- Adding notification providers
+- Adding new language files (see [these instructions](https://github.com/louislam/uptime-kuma/blob/master/src/lang/README.md))
+- Adding new language keys: `$t("...")`
 
-  Submitting security fixes is something that may put the community at risk.
+### ⚠️ Discussion required
-  Please read through our [security policy](SECURITY.md) and submit
-  vulnerabilities via an [advisory] + [issue] instead. We encourage you to
-  submit how to fix a vulnerability if you know how to, this is not required.
-  Following the security policy allows us to properly test, fix bugs. This
-  review allows us to notice, if there are any changes necessary to unrelated
-  parts like the documentation.
-  [**PLEASE SEE OUR SECURITY POLICY.**](SECURITY.md)
 
-  [advisory]: https://github.com/louislam/uptime-kuma/security/advisories/new
+- Large pull requests
-  [issue]: https://github.com/louislam/uptime-kuma/issues/new?template=security_issue.yml
+- New features
 
-  </p>
+### ❌ Won't be merged
-  </details>
 
-- <details><summary><b>Small, Non-Breaking Bug Fixes</b> (click to expand)</summary>
+- A dedicated PR for translating existing languages (see [these instructions](https://github.com/louislam/uptime-kuma/blob/master/src/lang/README.md))
-  <p>
+- Do not pass the auto-test
+- Any breaking changes
+- Duplicated pull requests
+- Buggy
+- UI/UX is not close to Uptime Kuma
+- Modifications or deletions of existing logic without a valid reason.
+- Adding functions that is completely out of scope
+- Converting existing code into other programming languages
+- Unnecessarily large code changes that are hard to review and cause conflicts with other PRs.
 
-  If you come across a bug and think you can solve, we appreciate your work.
+The above cases may not cover all possible situations.
-  Please make sure that you follow these rules:
-  - keep the PR as small as possible, fix only one thing at a time => keeping it
-    reviewable
-  - test that your code does what you claim it does.
 
-  <sub>Because maintainer time is precious, junior maintainers may merge
+I (@louislam) have the final say. If your pull request does not meet my expectations, I will reject it, no matter how much time you spend on it. Therefore, it is essential to have a discussion beforehand.
-  uncontroversial PRs in this area.</sub>
 
-  </p>
+I will assign your pull request to a [milestone](https://github.com/louislam/uptime-kuma/milestones), if I plan to review and merge it.
-  </details>
 
-- <details><summary><b>Translations / Internationalisation (i18n)</b> (click to expand)</summary>
+Also, please don't rush or ask for an ETA, because I have to understand the pull request, make sure it is no breaking changes and stick to my vision of this project, especially for large pull requests.
-  <p>
 
-  Please add **all** strings that are translatable to `src/lang/en.json`. If translation keys are omitted, they cannot be translated. **Do not include any other languages in your initial pull request** (even if it is your mother tongue) to avoid merge conflicts between Weblate and `master`. Once your PR is merged into `master`, the strings can be translated by awesome people donating their language skills.
+### Recommended Pull Request Guideline
 
-  We use Weblate to localise this project into many languages. If you want to help translate Uptime Kuma into your language, please see [these instructions on how to translate using Weblate](https://github.com/louislam/uptime-kuma/blob/master/src/lang/README.md).
+Before deep into coding, discussion first is preferred. Creating an empty pull request for discussion would be recommended.
 
-  There are some cases where a change cannot be done directly in Weblate and requires a PR:
+1. Fork the project
-  - A text may not yet be localisable. In this case, **adding a new language key** via `{{ $t("Translation key") }}` or [`<i18n-t keypath="Translation key">`](https://vue-i18n.intlify.dev/guide/advanced/component.html) might be necessary.
+1. Clone your fork repo to local
-  - Language keys need to be **added to `en.json`** to appear in Weblate. If this has not been done, a PR is appreciated.
+1. Create a new branch
-  - **Adding a new language** requires creating a new file. See [these instructions](https://github.com/louislam/uptime-kuma/blob/master/src/lang/README.md).
+1. Create an empty commit
+   `git commit -m "[empty commit] pull request for <YOUR TASK NAME>" --allow-empty`
+1. Push to your fork repo
+1. Create a pull request: https://github.com/louislam/uptime-kuma/compare
+1. Write a proper description
+1. Click "Change to draft"
+1. Discussion
 
-  <sub>Because maintainer time is precious, junior maintainers may merge uncontroversial PRs in this area.</sub>
+## Project Styles
 
-  </p>
+I personally do not like something that requires so many configurations before you can finally start the app. I hope Uptime Kuma installation will be as easy as like installing a mobile app.
-  </details>
 
-- <details><summary><b>New Notification Providers</b> (click to expand)</summary>
+- Easy to install for non-Docker users, no native build dependency is needed (for x86_64/armv7/arm64), no extra config, and no extra effort required to get it running
-  <p>
+- Single container for Docker users, no very complex docker-compose file. Just map the volume and expose the port, then good to go
-
+- Settings should be configurable in the frontend. Environment variables are discouraged, unless it is related to startup such as `DATA_DIR`
-  To set up a new notification provider these files need to be modified/created:
-  - `server/notification-providers/PROVIDER_NAME.js` is where the heart of the
-    notification provider lives.
-
-        - Both `monitorJSON` and `heartbeatJSON` can be `null` for some events. If
-
-  both are `null`, this is a general testing message, but if just
-  `heartbeatJSON` is `null` this is a certificate expiry.
-
-        - Please wrap the axios call into a
-
-  ```js
-  try {
-    let result = await axios.post(...);
-    if (result.status === ...) ...
-  } catch (error) {
-    this.throwGeneralAxiosError(error);
-  }
-  ```
-
-  - `server/notification.js` is where the backend of the notification provider
-    needs to be registered. _If you have an idea how we can skip this step, we
-    would love to hear about it ^^_
-
-  - `src/components/NotificationDialog.vue` you need to decide if the provider
-    is a regional or a global one and add it with a name to the respective list
-
-  - `src/components/notifications/PROVIDER_NAME.vue` is where the frontend of
-    each provider lives. Please make sure that you have:
-
-        - used `HiddenInput` for secret credentials
-        - included all the necessary helptexts/placeholder/.. to make sure the
-
-  notification provider is simple to setup for new users. - include all
-  translations (`{{ $t("Translation key") }}`,
-  [`i18n-t keypath="Translation key">`](https://vue-i18n.intlify.dev/guide/advanced/component.html))
-  in `src/lang/en.json` to enable our translators to translate this
-  - `src/components/notifications/index.js` is where the frontend of the
-    provider needs to be registered. _If you have an idea how we can skip this
-    step, we would love to hear about it ^^_
-
-  Offering notifications is close to the core of what we are as an uptime
-  monitor. Therefore, making sure that they work is also really important.
-  Because testing notification providers is quite time intensive, we mostly
-  offload this onto the person contributing a notification provider.
-
-  To make sure you have tested the notification provider, please include
-  screenshots of the following events in the pull-request description:
-  - `UP`/`DOWN`
-  - Certificate Expiry via <https://expired.badssl.com/>
-  - Domain Expiry via <https://google.com/> and a larger time set
-  - Testing (the test button on the notification provider setup page)
-
-  <br/>
-
-  Using the following way to format this is encouraged:
-
-  ```md
-  | Event              | Before                | After                |
-  | ------------------ | --------------------- | -------------------- |
-  | `UP`               | ![Before](image-link) | ![After](image-link) |
-  | `DOWN`             | ![Before](image-link) | ![After](image-link) |
-  | Certificate-expiry | ![Before](image-link) | ![After](image-link) |
-  | Domain-expiry      | ![Before](image-link) | ![After](image-link) |
-  | Testing            | ![Before](image-link) | ![After](image-link) |
-  ```
-
-  <sub>Because maintainer time is precious, junior maintainers may merge
-  uncontroversial PRs in this area.</sub>
-
-  </p>
-  </details>
-
-- <details><summary><b>New Monitoring Types</b> (click to expand)</summary>
-  <p>
-
-  To set up a new notification provider these files need to be modified/created:
-  - `server/monitor-types/MONITORING_TYPE.js` is the core of each monitor.
-    The `async check(...)`-function should:
-    - in the happy-path: set `heartbeat.msg` to a successful message and set `heartbeat.status = UP`
-    - in the unhappy-path: throw an `Error` for each fault that is detected with an actionable error message.
-    - NEVER set `heartbeat.status = DOWN` unless you want to explicitly ignore retries.
-
-  - `server/uptime-kuma-server.js` is where the monitoring backend needs to be
-    registered. _If you have an idea how we can skip this step, we would love to
-    hear about it ^^_
-
-  - `src/pages/EditMonitor.vue` is the shared frontend users interact with.
-    Please make sure that you have: - used `HiddenInput` for secret
-    credentials - included all the necessary helptexts/placeholder/.. to make
-    sure the notification provider is simple to setup for new users. - include
-    all translations (`{{ $t("Translation key") }}`,
-    [`<i18n-t keypath="Translation key">`](https://vue-i18n.intlify.dev/guide/advanced/component.html))
-    in `src/lang/en.json` to enable our translators to translate this
-
-  <sub>Because maintainer time is precious, junior maintainers may merge
-  uncontroversial PRs in this area.</sub>
-
-  </p>
-  </details>
-
-- <details><summary><b>New Features / Major Changes / Breaking Bugfixes</b> (click to expand)</summary>
-  <p>
-
-  be sure to **create an empty draft pull request or open an issue, so we can
-  have a discussion first**.
-  This is especially important for large pull requests or when you don't know if it will be merged or not.
-  When adding new features, please also add tests to ensure your changes work as expected and to prevent future regressions.
-
-  <sub>Because of the large impact of this work, only senior maintainers may
-  merge PRs in this area. </sub>
-
-  </p>
-  </details>
-
-- <details><summary><b>As a First-Time Contributor</b> (click to expand)</summary>
-  <p>
-
-  Contributing is easy and fun. We will guide you through the process:
-  1. **Fork** the [Uptime-Kuma repository](https://github.com/louislam/uptime-kuma/) and **clone** it to your local machine.
-  2. **Create a new branch** for your changes (e.g., `signal-notification-provider`).
-  3. **Make your changes** and **commit** them with a clear message.
-  4. **Push** your changes to your forked repository.
-  5. **Open a pull request** to the `master` branch of the Uptime Kuma repository.
-     - For large changes, please open a **draft pull request** first to discuss the changes with the maintainers.
-  6. **Provide a clear and concise description** of the changes you've made and link any related issues.
-  7. **Complete the PR checklist** and make sure all CI checks pass.
-  8. **Request a review** when your pull request is ready.
-
-  ## When Can You Change the PR Status to "Ready for Review"?
-
-  A PR should remain in **draft status** until all tasks are completed.
-  Only change the status to **Ready for Review** when:
-  - You have implemented all planned changes.
-  - Your code is fully tested and ready for review.
-  - You have updated or created the necessary tests.
-  - You have verified that CI/CD checks pass successfully.
-
-  A volunteer maintainer will review your PR as soon as possible.
-  You can help us by reviewing other PRs or taking a look at open issues.
-
-## The following rules are essential for making your PR mergeable
-
-- Merging multiple issues by a huge PR is more difficult to review and causes
-  conflicts with other PRs. Please
-  - (if possible) **create one PR for one issue** or
-  - (if not possible) **explain which issues a PR addresses and why this PR
-    should not be broken apart**
-
-- Make sure your **PR passes our continuous integration**. PRs will not be
-  merged unless all CI-Checks are green.
-- **Breaking changes** (unless for a good reason and discussed beforehand) will
-  not get merged / not get merged quickly. Such changes require a major version
-  release.
-- **Test your code** before submitting a PR. Buggy PRs will not be merged.
-- Make sure the **UI/UX is close to Uptime Kuma**.
-- **Think about the maintainability**: Don't add functionality that is
-  completely **out of scope**. Keep in mind that we need to be able to maintain
-  the functionality.
-- Don't modify or delete existing logic without a valid reason.
-- Don't convert existing code into other programming languages for no reason.
-
-### Continuous Integration
-
-All pull requests must pass our continuous integration checks. These checks include:
-
-- **Linting**: We use ESLint and Stylelint for code quality checks. You can run the linter locally with `npm run lint`.
-- **Formatting**: We use Prettier for code formatting. You can format your code with `npm run fmt` (or CI will do this for you)
-- **Testing**: We use Playwright for end-to-end tests and have a suite of backend tests. You can run the tests locally with `npm test`.
-
-I ([@louislam](https://github.com/louislam)) have the final say.
-If your pull request does not meet my expectations, I will reject it, no matter how much time
-you spent on it.
-
-We will assign your pull request to a [milestone](https://github.com/louislam/uptime-kuma/milestones), if we plan to review and merge it.
-
-Please don't rush or ask for an ETA.
-We have to understand the pull request, make sure it has no breaking changes and stick to the vision of this project, especially for large pull requests.
-
-## I'd Like to Work on an Issue. How Do I Do That?
-
-We have found that assigning people to issues is unnecessary management
-overhead. Instead, a short comment stating that you want to work on an issue is
-appreciated, as it saves time for other developers. If you encounter any
-problems during development, feel free to leave a comment describing what you
-are stuck on. We are here to help.
-
-## Project Style
-
-I personally do not like something that requires a lot of configuration before
-you can finally start the app. The goal is to make the Uptime Kuma installation
-as easy as installing a mobile app.
-
-- Easy to install for non-Docker users
-  - no native build dependency is needed (for `x86_64`/`armv7`/`arm64`)
-  - no extra configuration and
-  - no extra effort required to get it running
-
-- Single container for Docker users
-  - no complex docker-compose file
-  - mapping the volume and exposing the port should be the only requirements
-
-- Settings should be configurable in the frontend. Environment variables are
-  discouraged, unless it is related to startup such as `DATA_DIR`
 - Easy to use
 - The web UI styling should be consistent and nice
 
@@ -316,21 +108,22 @@ as easy as installing a mobile app.
 
 ## Tools
 
-- [`Node.js`](https://nodejs.org/) >= 20.4.0
+- [`Node.js`](https://nodejs.org/) >= 14
-- [`npm`](https://www.npmjs.com/) >= 9.3
+- [`npm`](https://www.npmjs.com/) >= 8.5
 - [`git`](https://git-scm.com/)
-- IDE that supports [`ESLint`](https://eslint.org/) and EditorConfig (I am using
+- IDE that supports [`ESLint`](https://eslint.org/) and EditorConfig (I am using [`IntelliJ IDEA`](https://www.jetbrains.com/idea/))
-  [`IntelliJ IDEA`](https://www.jetbrains.com/idea/))
+- A SQLite GUI tool (f.ex. [`SQLite Expert Personal`](https://www.sqliteexpert.com/download.html) or [`DBeaver Community`](https://dbeaver.io/download/))
-- A SQLite GUI tool (f.ex.
+
-  [`SQLite Expert Personal`](https://www.sqliteexpert.com/download.html) or
+### GitHub Codespace
-  [`DBeaver Community`](https://dbeaver.io/download/))
+
+If you don't want to setup an local environment, you can now develop on GitHub Codespace, read more:
+
+https://github.com/louislam/uptime-kuma/tree/master/.devcontainer
 
 ## Git Branches
 
-- `master`: 2.X.X development. If you want to add a new feature, your pull
+- `master`: 2.X.X development. If you want to add a new feature, your pull request should base on this.
-  request should base on this.
+- `1.23.X`: 1.23.X development. If you want to fix a bug for v1 and v2, your pull request should base on this.
-- `1.23.X`: 1.23.X development. If you want to fix a bug for v1 and v2, your
-  pull request should base on this.
 - All other branches are unused, outdated or for dev.
 
 ## Install Dependencies for Development
@@ -341,6 +134,8 @@ npm ci
 
 ## Dev Server
 
+(2022-04-26 Update)
+
 We can start the frontend dev server and the backend dev server in one command.
 
 Port `3000` and port `3001` will be used.
@@ -349,8 +144,7 @@ Port `3000` and port `3001` will be used.
 npm run dev
 ```
 
-But sometimes you may want to restart the server without restarting the
+But sometimes, you would like to restart the server, but not the frontend, you can run these commands in two terminals:
-frontend. In that case, you can run these commands in two terminals:
 
 ```bash
 npm run start-frontend-dev
@@ -361,55 +155,56 @@ npm run start-server-dev
 
 It binds to `0.0.0.0:3001` by default.
 
-The backend is an `express.js` server with `socket.io` integrated. It uses
+It is mainly a socket.io app + express.js.
-`socket.io` to communicate with clients, and most server logic is encapsulated
-in the `socket.io` handlers. `express.js` is also used to serve:
 
-- as an entry point for redirecting to a status page or the dashboard
+express.js is used for:
-- the frontend built files (`index.html`, `*.js`, `*.css`, etc.)
-- internal APIs of the status page
 
-### Structure in `/server/`
+- entry point such as redirecting to a status page or the dashboard
+- serving the frontend built files (index.html, .js and .css etc.)
+- serving internal APIs of the status page
 
-- `jobs/` (Jobs that are running in another process)
+### Structure in /server/
-- `model/` (Object model, auto-mapping to the database table name)
+
-- `modules/` (Modified 3rd-party modules)
+- jobs/ (Jobs that are running in another process)
-- `monitor_types/` (Monitor Types)
+- model/ (Object model, auto-mapping to the database table name)
-- `notification-providers/` (individual notification logic)
+- modules/ (Modified 3rd-party modules)
-- `routers/` (Express Routers)
+- monitor_types (Monitor Types)
-- `socket-handler/` (Socket.io Handlers)
+- notification-providers/ (individual notification logic)
-- `server.js` (Server entry point)
+- routers/ (Express Routers)
-- `uptime-kuma-server.js` (UptimeKumaServer class, main logic should be here,
+- socket-handler (Socket.io Handlers)
-  but some still in `server.js`)
+- server.js (Server entry point)
+- uptime-kuma-server.js (UptimeKumaServer class, main logic should be here, but some still in `server.js`)
 
 ## Frontend Dev Server
 
-It binds to `0.0.0.0:3000` by default. The frontend dev server is used for
+It binds to `0.0.0.0:3000` by default. The frontend dev server is used for development only.
-development only.
 
-For production, it is not used. It will be compiled to `dist` directory instead via `npm run build`.
+For production, it is not used. It will be compiled to `dist` directory instead.
 
 You can use Vue.js devtools Chrome extension for debugging.
 
+### Build the frontend
+
+```bash
+npm run build
+```
+
 ### Frontend Details
 
-Uptime Kuma Frontend is a single page application (SPA). Most paths are handled
+Uptime Kuma Frontend is a single page application (SPA). Most paths are handled by Vue Router.
-by Vue Router.
 
 The router is in `src/router.js`
 
-Most data in the frontend is stored at the root level, even though the router can navigate to different pages.
+As you can see, most data in the frontend is stored at the root level, even though you changed the current router to any other pages.
 
 The data and socket logic are in `src/mixins/socket.js`.
 
 ## Database Migration
 
-See: <https://github.com/louislam/uptime-kuma/tree/master/db/knex_migrations>
+See: https://github.com/louislam/uptime-kuma/tree/master/db/knex_migrations
 
 ## Unit Test
 
-To run unit tests, use the following command:
-
 ```bash
 npm run build
 npm test
@@ -417,151 +212,132 @@ npm test
 
 ## Dependencies
 
-Both frontend and backend share the same `package.json`.
+Both frontend and backend share the same package.json. However, the frontend dependencies are eventually not used in the production environment, because it is usually also baked into dist files. So:
-However, the frontend dependencies are eventually not used in the production environment, because it
-is usually also baked into `dist` files. So:
 
 - Frontend dependencies = "devDependencies"
-  - Examples: - `vue`, `chart.js`
+  - Examples: vue, chart.js
 - Backend dependencies = "dependencies"
-  - Examples: `socket.io`, `sqlite3`
+  - Examples: socket.io, sqlite3
 - Development dependencies = "devDependencies"
-  - Examples: `eslint`, `sass`
+  - Examples: eslint, sass
 
 ### Update Dependencies
 
-Since previously updating Vite 2.5.10 to 2.6.0 broke the application completely,
+Since previously updating Vite 2.5.10 to 2.6.0 broke the application completely, from now on, it should update the patch release version only.
-from now on, it should update the patch release version only.
 
 Patch release = the third digit ([Semantic Versioning](https://semver.org/))
 
-If for security / bug / other reasons, a library must be updated, breaking
+If for security / bug / other reasons, a library must be updated, breaking changes need to be checked by the person proposing the change.
-changes need to be checked by the person proposing the change.
+
+## Translations
+
+Please add **all** the strings which are translatable to `src/lang/en.json` (If translation keys are omitted, they can not be translated).
+
+**Don't include any other languages in your initial Pull-Request** (even if this is your mother tongue), to avoid merge-conflicts between weblate and `master`.
+The translations can then (after merging a PR into `master`) be translated by awesome people donating their language skills.
+
+If you want to help by translating Uptime Kuma into your language, please visit the [instructions on how to translate using weblate](https://github.com/louislam/uptime-kuma/blob/master/src/lang/README.md).
 
 ## Spelling & Grammar
 
-Feel free to correct the spelling and grammar in the documentation or code.
+Feel free to correct the grammar in the documentation or code.
-English is not the native language of the maintainers.
+My mother language is not English and my grammar is not that great.
 
 ## Wiki
 
-Since there is no way to make a pull request to the wiki, I have set up another
+Since there is no way to make a pull request to wiki's repo, I have set up another repo to do that.
-repo to do that.
 
-<https://github.com/louislam/uptime-kuma-wiki>
+https://github.com/louislam/uptime-kuma-wiki
+
+## Docker
+
+### Arch
+
+- amd64
+- arm64
+- armv7
+
+### Docker Tags
+
+#### v2
+
+- `2`, `latest-2`: v2 with full features such as Chromium and bundled MariaDB
+- `2.x.x`
+- `2-slim`: v2 with basic features
+- `2.x.x-slim`
+- `beta2`: Latest beta build
+- `2.x.x-beta.x`
+- `nightly2`: Dev build
+- `base2`: Basic Debian setup without Uptime Kuma source code (Full features)
+- `base2-slim`: Basic Debian setup without Uptime Kuma source code
+- `pr-test2`: For testing pull request without setting up a local environment
+
+#### v1
+
+- `1`, `latest`, `1-debian`, `debian`: Latest version of v1
+- `1.x.x`, `1.x.x-debian`
+- `1.x.x-beta.x`: Beta build
+- `beta`: Latest beta build
+- `nightly`: Dev build
+- `base-debian`: Basic Debian setup without Uptime Kuma source code
+- `pr-test`: For testing pull request without setting up a local environment
+- `base-alpine`: (Deprecated) Basic Alpine setup without Uptime Kuma source code
+- `1-alpine`, `alpine`: (Deprecated)
+- `1.x.x-alpine`: (Deprecated)
 
 ## Maintainer
 
-### What is a maintainer and what are their roles?
+Check the latest issues and pull requests:
+https://github.com/louislam/uptime-kuma/issues?q=sort%3Aupdated-desc
 
-This project has multiple maintainers who specialise in different areas.
+### Release Procedures
-Currently, there are 3 maintainers:
 
-| Person            | Role              | Main Area        |
+1. Draft a release note
-| ----------------- | ----------------- | ---------------- |
+2. Make sure the repo is cleared
-| `@louislam`       | senior maintainer | major features   |
+3. If the healthcheck is updated, remember to re-compile it: `npm run build-docker-builder-go`
-| `@chakflying`     | junior maintainer | fixing bugs      |
+4. `npm run release-final` with env vars: `VERSION` and `GITHUB_TOKEN`
-| `@commanderstorm` | junior maintainer | issue-management |
+5. Wait until the `Press any key to continue`
+6. `git push`
+7. Publish the release note as 1.X.X
+8. Press any key to continue
+9. Deploy to the demo server: `npm run deploy-demo-server`
 
-### Procedures
+Checking:
 
-We have a few procedures we follow. These are documented here:
+- Check all tags is fine on https://hub.docker.com/r/louislam/uptime-kuma/tags
+- Try the Docker image with tag 1.X.X (Clean install / amd64 / arm64 / armv7)
+- Try clean installation with Node.js
 
-- <details><summary><b>Set up a Docker Builder</b> (click to expand)</summary>
+### Release Beta Procedures
-  <p>
-  - amd64, armv7 using local.
-  - arm64 using remote arm64 cpu, as the emulator is too slow and can no longer
-    pass the `npm ci` command.
-  1. Add the public key to the remote server.
-  2. Add the remote context. The remote machine must be arm64 and installed
-     Docker CE.
 
-  ```bash
+1. Draft a release note, check "This is a pre-release"
-  docker context create oracle-arm64-jp --docker "host=ssh://root@100.107.174.88"
+2. Make sure the repo is cleared
-  ```
+3. `npm run release-beta` with env vars: `VERSION` and `GITHUB_TOKEN`
+4. Wait until the `Press any key to continue`
+5. Publish the release note as 1.X.X-beta.X
+6. Press any key to continue
 
-  3. Create a new builder.
+### Release Wiki
 
-     ```bash
+#### Setup Repo
-     docker buildx create --name kuma-builder --platform linux/amd64,linux/arm/v7
-     docker buildx use kuma-builder
-     docker buildx inspect --bootstrap
-     ```
 
-  4. Append the remote context to the builder.
+```bash
+git clone https://github.com/louislam/uptime-kuma-wiki.git
+cd uptime-kuma-wiki
+git remote add production https://github.com/louislam/uptime-kuma.wiki.git
+```
 
-     ```bash
+#### Push to Production Wiki
-     docker buildx create --append --name kuma-builder --platform linux/arm64 oracle-arm64-jp
-     ```
 
-  5. Verify the builder and check if the builder is using `kuma-builder`.
+```bash
-     `docker buildx inspect kuma-builder docker buildx ls`
+git pull
+git push production master
+```
 
-  </p>
+## Useful Commands
-  </details>
 
-- <details><summary><b>Release</b> (click to expand)</summary>
+Change the base of a pull request such as `master` to `1.23.X`
-  <p>
-  1. Draft a release note
-  2. Make sure the repo is cleared
-  3. If the healthcheck is updated, remember to re-compile it:
-     `npm run build-docker-builder-go`
-  4. `npm run release-final` with env vars: `VERSION` and `GITHUB_TOKEN`
-  5. Wait until the `Press any key to continue`
-  6. `git push`
-  7. Publish the release note as `1.X.X`
-  8. Press any key to continue
-  9. Deploy to the demo server: `npm run deploy-demo-server`
 
-  These Items need to be checked:
+```bash
-  - [ ] Check all tags is fine on
+git rebase --onto <new parent> <old parent>
-        <https://hub.docker.com/r/louislam/uptime-kuma/tags>
+```
-  - [ ] Try the Docker image with tag 1.X.X (Clean install / amd64 / arm64 /
-        armv7)
-  - [ ] Try clean installation with Node.js
-
-  </p>
-  </details>
-
-- <details><summary><b>Release Beta</b> (click to expand)</summary>
-  <p>
-  1. Draft a release note, check `This is a pre-release`
-  2. Make sure the repo is cleared
-  3. `npm run release-beta` with env vars: `VERSION` and `GITHUB_TOKEN`
-  4. Wait until the `Press any key to continue`
-  5. Publish the release note as `1.X.X-beta.X`
-  6. Press any key to continue
-
-  </p>
-  </details>
-
-- <details><summary><b>Release Wiki</b> (click to expand)</summary>
-  <p>
-
-  **Setup Repo**
-
-  ```bash
-  git clone https://github.com/louislam/uptime-kuma-wiki.git
-  cd uptime-kuma-wiki
-  git remote add production https://github.com/louislam/uptime-kuma.wiki.git
-  ```
-
-  **Push to Production Wiki**
-
-  ```bash
-  git pull
-  git push production master
-  ```
-
-  </p>
-  </details>
-
-- <details><summary>Change the base of a pull request such as <code>master</code> to <code>1.23.X</code> (click to expand)</summary>
-  <p>
-
-  ```bash
-  git rebase --onto <new parent> <old parent>
-  ```
-
-  </p>
-  </details>

README.md

@@ -1,29 +1,29 @@
 <div align="center" width="100%">
-    <img src="./public/icon.svg" width="128" alt="Uptime Kuma Logo" />
+    <img src="./public/icon.svg" width="128" alt="" />
 </div>
 
 # Uptime Kuma
 
 Uptime Kuma is an easy-to-use self-hosted monitoring tool.
 
-<a target="_blank" href="https://github.com/louislam/uptime-kuma"><img src="https://img.shields.io/github/stars/louislam/uptime-kuma?style=flat" /></a> <a target="_blank" href="https://hub.docker.com/r/louislam/uptime-kuma"><img src="https://img.shields.io/docker/pulls/louislam/uptime-kuma" /></a> <a target="_blank" href="https://hub.docker.com/r/louislam/uptime-kuma"><img src="https://img.shields.io/docker/v/louislam/uptime-kuma/2?label=docker%20image%20ver." /></a> <a target="_blank" href="https://github.com/louislam/uptime-kuma"><img src="https://img.shields.io/github/last-commit/louislam/uptime-kuma" /></a> <a target="_blank" href="https://opencollective.com/uptime-kuma"><img src="https://opencollective.com/uptime-kuma/total/badge.svg?label=Open%20Collective%20Backers&color=brightgreen" /></a>
+<a target="_blank" href="https://github.com/louislam/uptime-kuma"><img src="https://img.shields.io/github/stars/louislam/uptime-kuma" /></a> <a target="_blank" href="https://hub.docker.com/r/louislam/uptime-kuma"><img src="https://img.shields.io/docker/pulls/louislam/uptime-kuma" /></a> <a target="_blank" href="https://hub.docker.com/r/louislam/uptime-kuma"><img src="https://img.shields.io/docker/v/louislam/uptime-kuma/latest?label=docker%20image%20ver." /></a> <a target="_blank" href="https://github.com/louislam/uptime-kuma"><img src="https://img.shields.io/github/last-commit/louislam/uptime-kuma" /></a>  <a target="_blank" href="https://opencollective.com/uptime-kuma"><img src="https://opencollective.com/uptime-kuma/total/badge.svg?label=Open%20Collective%20Backers&color=brightgreen" /></a>
 [![GitHub Sponsors](https://img.shields.io/github/sponsors/louislam?label=GitHub%20Sponsors)](https://github.com/sponsors/louislam) <a href="https://weblate.kuma.pet/projects/uptime-kuma/uptime-kuma/">
 <img src="https://weblate.kuma.pet/widgets/uptime-kuma/-/svg-badge.svg" alt="Translation status" />
 </a>
 
-<img src="https://user-images.githubusercontent.com/1336778/212262296-e6205815-ad62-488c-83ec-a5b0d0689f7c.jpg" width="700" alt="Uptime Kuma Dashboard Screenshot" />
+<img src="https://user-images.githubusercontent.com/1336778/212262296-e6205815-ad62-488c-83ec-a5b0d0689f7c.jpg" width="700" alt="" />
 
 ## 🥔 Live Demo
 
 Try it!
 
-Demo Server (Location: Frankfurt - Germany): <https://demo.kuma.pet/start-demo>
+- Tokyo Demo Server: https://demo.uptime.kuma.pet (Sponsored by [Uptime Kuma Sponsors](https://github.com/louislam/uptime-kuma#%EF%B8%8F-sponsors))
 
-It is a temporary live demo, all data will be deleted after 10 minutes. Sponsored by [Uptime Kuma Sponsors](https://github.com/louislam/uptime-kuma#%EF%B8%8F-sponsors).
+It is a temporary live demo, all data will be deleted after 10 minutes. Use the one that is closer to you, but I suggest that you should install and try it out for the best demo experience.
 
 ## ⭐ Features
 
-- Monitoring uptime for HTTP(s) / TCP / HTTP(s) Keyword / HTTP(s) Json Query / Websocket / Ping / DNS Record / Push / Steam Game Server / Docker Containers
+- Monitoring uptime for HTTP(s) / TCP / HTTP(s) Keyword / HTTP(s) Json Query / Ping / DNS Record / Push / Steam Game Server / Docker Containers
 - Fancy, Reactive, Fast UI/UX
 - Notifications via Telegram, Discord, Gotify, Slack, Pushover, Email (SMTP), and [90+ notification services, click here for the full list](https://github.com/louislam/uptime-kuma/tree/master/src/components/notifications)
 - 20-second intervals
@@ -37,48 +37,33 @@ It is a temporary live demo, all data will be deleted after 10 minutes. Sponsore
 
 ## 🔧 How to Install
 
-### 🐳 Docker Compose
+### 🐳 Docker
 
 ```bash
-mkdir uptime-kuma
+docker run -d --restart=always -p 3001:3001 -v uptime-kuma:/app/data --name uptime-kuma louislam/uptime-kuma:1
-cd uptime-kuma
-curl -o compose.yaml https://raw.githubusercontent.com/louislam/uptime-kuma/master/compose.yaml
-docker compose up -d
 ```
 
-Uptime Kuma is now running on all network interfaces (e.g. http://localhost:3001 or http://your-ip:3001).
+⚠️ Please use a **local volume** only. Other types such as NFS are not supported.
 
-> [!WARNING]
+Uptime Kuma is now running on http://localhost:3001
-> File Systems like **NFS** (Network File System) are **NOT** supported. Please map to a local directory or volume.
-
-### 🐳 Docker Command
-
-```bash
-docker run -d --restart=always -p 3001:3001 -v uptime-kuma:/app/data --name uptime-kuma louislam/uptime-kuma:2
-```
-
-Uptime Kuma is now running on all network interfaces (e.g. http://localhost:3001 or http://your-ip:3001).
-
-If you want to limit exposure to localhost only:
-
-```bash
-docker run ... -p 127.0.0.1:3001:3001 ...
-```
 
 ### 💪🏻 Non-Docker
 
 Requirements:
 
 - Platform
-  - ✅ Major Linux distros such as Debian, Ubuntu, Fedora and ArchLinux etc.
+  - ✅ Major Linux distros such as Debian, Ubuntu, CentOS, Fedora and ArchLinux etc.
   - ✅ Windows 10 (x64), Windows Server 2012 R2 (x64) or higher
-  - ❌ FreeBSD / OpenBSD / NetBSD
   - ❌ Replit / Heroku
-- [Node.js](https://nodejs.org/en/download/) >= 20.4
+- [Node.js](https://nodejs.org/en/download/) 14 / 16 / 18 / 20.4
+- [npm](https://docs.npmjs.com/cli/) >= 7
 - [Git](https://git-scm.com/downloads)
 - [pm2](https://pm2.keymetrics.io/) - For running Uptime Kuma in the background
 
 ```bash
+# Update your npm
+npm install npm@9 -g
+
 git clone https://github.com/louislam/uptime-kuma.git
 cd uptime-kuma
 npm run setup
@@ -94,7 +79,7 @@ npm install pm2 -g && pm2 install pm2-logrotate
 pm2 start server/server.js --name uptime-kuma
 ```
 
-Uptime Kuma is now running on all network interfaces (e.g. http://localhost:3001 or http://your-ip:3001).
+Uptime Kuma is now running on http://localhost:3001
 
 More useful PM2 Commands
 
@@ -103,91 +88,94 @@ More useful PM2 Commands
 pm2 monit
 
 # If you want to add it to startup
-pm2 startup && pm2 save
+pm2 save && pm2 startup
 ```
 
+### Windows Portable (x64)
+
+https://github.com/louislam/uptime-kuma/releases/download/1.23.1/uptime-kuma-windows-x64-portable-1.23.1-2.zip
+
 ### Advanced Installation
 
 If you need more options or need to browse via a reverse proxy, please read:
 
-<https://github.com/louislam/uptime-kuma/wiki/%F0%9F%94%A7-How-to-Install>
+https://github.com/louislam/uptime-kuma/wiki/%F0%9F%94%A7-How-to-Install
 
 ## 🆙 How to Update
 
 Please read:
 
-<https://github.com/louislam/uptime-kuma/wiki/%F0%9F%86%99-How-to-Update>
+https://github.com/louislam/uptime-kuma/wiki/%F0%9F%86%99-How-to-Update
 
 ## 🆕 What's Next?
 
 I will assign requests/issues to the next milestone.
 
-<https://github.com/louislam/uptime-kuma/milestones>
+https://github.com/louislam/uptime-kuma/milestones
+
+Project Plan:
+
+https://github.com/users/louislam/projects/4/views/1
 
 ## ❤️ Sponsors
 
 Thank you so much! (GitHub Sponsors will be updated manually. OpenCollective sponsors will be updated automatically, the list will be cached by GitHub though. It may need some time to be updated)
 
-<img src="https://uptime.kuma.pet/sponsors?v=6" alt="Uptime Kuma Sponsors" />
+<img src="https://uptime.kuma.pet/sponsors?v=6" alt />
 
 ## 🖼 More Screenshots
 
 Light Mode:
 
-<img src="https://uptime.kuma.pet/img/light.jpg" width="512" alt="Uptime Kuma Light Mode Screenshot of how the Dashboard looks" />
+<img src="https://uptime.kuma.pet/img/light.jpg" width="512" alt="" />
 
 Status Page:
 
-<img src="https://user-images.githubusercontent.com/1336778/134628766-a3fe0981-0926-4285-ab46-891a21c3e4cb.png" width="512" alt="Uptime Kuma Status Page Screenshot" />
+<img src="https://user-images.githubusercontent.com/1336778/134628766-a3fe0981-0926-4285-ab46-891a21c3e4cb.png" width="512" alt="" />
 
 Settings Page:
 
-<img src="https://louislam.net/uptimekuma/2.jpg" width="400" alt="Uptime Kuma Settings Page Screenshot" />
+<img src="https://louislam.net/uptimekuma/2.jpg" width="400" alt="" />
 
 Telegram Notification Sample:
 
-<img src="https://louislam.net/uptimekuma/3.jpg" width="400" alt="Uptime Kuma Telegram Notification Sample Screenshot" />
+<img src="https://louislam.net/uptimekuma/3.jpg" width="400" alt="" />
 
 ## Motivation
 
-- I was looking for a self-hosted monitoring tool like "Uptime Robot", but it is hard to find a suitable one. One of the closest ones is statping. Unfortunately, it is not stable and no longer maintained.
+- I was looking for a self-hosted monitoring tool like "Uptime Robot", but it is hard to find a suitable one. One of the close ones is statping. Unfortunately, it is not stable and no longer maintained.
-- Wanted to build a fancy UI.
+- Want to build a fancy UI.
 - Learn Vue 3 and vite.js.
 - Show the power of Bootstrap 5.
-- Try to use WebSocket with SPA instead of a REST API.
+- Try to use WebSocket with SPA instead of REST API.
 - Deploy my first Docker image to Docker Hub.
 
-If you love this project, please consider giving it a ⭐.
+If you love this project, please consider giving me a ⭐.
 
 ## 🗣️ Discussion / Ask for Help
 
-⚠️ For any general or technical questions, please don't send me an email, as I am unable to provide support in that manner. I will not respond if you ask questions there.
+⚠️ For any general or technical questions, please don't send me an email, as I am unable to provide support in that manner. I will not respond if you asked such questions.
 
-I recommend using Google, GitHub Issues, or Uptime Kuma's subreddit for finding answers to your question. If you cannot find the information you need, feel free to ask:
+I recommend using Google, GitHub Issues, or Uptime Kuma's Subreddit for finding answers to your question. If you cannot find the information you need, feel free to ask:
 
 - [GitHub Issues](https://github.com/louislam/uptime-kuma/issues)
-- [Subreddit (r/UptimeKuma)](https://www.reddit.com/r/UptimeKuma/)
+- [Subreddit r/Uptime kuma](https://www.reddit.com/r/UptimeKuma/)
 
-My Reddit account: [u/louislamlam](https://reddit.com/u/louislamlam)
+My Reddit account: [u/louislamlam](https://reddit.com/u/louislamlam).
-You can mention me if you ask a question on the subreddit.
+You can mention me if you ask a question on Reddit.
 
-## Contributions
+## Contribute
-
-### Create Pull Requests
-
-Pull requests are awesome.
-To keep reviews fast and effective, please make sure you’ve [read our pull request guidelines](https://github.com/louislam/uptime-kuma/blob/master/CONTRIBUTING.md#can-i-create-a-pull-request-for-uptime-kuma).
 
 ### Test Pull Requests
 
 There are a lot of pull requests right now, but I don't have time to test them all.
 
 If you want to help, you can check this:
-<https://github.com/louislam/uptime-kuma/wiki/Test-Pull-Requests>
+https://github.com/louislam/uptime-kuma/wiki/Test-Pull-Requests
 
 ### Test Beta Version
 
-Check out the latest beta release here: <https://github.com/louislam/uptime-kuma/releases>
+Check out the latest beta release here: https://github.com/louislam/uptime-kuma/releases
 
 ### Bug Reports / Feature Requests
 
@@ -200,4 +188,8 @@ If you want to translate Uptime Kuma into your language, please visit [Weblate R
 ### Spelling & Grammar
 
 Feel free to correct the grammar in the documentation or code.
-My mother language is not English and my grammar is not that great.
+My mother language is not english and my grammar is not that great.
+
+### Create Pull Requests
+
+If you want to modify Uptime Kuma, please read this guide and follow the rules here: https://github.com/louislam/uptime-kuma/blob/master/CONTRIBUTING.md

SECURITY.md

@@ -2,42 +2,29 @@
 
 ## Reporting a Vulnerability
 
-1. Please report security issues to
+1. Please report security issues to https://github.com/louislam/uptime-kuma/security/advisories/new.
-   <https://github.com/louislam/uptime-kuma/security/advisories/new>.
+1. Please also create an empty security issue to alert me, as GitHub Advisories do not send a notification, I probably will miss it without this. https://github.com/louislam/uptime-kuma/issues/new?assignees=&labels=help&template=security.md
-2. Please also create an empty security issue to alert me, as GitHub Advisories
-   do not send a notification, I probably will miss it without this.
-   <https://github.com/louislam/uptime-kuma/issues/new?assignees=&labels=help&template=security.md>
 
-- Do not report any upstream dependency issues / scan result by any tools. It will be closed immediately without explanations. Unless you have PoC to prove that the upstream issue affected Uptime Kuma.
+Do not use the public issue tracker or discuss it in public as it will cause more damage.
-- Do not use the public issue tracker or discuss it in public as it will cause
-  more damage.
 
 ## Do you accept other 3rd-party bug bounty platforms?
 
-At this moment, I DO NOT accept other bug bounty platforms, because I am not
+At this moment, I DO NOT accept other bug bounty platforms, because I am not familiar with these platforms and someone has tried to send a phishing link to me by doing this already. To minimize my own risk, please report through GitHub Advisories only. I will ignore all 3rd-party bug bounty platforms emails.
-familiar with these platforms and someone has tried to send a phishing link to
-me by doing this already. To minimize my own risk, please report through GitHub
-Advisories only. I will ignore all 3rd-party bug bounty platforms emails.
 
 ## Supported Versions
 
 ### Uptime Kuma Versions
 
-You should use or upgrade to the latest version of Uptime Kuma.
+You should use or upgrade to the latest version of Uptime Kuma. All `1.X.X` versions are upgradable to the latest version.
-All versions are upgradable to the latest version.
 
 ### Upgradable Docker Tags
 
-| Tag             | Supported                                                                             |
+| Tag | Supported          |
-| --------------- | ------------------------------------------------------------------------------------- |
+| ------- | ------------------ |
-| 2               | :white_check_mark:                                                                    |
+| 1 | :white_check_mark: |
-| 2-slim          | :white_check_mark:                                                                    |
+| 1-debian | :white_check_mark: |
-| next            | :white_check_mark:                                                                    |
+| latest | :white_check_mark: |
-| next-slim       | :white_check_mark:                                                                    |
+| debian | :white_check_mark: |
-| 2-rootless      | :white_check_mark:                                                                    |
+| 1-alpine | ⚠️ Deprecated |
-| 2-slim-rootless | :white_check_mark:                                                                    |
+| alpine | ⚠️ Deprecated |
-| 1               | [⚠️ Deprecated](https://github.com/louislam/uptime-kuma/wiki/Migration-From-v1-To-v2) |
+| All other tags  | ❌ |
-| 1-debian        | [⚠️ Deprecated](https://github.com/louislam/uptime-kuma/wiki/Migration-From-v1-To-v2) |
-| latest          | [⚠️ Deprecated](https://github.com/louislam/uptime-kuma/wiki/Migration-From-v1-To-v2) |
-| debian          | [⚠️ Deprecated](https://github.com/louislam/uptime-kuma/wiki/Migration-From-v1-To-v2) |
-| All other tags  | ❌                                                                                    |

babel.config.js

@@ -0,0 +1,7 @@
+const config = {};
+
+if (process.env.TEST_FRONTEND) {
+    config.presets = [ "@babel/preset-env" ];
+}
+
+module.exports = config;

compose.yaml

@@ -1,9 +0,0 @@
-services:
-  uptime-kuma:
-    image: louislam/uptime-kuma:2
-    restart: unless-stopped
-    volumes:
-      - ./data:/app/data
-    ports:
-      # <Host Port>:<Container Port>
-      - "3001:3001"

config/cypress.config.js

@@ -0,0 +1,28 @@
+const { defineConfig } = require("cypress");
+
+module.exports = defineConfig({
+    projectId: "vyjuem",
+    e2e: {
+        experimentalStudio: true,
+        setupNodeEvents(on, config) {
+
+        },
+        fixturesFolder: "test/cypress/fixtures",
+        screenshotsFolder: "test/cypress/screenshots",
+        videosFolder: "test/cypress/videos",
+        downloadsFolder: "test/cypress/downloads",
+        supportFile: "test/cypress/support/e2e.js",
+        baseUrl: "http://localhost:3002",
+        defaultCommandTimeout: 10000,
+        pageLoadTimeout: 60000,
+        viewportWidth: 1920,
+        viewportHeight: 1080,
+        specPattern: [
+            "test/cypress/e2e/setup.cy.js",
+            "test/cypress/e2e/**/*.js"
+        ],
+    },
+    env: {
+        baseUrl: "http://localhost:3002",
+    },
+});

config/cypress.frontend.config.js

@@ -0,0 +1,10 @@
+const { defineConfig } = require("cypress");
+
+module.exports = defineConfig({
+    e2e: {
+        supportFile: false,
+        specPattern: [
+            "test/cypress/unit/**/*.js"
+        ],
+    }
+});

config/jest-backend.config.js

@@ -0,0 +1,5 @@
+module.exports = {
+    "rootDir": "..",
+    "testRegex": "./test/backend.spec.js",
+};
+

config/playwright.config.js

@@ -1,67 +0,0 @@
-import { defineConfig, devices } from "@playwright/test";
-
-const port = 30001;
-export const url = `http://localhost:${port}`;
-
-export default defineConfig({
-    // Look for test files in the "tests" directory, relative to this configuration file.
-    testDir: "../test/e2e/specs",
-    outputDir: "../private/playwright-test-results",
-    fullyParallel: false,
-    locale: "en-US",
-
-    // Fail the build on CI if you accidentally left test.only in the source code.
-    forbidOnly: !!process.env.CI,
-
-    // Retry on CI only.
-    retries: process.env.CI ? 2 : 0,
-
-    // Opt out of parallel tests on CI.
-    workers: 1,
-
-    // Reporter to use
-    reporter: [
-        [
-            "html",
-            {
-                outputFolder: "../private/playwright-report",
-                open: "never",
-            },
-        ],
-    ],
-
-    use: {
-        // Base URL to use in actions like `await page.goto('/')`.
-        baseURL: url,
-
-        // Collect trace when retrying the failed test.
-        trace: "on-first-retry",
-    },
-
-    // Configure projects for major browsers.
-    projects: [
-        {
-            name: "run-once setup",
-            testMatch: /setup-process\.once\.js/,
-            use: { ...devices["Desktop Chrome"] },
-        },
-        {
-            name: "specs",
-            use: { ...devices["Desktop Chrome"] },
-            dependencies: ["run-once setup"],
-        },
-        /*
-        {
-            name: "firefox",
-            use: { browserName: "firefox" }
-        },*/
-    ],
-
-    // Run your local dev server before starting the tests.
-    webServer: {
-        command: `node extra/remove-playwright-test-data.js && cross-env NODE_ENV=development node server/server.js --port=${port} --data-dir=./data/playwright-test`,
-        url,
-        reuseExistingServer: false,
-        cwd: "../",
-    },
-});

config/vite.config.js

@@ -1,8 +1,9 @@
+import legacy from "@vitejs/plugin-legacy";
 import vue from "@vitejs/plugin-vue";
 import { defineConfig } from "vite";
 import visualizer from "rollup-plugin-visualizer";
 import viteCompression from "vite-plugin-compression";
-import { VitePWA } from "vite-plugin-pwa";
+import commonjs from "vite-plugin-commonjs";
 
 const postCssScss = require("postcss-scss");
 const postcssRTLCSS = require("postcss-rtlcss");
@@ -15,13 +16,19 @@ export default defineConfig({
         port: 3000,
     },
     define: {
-        FRONTEND_VERSION: JSON.stringify(process.env.npm_package_version),
+        "FRONTEND_VERSION": JSON.stringify(process.env.npm_package_version),
-        "process.env": {},
+        "DEVCONTAINER": JSON.stringify(process.env.DEVCONTAINER),
+        "GITHUB_CODESPACES_PORT_FORWARDING_DOMAIN": JSON.stringify(process.env.GITHUB_CODESPACES_PORT_FORWARDING_DOMAIN),
+        "CODESPACE_NAME": JSON.stringify(process.env.CODESPACE_NAME),
     },
     plugins: [
+        commonjs(),
         vue(),
+        legacy({
+            targets: [ "since 2015" ],
+        }),
         visualizer({
-            filename: "tmp/dist-stats.html",
+            filename: "tmp/dist-stats.html"
         }),
         viteCompression({
             algorithm: "gzip",
@@ -31,31 +38,24 @@ export default defineConfig({
             algorithm: "brotliCompress",
             filter: viteCompressionFilter,
         }),
-        VitePWA({
-            registerType: null,
-            srcDir: "src",
-            filename: "serviceWorker.ts",
-            strategies: "injectManifest",
-            injectManifest: {
-                maximumFileSizeToCacheInBytes: 3 * 1024 * 1024, // 3 MiB
-            },
-        }),
     ],
     css: {
         postcss: {
-            parser: postCssScss,
+            "parser": postCssScss,
-            map: false,
+            "map": false,
-            plugins: [postcssRTLCSS],
+            "plugins": [ postcssRTLCSS ]
-        },
+        }
     },
     build: {
         commonjsOptions: {
-            include: [/.js$/],
+            include: [ /.js$/ ],
         },
         rollupOptions: {
             output: {
-                manualChunks(id, { getModuleInfo, getModuleIds }) {},
+                manualChunks(id, { getModuleInfo, getModuleIds }) {
-            },
+
+                }
+            }
         },
-    },
+    }
 });

db/knex_init_db.js

@@ -39,7 +39,7 @@ async function createTables() {
         table.integer("user_id").unsigned().notNullable();
         table.string("protocol", 10).notNullable();
         table.string("host", 255).notNullable();
-        table.smallint("port").notNullable(); // TODO: Maybe a issue with MariaDB, need migration to int
+        table.smallint("port").notNullable();           // TODO: Maybe a issue with MariaDB, need migration to int
         table.boolean("auth").notNullable();
         table.string("username", 255).nullable();
         table.string("password", 255).nullable();
@@ -67,7 +67,10 @@ async function createTables() {
         table.increments("id");
         table.string("name", 150);
         table.boolean("active").notNullable().defaultTo(true);
-        table.integer("user_id").unsigned().references("id").inTable("user").onDelete("SET NULL").onUpdate("CASCADE");
+        table.integer("user_id").unsigned()
+            .references("id").inTable("user")
+            .onDelete("SET NULL")
+            .onUpdate("CASCADE");
         table.integer("interval").notNullable().defaultTo(20);
         table.text("url");
         table.string("type", 20);
@@ -80,7 +83,7 @@ async function createTables() {
         table.boolean("ignore_tls").notNullable().defaultTo(false);
         table.boolean("upside_down").notNullable().defaultTo(false);
         table.integer("maxredirects").notNullable().defaultTo(10);
-        table.text("accepted_statuscodes_json").notNullable().defaultTo('["200-299"]');
+        table.text("accepted_statuscodes_json").notNullable().defaultTo("[\"200-299\"]");
         table.string("dns_resolve_type", 5);
         table.string("dns_resolve_server", 255);
         table.string("dns_last_result", 255);
@@ -91,9 +94,11 @@ async function createTables() {
         table.text("headers").defaultTo(null);
         table.text("basic_auth_user").defaultTo(null);
         table.text("basic_auth_pass").defaultTo(null);
-        table.integer("docker_host").unsigned().references("id").inTable("docker_host");
+        table.integer("docker_host").unsigned()
+            .references("id").inTable("docker_host");
         table.string("docker_container", 255);
-        table.integer("proxy_id").unsigned().references("id").inTable("proxy");
+        table.integer("proxy_id").unsigned()
+            .references("id").inTable("proxy");
         table.boolean("expiry_notification").defaultTo(true);
         table.text("mqtt_topic");
         table.string("mqtt_success_message", 255);
@@ -125,12 +130,8 @@ async function createTables() {
     await knex.schema.createTable("heartbeat", (table) => {
         table.increments("id");
         table.boolean("important").notNullable().defaultTo(false);
-        table
+        table.integer("monitor_id").unsigned().notNullable()
-            .integer("monitor_id")
+            .references("id").inTable("monitor")
-            .unsigned()
-            .notNullable()
-            .references("id")
-            .inTable("monitor")
             .onDelete("CASCADE")
             .onUpdate("CASCADE");
         table.smallint("status").notNullable();
@@ -142,9 +143,9 @@ async function createTables() {
         table.integer("down_count").notNullable().defaultTo(0);
 
         table.index("important");
-        table.index(["monitor_id", "time"], "monitor_time_index");
+        table.index([ "monitor_id", "time" ], "monitor_time_index");
         table.index("monitor_id");
-        table.index(["monitor_id", "important", "time"], "monitor_important_time_index");
+        table.index([ "monitor_id", "important", "time" ], "monitor_important_time_index");
     });
 
     // incident
@@ -165,7 +166,10 @@ async function createTables() {
         table.increments("id");
         table.string("title", 150).notNullable();
         table.text("description").notNullable();
-        table.integer("user_id").unsigned().references("id").inTable("user").onDelete("SET NULL").onUpdate("CASCADE");
+        table.integer("user_id").unsigned()
+            .references("id").inTable("user")
+            .onDelete("SET NULL")
+            .onUpdate("CASCADE");
         table.boolean("active").notNullable().defaultTo(true);
         table.string("strategy", 50).notNullable().defaultTo("single");
         table.datetime("start_date");
@@ -177,7 +181,7 @@ async function createTables() {
         table.integer("interval_day");
 
         table.index("active");
-        table.index(["strategy", "active"], "manual_active");
+        table.index([ "strategy", "active" ], "manual_active");
         table.index("user_id", "maintenance_user_id");
     });
 
@@ -205,21 +209,13 @@ async function createTables() {
     await knex.schema.createTable("maintenance_status_page", (table) => {
         table.increments("id");
 
-        table
+        table.integer("status_page_id").unsigned().notNullable()
-            .integer("status_page_id")
+            .references("id").inTable("status_page")
-            .unsigned()
-            .notNullable()
-            .references("id")
-            .inTable("status_page")
             .onDelete("CASCADE")
             .onUpdate("CASCADE");
 
-        table
+        table.integer("maintenance_id").unsigned().notNullable()
-            .integer("maintenance_id")
+            .references("id").inTable("maintenance")
-            .unsigned()
-            .notNullable()
-            .references("id")
-            .inTable("maintenance")
             .onDelete("CASCADE")
             .onUpdate("CASCADE");
     });
@@ -227,12 +223,8 @@ async function createTables() {
     // maintenance_timeslot
     await knex.schema.createTable("maintenance_timeslot", (table) => {
         table.increments("id");
-        table
+        table.integer("maintenance_id").unsigned().notNullable()
-            .integer("maintenance_id")
+            .references("id").inTable("maintenance")
-            .unsigned()
-            .notNullable()
-            .references("id")
-            .inTable("maintenance")
             .onDelete("CASCADE")
             .onUpdate("CASCADE");
         table.datetime("start_date").notNullable();
@@ -240,51 +232,35 @@ async function createTables() {
         table.boolean("generated_next").defaultTo(false);
 
         table.index("maintenance_id");
-        table.index(["maintenance_id", "start_date", "end_date"], "active_timeslot_index");
+        table.index([ "maintenance_id", "start_date", "end_date" ], "active_timeslot_index");
         table.index("generated_next", "generated_next_index");
     });
 
     // monitor_group
     await knex.schema.createTable("monitor_group", (table) => {
         table.increments("id");
-        table
+        table.integer("monitor_id").unsigned().notNullable()
-            .integer("monitor_id")
+            .references("id").inTable("monitor")
-            .unsigned()
-            .notNullable()
-            .references("id")
-            .inTable("monitor")
             .onDelete("CASCADE")
             .onUpdate("CASCADE");
-        table
+        table.integer("group_id").unsigned().notNullable()
-            .integer("group_id")
+            .references("id").inTable("group")
-            .unsigned()
-            .notNullable()
-            .references("id")
-            .inTable("group")
             .onDelete("CASCADE")
             .onUpdate("CASCADE");
         table.integer("weight").notNullable().defaultTo(1000);
         table.boolean("send_url").notNullable().defaultTo(false);
 
-        table.index(["monitor_id", "group_id"], "fk");
+        table.index([ "monitor_id", "group_id" ], "fk");
     });
     // monitor_maintenance
     await knex.schema.createTable("monitor_maintenance", (table) => {
         table.increments("id");
-        table
+        table.integer("monitor_id").unsigned().notNullable()
-            .integer("monitor_id")
+            .references("id").inTable("monitor")
-            .unsigned()
-            .notNullable()
-            .references("id")
-            .inTable("monitor")
             .onDelete("CASCADE")
             .onUpdate("CASCADE");
-        table
+        table.integer("maintenance_id").unsigned().notNullable()
-            .integer("maintenance_id")
+            .references("id").inTable("maintenance")
-            .unsigned()
-            .notNullable()
-            .references("id")
-            .inTable("maintenance")
             .onDelete("CASCADE")
             .onUpdate("CASCADE");
 
@@ -299,30 +275,22 @@ async function createTables() {
         table.boolean("active").notNullable().defaultTo(true);
         table.integer("user_id").unsigned();
         table.boolean("is_default").notNullable().defaultTo(false);
-        table.text("config", "longtext");
+        table.text("config");
     });
 
     // monitor_notification
     await knex.schema.createTable("monitor_notification", (table) => {
-        table.increments("id").unsigned(); // TODO: no auto increment????
+        table.increments("id").unsigned();      // TODO: no auto increment????
-        table
+        table.integer("monitor_id").unsigned().notNullable()
-            .integer("monitor_id")
+            .references("id").inTable("monitor")
-            .unsigned()
-            .notNullable()
-            .references("id")
-            .inTable("monitor")
             .onDelete("CASCADE")
             .onUpdate("CASCADE");
-        table
+        table.integer("notification_id").unsigned().notNullable()
-            .integer("notification_id")
+            .references("id").inTable("notification")
-            .unsigned()
-            .notNullable()
-            .references("id")
-            .inTable("notification")
             .onDelete("CASCADE")
             .onUpdate("CASCADE");
 
-        table.index(["monitor_id", "notification_id"], "monitor_notification_index");
+        table.index([ "monitor_id", "notification_id" ], "monitor_notification_index");
     });
 
     // tag
@@ -336,20 +304,12 @@ async function createTables() {
     // monitor_tag
     await knex.schema.createTable("monitor_tag", (table) => {
         table.increments("id");
-        table
+        table.integer("monitor_id").unsigned().notNullable()
-            .integer("monitor_id")
+            .references("id").inTable("monitor")
-            .unsigned()
-            .notNullable()
-            .references("id")
-            .inTable("monitor")
             .onDelete("CASCADE")
             .onUpdate("CASCADE");
-        table
+        table.integer("tag_id").unsigned().notNullable()
-            .integer("tag_id")
+            .references("id").inTable("tag")
-            .unsigned()
-            .notNullable()
-            .references("id")
-            .inTable("tag")
             .onDelete("CASCADE")
             .onUpdate("CASCADE");
         table.text("value");
@@ -358,14 +318,7 @@ async function createTables() {
     // monitor_tls_info
     await knex.schema.createTable("monitor_tls_info", (table) => {
         table.increments("id");
-        table
+        table.integer("monitor_id").unsigned().notNullable();         //TODO: no fk ?
-            .integer("monitor_id")
-            .unsigned()
-            .notNullable()
-            .references("id")
-            .inTable("monitor")
-            .onDelete("CASCADE")
-            .onUpdate("CASCADE");
         table.text("info_json");
     });
 
@@ -375,8 +328,8 @@ async function createTables() {
         table.string("type", 50).notNullable();
         table.integer("monitor_id").unsigned().notNullable();
         table.integer("days").notNullable();
-        table.unique(["type", "monitor_id", "days"]);
+        table.unique([ "type", "monitor_id", "days" ]);
-        table.index(["type", "monitor_id", "days"], "good_index");
+        table.index([ "type", "monitor_id", "days" ], "good_index");
     });
 
     // setting
@@ -390,19 +343,16 @@ async function createTables() {
     // status_page_cname
     await knex.schema.createTable("status_page_cname", (table) => {
         table.increments("id");
-        table
+        table.integer("status_page_id").unsigned()
-            .integer("status_page_id")
+            .references("id").inTable("status_page")
-            .unsigned()
-            .references("id")
-            .inTable("status_page")
             .onDelete("CASCADE")
             .onUpdate("CASCADE");
         table.string("domain").notNullable().unique().collate("utf8_general_ci");
     });
 
     /*********************
-     * Converted Patch here
+    * Converted Patch here
-     *********************/
+    *********************/
 
     // 2023-06-30-1348-http-body-encoding.js
     // ALTER TABLE monitor ADD http_body_encoding VARCHAR(25);
@@ -443,12 +393,8 @@ async function createTables() {
         table.increments("id").primary();
         table.string("key", 255).notNullable();
         table.string("name", 255).notNullable();
-        table
+        table.integer("user_id").unsigned().notNullable()
-            .integer("user_id")
+            .references("id").inTable("user")
-            .unsigned()
-            .notNullable()
-            .references("id")
-            .inTable("user")
             .onDelete("CASCADE")
             .onUpdate("CASCADE");
         table.dateTime("created_date").defaultTo(knex.fn.now()).notNullable();
@@ -481,11 +427,13 @@ async function createTables() {
         ALTER TABLE maintenance ADD timezone VARCHAR(255);
         ALTER TABLE maintenance ADD duration INTEGER;
     */
-    await knex.schema.dropTableIfExists("maintenance_timeslot").table("maintenance", function (table) {
+    await knex.schema
-        table.text("cron");
+        .dropTableIfExists("maintenance_timeslot")
-        table.string("timezone", 255);
+        .table("maintenance", function (table) {
-        table.integer("duration");
+            table.text("cron");
-    });
+            table.string("timezone", 255);
+            table.integer("duration");
+        });
 
     // 2023-06-30-1413-add-parent-monitor.js.
     /*
@@ -493,7 +441,10 @@ async function createTables() {
         ADD parent INTEGER REFERENCES [monitor] ([id]) ON DELETE SET NULL ON UPDATE CASCADE;
     */
     await knex.schema.table("monitor", function (table) {
-        table.integer("parent").unsigned().references("id").inTable("monitor").onDelete("SET NULL").onUpdate("CASCADE");
+        table.integer("parent").unsigned()
+            .references("id").inTable("monitor")
+            .onDelete("SET NULL")
+            .onUpdate("CASCADE");
     });
 
     /*
@@ -542,11 +493,8 @@ ALTER TABLE monitor
     await knex.schema.table("monitor", function (table) {
         table.string("kafka_producer_topic", 255);
         table.text("kafka_producer_brokers");
-
+        table.integer("kafka_producer_ssl");
-        // patch-fix-kafka-producer-booleans.sql
+        table.string("kafka_producer_allow_auto_topic_creation", 255);
-        table.boolean("kafka_producer_ssl").defaultTo(0).notNullable();
-        table.boolean("kafka_producer_allow_auto_topic_creation").defaultTo(0).notNullable();
-
         table.text("kafka_producer_sasl_options");
         table.text("kafka_producer_message");
     });

db/knex_migrations/2023-08-16-0000-create-uptime.js

@@ -3,41 +3,39 @@ exports.up = function (knex) {
         .createTable("stat_minutely", function (table) {
             table.increments("id");
             table.comment("This table contains the minutely aggregate statistics for each monitor");
-            table
+            table.integer("monitor_id").unsigned().notNullable()
-                .integer("monitor_id")
+                .references("id").inTable("monitor")
-                .unsigned()
-                .notNullable()
-                .references("id")
-                .inTable("monitor")
                 .onDelete("CASCADE")
                 .onUpdate("CASCADE");
-            table.integer("timestamp").notNullable().comment("Unix timestamp rounded down to the nearest minute");
+            table.integer("timestamp")
+                .notNullable()
+                .comment("Unix timestamp rounded down to the nearest minute");
             table.float("ping").notNullable().comment("Average ping in milliseconds");
             table.smallint("up").notNullable();
             table.smallint("down").notNullable();
 
-            table.unique(["monitor_id", "timestamp"]);
+            table.unique([ "monitor_id", "timestamp" ]);
         })
         .createTable("stat_daily", function (table) {
             table.increments("id");
             table.comment("This table contains the daily aggregate statistics for each monitor");
-            table
+            table.integer("monitor_id").unsigned().notNullable()
-                .integer("monitor_id")
+                .references("id").inTable("monitor")
-                .unsigned()
-                .notNullable()
-                .references("id")
-                .inTable("monitor")
                 .onDelete("CASCADE")
                 .onUpdate("CASCADE");
-            table.integer("timestamp").notNullable().comment("Unix timestamp rounded down to the nearest day");
+            table.integer("timestamp")
+                .notNullable()
+                .comment("Unix timestamp rounded down to the nearest day");
             table.float("ping").notNullable().comment("Average ping in milliseconds");
             table.smallint("up").notNullable();
             table.smallint("down").notNullable();
 
-            table.unique(["monitor_id", "timestamp"]);
+            table.unique([ "monitor_id", "timestamp" ]);
         });
 };
 
 exports.down = function (knex) {
-    return knex.schema.dropTable("stat_minutely").dropTable("stat_daily");
+    return knex.schema
+        .dropTable("stat_minutely")
+        .dropTable("stat_daily");
 };

db/knex_migrations/2023-08-18-0301-heartbeat.js

@@ -1,13 +1,16 @@
 exports.up = function (knex) {
     // Add new column heartbeat.end_time
-    return knex.schema.alterTable("heartbeat", function (table) {
+    return knex.schema
-        table.datetime("end_time").nullable().defaultTo(null);
+        .alterTable("heartbeat", function (table) {
-    });
+            table.datetime("end_time").nullable().defaultTo(null);
+        });
+
 };
 
 exports.down = function (knex) {
     // Rename heartbeat.start_time to heartbeat.time
-    return knex.schema.alterTable("heartbeat", function (table) {
+    return knex.schema
-        table.dropColumn("end_time");
+        .alterTable("heartbeat", function (table) {
-    });
+            table.dropColumn("end_time");
+        });
 };

db/knex_migrations/2023-09-29-0000-heartbeat-retires.js

@@ -1,12 +0,0 @@
-exports.up = function (knex) {
-    // Add new column heartbeat.retries
-    return knex.schema.alterTable("heartbeat", function (table) {
-        table.integer("retries").notNullable().defaultTo(0);
-    });
-};
-
-exports.down = function (knex) {
-    return knex.schema.alterTable("heartbeat", function (table) {
-        table.dropColumn("retries");
-    });
-};

db/knex_migrations/2023-10-08-0000-mqtt-query.js

@@ -1,13 +0,0 @@
-exports.up = function (knex) {
-    // Add new column monitor.mqtt_check_type
-    return knex.schema.alterTable("monitor", function (table) {
-        table.string("mqtt_check_type", 255).notNullable().defaultTo("keyword");
-    });
-};
-
-exports.down = function (knex) {
-    // Drop column monitor.mqtt_check_type
-    return knex.schema.alterTable("monitor", function (table) {
-        table.dropColumn("mqtt_check_type");
-    });
-};

db/knex_migrations/2023-10-11-1915-push-token-to-32.js

@@ -1,12 +0,0 @@
-exports.up = function (knex) {
-    // update monitor.push_token to 32 length
-    return knex.schema.alterTable("monitor", function (table) {
-        table.string("push_token", 32).alter();
-    });
-};
-
-exports.down = function (knex) {
-    return knex.schema.alterTable("monitor", function (table) {
-        table.string("push_token", 20).alter();
-    });
-};

db/knex_migrations/2023-10-16-0000-create-remote-browsers.js

@@ -1,26 +0,0 @@
-exports.up = function (knex) {
-    return knex.schema
-        .createTable("remote_browser", function (table) {
-            table.increments("id");
-            table.string("name", 255).notNullable();
-            table.string("url", 255).notNullable();
-            table.integer("user_id").unsigned();
-        })
-        .alterTable("monitor", function (table) {
-            // Add new column monitor.remote_browser
-            table
-                .integer("remote_browser")
-                .nullable()
-                .defaultTo(null)
-                .unsigned()
-                .index()
-                .references("id")
-                .inTable("remote_browser");
-        });
-};
-
-exports.down = function (knex) {
-    return knex.schema.dropTable("remote_browser").alterTable("monitor", function (table) {
-        table.dropColumn("remote_browser");
-    });
-};

db/knex_migrations/2023-12-20-0000-alter-status-page.js

@@ -1,11 +0,0 @@
-exports.up = function (knex) {
-    return knex.schema.alterTable("status_page", function (table) {
-        table.integer("auto_refresh_interval").defaultTo(300).unsigned();
-    });
-};
-
-exports.down = function (knex) {
-    return knex.schema.alterTable("status_page", function (table) {
-        table.dropColumn("auto_refresh_interval");
-    });
-};

db/knex_migrations/2023-12-21-0000-stat-ping-min-max.js

@@ -1,39 +0,0 @@
-exports.up = function (knex) {
-    return knex.schema
-        .alterTable("stat_daily", function (table) {
-            table
-                .float("ping_min")
-                .notNullable()
-                .defaultTo(0)
-                .comment("Minimum ping during this period in milliseconds");
-            table
-                .float("ping_max")
-                .notNullable()
-                .defaultTo(0)
-                .comment("Maximum ping during this period in milliseconds");
-        })
-        .alterTable("stat_minutely", function (table) {
-            table
-                .float("ping_min")
-                .notNullable()
-                .defaultTo(0)
-                .comment("Minimum ping during this period in milliseconds");
-            table
-                .float("ping_max")
-                .notNullable()
-                .defaultTo(0)
-                .comment("Maximum ping during this period in milliseconds");
-        });
-};
-
-exports.down = function (knex) {
-    return knex.schema
-        .alterTable("stat_daily", function (table) {
-            table.dropColumn("ping_min");
-            table.dropColumn("ping_max");
-        })
-        .alterTable("stat_minutely", function (table) {
-            table.dropColumn("ping_min");
-            table.dropColumn("ping_max");
-        });
-};

db/knex_migrations/2023-12-22-0000-hourly-uptime.js

@@ -1,26 +0,0 @@
-exports.up = function (knex) {
-    return knex.schema.createTable("stat_hourly", function (table) {
-        table.increments("id");
-        table.comment("This table contains the hourly aggregate statistics for each monitor");
-        table
-            .integer("monitor_id")
-            .unsigned()
-            .notNullable()
-            .references("id")
-            .inTable("monitor")
-            .onDelete("CASCADE")
-            .onUpdate("CASCADE");
-        table.integer("timestamp").notNullable().comment("Unix timestamp rounded down to the nearest hour");
-        table.float("ping").notNullable().comment("Average ping in milliseconds");
-        table.float("ping_min").notNullable().defaultTo(0).comment("Minimum ping during this period in milliseconds");
-        table.float("ping_max").notNullable().defaultTo(0).comment("Maximum ping during this period in milliseconds");
-        table.smallint("up").notNullable();
-        table.smallint("down").notNullable();
-
-        table.unique(["monitor_id", "timestamp"]);
-    });
-};
-
-exports.down = function (knex) {
-    return knex.schema.dropTable("stat_hourly");
-};

db/knex_migrations/2024-01-22-0000-stats-extras.js

@@ -1,25 +0,0 @@
-exports.up = function (knex) {
-    return knex.schema
-        .alterTable("stat_daily", function (table) {
-            table.text("extras").defaultTo(null).comment("Extra statistics during this time period");
-        })
-        .alterTable("stat_minutely", function (table) {
-            table.text("extras").defaultTo(null).comment("Extra statistics during this time period");
-        })
-        .alterTable("stat_hourly", function (table) {
-            table.text("extras").defaultTo(null).comment("Extra statistics during this time period");
-        });
-};
-
-exports.down = function (knex) {
-    return knex.schema
-        .alterTable("stat_daily", function (table) {
-            table.dropColumn("extras");
-        })
-        .alterTable("stat_minutely", function (table) {
-            table.dropColumn("extras");
-        })
-        .alterTable("stat_hourly", function (table) {
-            table.dropColumn("extras");
-        });
-};

db/knex_migrations/2024-04-26-0000-snmp-monitor.js

@@ -1,15 +0,0 @@
-exports.up = function (knex) {
-    return knex.schema.alterTable("monitor", function (table) {
-        table.string("snmp_oid").defaultTo(null);
-        table.enum("snmp_version", ["1", "2c", "3"]).defaultTo("2c");
-        table.string("json_path_operator").defaultTo(null);
-    });
-};
-
-exports.down = function (knex) {
-    return knex.schema.alterTable("monitor", function (table) {
-        table.dropColumn("snmp_oid");
-        table.dropColumn("snmp_version");
-        table.dropColumn("json_path_operator");
-    });
-};

db/knex_migrations/2024-08-24-000-add-cache-bust.js

@@ -1,11 +0,0 @@
-exports.up = function (knex) {
-    return knex.schema.alterTable("monitor", function (table) {
-        table.boolean("cache_bust").notNullable().defaultTo(false);
-    });
-};
-
-exports.down = function (knex) {
-    return knex.schema.alterTable("monitor", function (table) {
-        table.dropColumn("cache_bust");
-    });
-};

db/knex_migrations/2024-08-24-0000-conditions.js

@@ -1,11 +0,0 @@
-exports.up = function (knex) {
-    return knex.schema.alterTable("monitor", function (table) {
-        table.text("conditions").notNullable().defaultTo("[]");
-    });
-};
-
-exports.down = function (knex) {
-    return knex.schema.alterTable("monitor", function (table) {
-        table.dropColumn("conditions");
-    });
-};

db/knex_migrations/2024-10-1315-rabbitmq-monitor.js

@@ -1,15 +0,0 @@
-exports.up = function (knex) {
-    return knex.schema.alterTable("monitor", function (table) {
-        table.text("rabbitmq_nodes");
-        table.string("rabbitmq_username");
-        table.string("rabbitmq_password");
-    });
-};
-
-exports.down = function (knex) {
-    return knex.schema.alterTable("monitor", function (table) {
-        table.dropColumn("rabbitmq_nodes");
-        table.dropColumn("rabbitmq_username");
-        table.dropColumn("rabbitmq_password");
-    });
-};

db/knex_migrations/2024-10-31-0000-fix-snmp-monitor.js

@@ -1,7 +0,0 @@
-exports.up = function (knex) {
-    return knex("monitor").whereNull("json_path_operator").update("json_path_operator", "==");
-};
-exports.down = function (knex) {
-    // changing the json_path_operator back to null for all "==" is not possible anymore
-    // we have lost the context which fields have been set explicitely in >= v2.0 and which would need to be reverted
-};

db/knex_migrations/2024-11-27-1927-fix-info-json-data-type.js

@@ -1,12 +0,0 @@
-// Update info_json column to LONGTEXT mainly for MariaDB
-exports.up = function (knex) {
-    return knex.schema.alterTable("monitor_tls_info", function (table) {
-        table.text("info_json", "longtext").alter();
-    });
-};
-
-exports.down = function (knex) {
-    return knex.schema.alterTable("monitor_tls_info", function (table) {
-        table.text("info_json", "text").alter();
-    });
-};

db/knex_migrations/2025-01-01-0000-add-smtp.js

@@ -1,11 +0,0 @@
-exports.up = function (knex) {
-    return knex.schema.alterTable("monitor", function (table) {
-        table.string("smtp_security").defaultTo(null);
-    });
-};
-
-exports.down = function (knex) {
-    return knex.schema.alterTable("monitor", function (table) {
-        table.dropColumn("smtp_security");
-    });
-};

db/knex_migrations/2025-02-15-2312-add-wstest.js

@@ -1,14 +0,0 @@
-// Add websocket ignore headers and websocket subprotocol
-exports.up = function (knex) {
-    return knex.schema.alterTable("monitor", function (table) {
-        table.boolean("ws_ignore_sec_websocket_accept_header").notNullable().defaultTo(false);
-        table.string("ws_subprotocol", 255).notNullable().defaultTo("");
-    });
-};
-
-exports.down = function (knex) {
-    return knex.schema.alterTable("monitor", function (table) {
-        table.dropColumn("ws_ignore_sec_websocket_accept_header");
-        table.dropColumn("ws_subprotocol");
-    });
-};

db/knex_migrations/2025-02-17-2142-generalize-analytics.js

@@ -1,23 +0,0 @@
-// Udpate status_page table to generalize analytics fields
-exports.up = function (knex) {
-    return knex.schema
-        .alterTable("status_page", function (table) {
-            table.renameColumn("google_analytics_tag_id", "analytics_id");
-            table.string("analytics_script_url");
-            table.enu("analytics_type", ["google", "umami", "plausible", "matomo"]).defaultTo(null);
-        })
-        .then(() => {
-            // After a succesful migration, add google as default for previous pages
-            knex("status_page").whereNotNull("analytics_id").update({
-                analytics_type: "google",
-            });
-        });
-};
-
-exports.down = function (knex) {
-    return knex.schema.alterTable("status_page", function (table) {
-        table.renameColumn("analytics_id", "google_analytics_tag_id");
-        table.dropColumn("analytics_script_url");
-        table.dropColumn("analytics_type");
-    });
-};

db/knex_migrations/2025-03-04-0000-ping-advanced-options.js

@@ -1,21 +0,0 @@
-/* SQL:
-ALTER TABLE monitor ADD ping_count INTEGER default 1 not null;
-ALTER TABLE monitor ADD ping_numeric BOOLEAN default true not null;
-ALTER TABLE monitor ADD ping_per_request_timeout INTEGER default 2 not null;
-*/
-exports.up = function (knex) {
-    // Add new columns to table monitor
-    return knex.schema.alterTable("monitor", function (table) {
-        table.integer("ping_count").defaultTo(1).notNullable();
-        table.boolean("ping_numeric").defaultTo(true).notNullable();
-        table.integer("ping_per_request_timeout").defaultTo(2).notNullable();
-    });
-};
-
-exports.down = function (knex) {
-    return knex.schema.alterTable("monitor", function (table) {
-        table.dropColumn("ping_count");
-        table.dropColumn("ping_numeric");
-        table.dropColumn("ping_per_request_timeout");
-    });
-};

db/knex_migrations/2025-03-25-0127-fix-5721.js

@@ -1,12 +0,0 @@
-// Fix #5721: Change proxy port column type to integer to support larger port numbers
-exports.up = function (knex) {
-    return knex.schema.alterTable("proxy", function (table) {
-        table.integer("port").alter();
-    });
-};
-
-exports.down = function (knex) {
-    return knex.schema.alterTable("proxy", function (table) {
-        table.smallint("port").alter();
-    });
-};

db/knex_migrations/2025-05-09-0000-add-custom-url.js

@@ -1,12 +0,0 @@
-// Add column custom_url to monitor_group table
-exports.up = function (knex) {
-    return knex.schema.alterTable("monitor_group", function (table) {
-        table.text("custom_url", "text");
-    });
-};
-
-exports.down = function (knex) {
-    return knex.schema.alterTable("monitor_group", function (table) {
-        table.dropColumn("custom_url");
-    });
-};

db/knex_migrations/2025-06-03-0000-add-ip-family.js

@@ -1,11 +0,0 @@
-exports.up = function (knex) {
-    return knex.schema.alterTable("monitor", function (table) {
-        table.boolean("ip_family").defaultTo(null);
-    });
-};
-
-exports.down = function (knex) {
-    return knex.schema.alterTable("monitor", function (table) {
-        table.dropColumn("ip_family");
-    });
-};

db/knex_migrations/2025-06-11-0000-add-manual-monitor.js

@@ -1,11 +0,0 @@
-exports.up = function (knex) {
-    return knex.schema.alterTable("monitor", function (table) {
-        table.string("manual_status").defaultTo(null);
-    });
-};
-
-exports.down = function (knex) {
-    return knex.schema.alterTable("monitor", function (table) {
-        table.dropColumn("manual_status");
-    });
-};

db/knex_migrations/2025-06-13-0000-maintenance-add-last-start.js

@@ -1,33 +0,0 @@
-// Add column last_start_date to maintenance table
-exports.up = async function (knex) {
-    await knex.schema.alterTable("maintenance", function (table) {
-        table.datetime("last_start_date");
-    });
-
-    // Perform migration for recurring-interval strategy
-    const recurringMaintenances = await knex("maintenance")
-        .where({
-            strategy: "recurring-interval",
-            cron: "* * * * *",
-        })
-        .select("id", "start_time");
-
-    // eslint-disable-next-line camelcase
-    const maintenanceUpdates = recurringMaintenances.map(async ({ start_time, id }) => {
-        // eslint-disable-next-line camelcase
-        const [hourStr, minuteStr] = start_time.split(":");
-        const hour = parseInt(hourStr, 10);
-        const minute = parseInt(minuteStr, 10);
-
-        const cron = `${minute} ${hour} * * *`;
-
-        await knex("maintenance").where({ id }).update({ cron });
-    });
-    await Promise.all(maintenanceUpdates);
-};
-
-exports.down = function (knex) {
-    return knex.schema.alterTable("maintenance", function (table) {
-        table.dropColumn("last_start_date");
-    });
-};

db/knex_migrations/2025-06-15-0001-manual-monitor-fix.js

@@ -1,12 +0,0 @@
-// Fix: Change manual_status column type to smallint
-exports.up = function (knex) {
-    return knex.schema.alterTable("monitor", function (table) {
-        table.smallint("manual_status").alter();
-    });
-};
-
-exports.down = function (knex) {
-    return knex.schema.alterTable("monitor", function (table) {
-        table.string("manual_status").alter();
-    });
-};

db/knex_migrations/2025-06-24-0000-add-audience-to-oauth.js

@@ -1,11 +0,0 @@
-exports.up = function (knex) {
-    return knex.schema.alterTable("monitor", function (table) {
-        table.string("oauth_audience").nullable().defaultTo(null);
-    });
-};
-
-exports.down = function (knex) {
-    return knex.schema.alterTable("monitor", function (table) {
-        table.string("oauth_audience").alter();
-    });
-};

db/knex_migrations/2025-07-17-0000-mqtt-websocket-path.js

@@ -1,13 +0,0 @@
-exports.up = function (knex) {
-    // Add new column monitor.mqtt_websocket_path
-    return knex.schema.alterTable("monitor", function (table) {
-        table.string("mqtt_websocket_path", 255).nullable();
-    });
-};
-
-exports.down = function (knex) {
-    // Drop column monitor.mqtt_websocket_path
-    return knex.schema.alterTable("monitor", function (table) {
-        table.dropColumn("mqtt_websocket_path");
-    });
-};

db/knex_migrations/2025-09-02-0000-add-domain-expiry.js

@@ -1,23 +0,0 @@
-exports.up = function (knex) {
-    return knex.schema
-        .alterTable("monitor", function (table) {
-            table.boolean("domain_expiry_notification").defaultTo(1);
-        })
-        .createTable("domain_expiry", (table) => {
-            table.increments("id");
-            table.datetime("last_check");
-            // Use VARCHAR(255) for MySQL/MariaDB compatibility with unique constraint
-            // Maximum domain name length is 253 characters (255 octets on the wire)
-            table.string("domain", 255).unique().notNullable();
-            table.datetime("expiry");
-            table.integer("last_expiry_notification_sent").defaultTo(null);
-        });
-};
-
-exports.down = function (knex) {
-    return knex.schema
-        .alterTable("monitor", function (table) {
-            table.boolean("domain_expiry_notification").alter();
-        })
-        .dropTable("domain_expiry");
-};

db/knex_migrations/2025-10-14-0000-add-ip-family-fix.js

@@ -1,14 +0,0 @@
-exports.up = function (knex) {
-    return knex.schema.alterTable("monitor", function (table) {
-        // Fix ip_family, change to varchar instead of boolean
-        // possible values are "ipv4" and "ipv6"
-        table.string("ip_family", 4).defaultTo(null).alter();
-    });
-};
-
-exports.down = function (knex) {
-    return knex.schema.alterTable("monitor", function (table) {
-        // Rollback to boolean
-        table.boolean("ip_family").defaultTo(null).alter();
-    });
-};

db/knex_migrations/2025-10-15-0000-stat-table-fix.js

@@ -1,27 +0,0 @@
-// Fix for #4315. Logically, setting it to 0 ping may not be correct, but it is better than throwing errors
-
-exports.up = function (knex) {
-    return knex.schema
-        .alterTable("stat_daily", function (table) {
-            table.integer("ping").defaultTo(0).alter();
-        })
-        .alterTable("stat_hourly", function (table) {
-            table.integer("ping").defaultTo(0).alter();
-        })
-        .alterTable("stat_minutely", function (table) {
-            table.integer("ping").defaultTo(0).alter();
-        });
-};
-
-exports.down = function (knex) {
-    return knex.schema
-        .alterTable("stat_daily", function (table) {
-            table.integer("ping").alter();
-        })
-        .alterTable("stat_hourly", function (table) {
-            table.integer("ping").alter();
-        })
-        .alterTable("stat_minutely", function (table) {
-            table.integer("ping").alter();
-        });
-};

db/knex_migrations/2025-10-15-0001-add-monitor-response-config.js

@@ -1,15 +0,0 @@
-exports.up = function (knex) {
-    return knex.schema.alterTable("monitor", function (table) {
-        table.boolean("save_response").notNullable().defaultTo(false);
-        table.boolean("save_error_response").notNullable().defaultTo(true);
-        table.integer("response_max_length").notNullable().defaultTo(1024); // Default 1KB
-    });
-};
-
-exports.down = function (knex) {
-    return knex.schema.alterTable("monitor", function (table) {
-        table.dropColumn("save_response");
-        table.dropColumn("save_error_response");
-        table.dropColumn("response_max_length");
-    });
-};

db/knex_migrations/2025-10-15-0002-add-response-to-heartbeat.js

@@ -1,11 +0,0 @@
-exports.up = function (knex) {
-    return knex.schema.alterTable("heartbeat", function (table) {
-        table.text("response").nullable().defaultTo(null);
-    });
-};
-
-exports.down = function (knex) {
-    return knex.schema.alterTable("heartbeat", function (table) {
-        table.dropColumn("response");
-    });
-};

db/knex_migrations/2025-10-24-0000-show-only-last-heartbeat.js

@@ -1,13 +0,0 @@
-exports.up = function (knex) {
-    // Add new column status_page.show_only_last_heartbeat
-    return knex.schema.alterTable("status_page", function (table) {
-        table.boolean("show_only_last_heartbeat").notNullable().defaultTo(false);
-    });
-};
-
-exports.down = function (knex) {
-    // Drop column status_page.show_only_last_heartbeat
-    return knex.schema.alterTable("status_page", function (table) {
-        table.dropColumn("show_only_last_heartbeat");
-    });
-};

db/knex_migrations/2025-12-09-0000-add-system-service-monitor.js

@@ -1,19 +0,0 @@
-/**
- * @param {import("knex").Knex} knex The Knex.js instance for database interaction.
- * @returns {Promise<void>}
- */
-exports.up = async (knex) => {
-    await knex.schema.alterTable("monitor", (table) => {
-        table.string("system_service_name");
-    });
-};
-
-/**
- * @param {import("knex").Knex} knex The Knex.js instance for database interaction.
- * @returns {Promise<void>}
- */
-exports.down = async (knex) => {
-    await knex.schema.alterTable("monitor", (table) => {
-        table.dropColumn("system_service_name");
-    });
-};

db/knex_migrations/2025-12-22-0121-optimize-important-indexes.js

@@ -1,37 +0,0 @@
-exports.up = async function (knex) {
-    const isSQLite = knex.client.dialect === "sqlite3";
-
-    if (isSQLite) {
-        // For SQLite: Use partial indexes with WHERE important = 1
-        // Drop existing indexes using IF EXISTS
-        await knex.raw("DROP INDEX IF EXISTS monitor_important_time_index");
-        await knex.raw("DROP INDEX IF EXISTS heartbeat_important_index");
-
-        // Create partial indexes with predicate
-        await knex.schema.alterTable("heartbeat", function (table) {
-            table.index(["monitor_id", "time"], "monitor_important_time_index", {
-                predicate: knex.whereRaw("important = 1"),
-            });
-            table.index(["important"], "heartbeat_important_index", {
-                predicate: knex.whereRaw("important = 1"),
-            });
-        });
-    }
-    // For MariaDB/MySQL: No changes (partial indexes not supported)
-};
-
-exports.down = async function (knex) {
-    const isSQLite = knex.client.dialect === "sqlite3";
-
-    if (isSQLite) {
-        // Restore original indexes
-        await knex.raw("DROP INDEX IF EXISTS monitor_important_time_index");
-        await knex.raw("DROP INDEX IF EXISTS heartbeat_important_index");
-
-        await knex.schema.alterTable("heartbeat", function (table) {
-            table.index(["monitor_id", "important", "time"], "monitor_important_time_index");
-            table.index(["important"]);
-        });
-    }
-    // For MariaDB/MySQL: No changes
-};

db/knex_migrations/2025-12-29-0000-remove-line-notify.js

@@ -1,30 +0,0 @@
-exports.up = async function (knex) {
-    const notifications = await knex("notification").select("id", "config");
-    const lineNotifyIDs = [];
-
-    for (const { id, config } of notifications) {
-        try {
-            const parsedConfig = JSON.parse(config || "{}");
-            const type = typeof parsedConfig.type === "string" ? parsedConfig.type.toLowerCase() : "";
-
-            if (type === "linenotify" || type === "line-notify") {
-                lineNotifyIDs.push(id);
-            }
-        } catch (error) {
-            // Ignore invalid JSON blobs here; they are handled elsewhere in the app.
-        }
-    }
-
-    if (lineNotifyIDs.length === 0) {
-        return;
-    }
-
-    await knex.transaction(async (trx) => {
-        await trx("monitor_notification").whereIn("notification_id", lineNotifyIDs).del();
-        await trx("notification").whereIn("id", lineNotifyIDs).del();
-    });
-};
-
-exports.down = async function () {
-    // Removal of LINE Notify configs is not reversible.
-};

db/knex_migrations/2025-12-31-2143-add-snmp-v3-username.js

@@ -1,11 +0,0 @@
-exports.up = async function (knex) {
-    await knex.schema.alterTable("monitor", (table) => {
-        table.string("snmp_v3_username", 255);
-    });
-};
-
-exports.down = async function (knex) {
-    await knex.schema.alterTable("monitor", (table) => {
-        table.dropColumn("snmp_v3_username");
-    });
-};

db/knex_migrations/2026-01-02-0551-dns-last-result-to-text.js

@@ -1,12 +0,0 @@
-// Change dns_last_result column from VARCHAR(255) to TEXT to handle longer DNS TXT records
-exports.up = function (knex) {
-    return knex.schema.alterTable("monitor", function (table) {
-        table.text("dns_last_result").alter();
-    });
-};
-
-exports.down = function (knex) {
-    return knex.schema.alterTable("monitor", function (table) {
-        table.string("dns_last_result", 255).alter();
-    });
-};

db/knex_migrations/2026-01-02-0713-gamedig-v4-to-v5.js

@@ -1,186 +0,0 @@
-// Migration to update monitor.game from GameDig v4 to v5 game IDs
-// Reference: https://github.com/gamedig/node-gamedig/blob/master/MIGRATE_IDS.md
-
-// Lookup table mapping v4 game IDs to v5 game IDs
-const gameDig4to5IdMap = {
-    americasarmypg: "aapg",
-    "7d2d": "sdtd",
-    as: "actionsource",
-    ageofchivalry: "aoc",
-    arkse: "ase",
-    arcasimracing: "asr08",
-    arma: "aaa",
-    arma2oa: "a2oa",
-    armacwa: "acwa",
-    armar: "armaresistance",
-    armare: "armareforger",
-    armagetron: "armagetronadvanced",
-    bat1944: "battalion1944",
-    bf1942: "battlefield1942",
-    bfv: "battlefieldvietnam",
-    bf2: "battlefield2",
-    bf2142: "battlefield2142",
-    bfbc2: "bbc2",
-    bf3: "battlefield3",
-    bf4: "battlefield4",
-    bfh: "battlefieldhardline",
-    bd: "basedefense",
-    bs: "bladesymphony",
-    buildandshoot: "bas",
-    cod4: "cod4mw",
-    callofjuarez: "coj",
-    chivalry: "cmw",
-    commandos3: "c3db",
-    cacrenegade: "cacr",
-    contactjack: "contractjack",
-    cs15: "counterstrike15",
-    cs16: "counterstrike16",
-    cs2: "counterstrike2",
-    crossracing: "crce",
-    darkesthour: "dhe4445",
-    daysofwar: "dow",
-    deadlydozenpt: "ddpt",
-    dh2005: "deerhunter2005",
-    dinodday: "ddd",
-    dirttrackracing2: "dtr2",
-    dmc: "deathmatchclassic",
-    dnl: "dal",
-    drakan: "dootf",
-    dys: "dystopia",
-    em: "empiresmod",
-    empyrion: "egs",
-    f12002: "formulaone2002",
-    flashpointresistance: "ofr",
-    fivem: "gta5f",
-    forrest: "theforrest",
-    graw: "tcgraw",
-    graw2: "tcgraw2",
-    giantscitizenkabuto: "gck",
-    ges: "goldeneyesource",
-    gore: "gus",
-    hldm: "hld",
-    hldms: "hlds",
-    hlopfor: "hlof",
-    hl2dm: "hl2d",
-    hidden: "thehidden",
-    had2: "hiddendangerous2",
-    igi2: "i2cs",
-    il2: "il2sturmovik",
-    insurgencymic: "imic",
-    isle: "theisle",
-    jamesbondnightfire: "jb007n",
-    jc2mp: "jc2m",
-    jc3mp: "jc3m",
-    kingpin: "kloc",
-    kisspc: "kpctnc",
-    kspdmp: "kspd",
-    kzmod: "kreedzclimbing",
-    left4dead: "l4d",
-    left4dead2: "l4d2",
-    m2mp: "m2m",
-    mohsh: "mohaas",
-    mohbt: "mohaab",
-    mohab: "moha",
-    moh2010: "moh",
-    mohwf: "mohw",
-    minecraftbe: "mbe",
-    mtavc: "gtavcmta",
-    mtasa: "gtasamta",
-    ns: "naturalselection",
-    ns2: "naturalselection2",
-    nwn: "neverwinternights",
-    nwn2: "neverwinternights2",
-    nolf: "tonolf",
-    nolf2: "nolf2asihw",
-    pvkii: "pvak2",
-    ps: "postscriptum",
-    primalcarnage: "pce",
-    pc: "projectcars",
-    pc2: "projectcars2",
-    prbf2: "prb2",
-    przomboid: "projectzomboid",
-    quake1: "quake",
-    quake3: "q3a",
-    ragdollkungfu: "rdkf",
-    r6: "rainbowsix",
-    r6roguespear: "rs2rs",
-    r6ravenshield: "rs3rs",
-    redorchestraost: "roo4145",
-    redm: "rdr2r",
-    riseofnations: "ron",
-    rs2: "rs2v",
-    samp: "gtasam",
-    saomp: "gtasao",
-    savage2: "s2ats",
-    ss: "serioussam",
-    ss2: "serioussam2",
-    ship: "theship",
-    sinep: "sinepisodes",
-    sonsoftheforest: "sotf",
-    swbf: "swb",
-    swbf2: "swb2",
-    swjk: "swjkja",
-    swjk2: "swjk2jo",
-    takeonhelicopters: "toh",
-    tf2: "teamfortress2",
-    terraria: "terrariatshock",
-    tribes1: "t1s",
-    ut: "unrealtournament",
-    ut2003: "unrealtournament2003",
-    ut2004: "unrealtournament2004",
-    ut3: "unrealtournament3",
-    v8supercar: "v8sc",
-    vcmp: "vcm",
-    vs: "vampireslayer",
-    wheeloftime: "wot",
-    wolfenstein2009: "wolfenstein",
-    wolfensteinet: "wet",
-    wurm: "wurmunlimited",
-};
-
-/**
- * Migrate game IDs from v4 to v5
- * @param {import("knex").Knex} knex - Knex instance
- * @returns {Promise<void>}
- */
-exports.up = async function (knex) {
-    await knex.transaction(async (trx) => {
-        // Get all monitors that use the gamedig type
-        const monitors = await trx("monitor").select("id", "game").where("type", "gamedig").whereNotNull("game");
-
-        // Update each monitor with the new game ID if it needs migration
-        for (const monitor of monitors) {
-            const oldGameId = monitor.game;
-            const newGameId = gameDig4to5IdMap[oldGameId];
-
-            if (newGameId) {
-                await trx("monitor").where("id", monitor.id).update({ game: newGameId });
-            }
-        }
-    });
-};
-
-/**
- * Revert game IDs from v5 back to v4
- * @param {import("knex").Knex} knex - Knex instance
- * @returns {Promise<void>}
- */
-exports.down = async function (knex) {
-    // Create reverse mapping from the same LUT
-    const gameDig5to4IdMap = Object.fromEntries(Object.entries(gameDig4to5IdMap).map(([v4, v5]) => [v5, v4]));
-
-    await knex.transaction(async (trx) => {
-        // Get all monitors that use the gamedig type
-        const monitors = await trx("monitor").select("id", "game").where("type", "gamedig").whereNotNull("game");
-
-        // Revert each monitor back to the old game ID if it was migrated
-        for (const monitor of monitors) {
-            const newGameId = monitor.game;
-            const oldGameId = gameDig5to4IdMap[newGameId];
-
-            if (oldGameId) {
-                await trx("monitor").where("id", monitor.id).update({ game: oldGameId });
-            }
-        }
-    });
-};

db/knex_migrations/2026-01-05-0000-add-rss-title.js

@@ -1,11 +0,0 @@
-exports.up = async function (knex) {
-    await knex.schema.alterTable("status_page", function (table) {
-        table.string("rss_title", 255);
-    });
-};
-
-exports.down = function (knex) {
-    return knex.schema.alterTable("status_page", function (table) {
-        table.dropColumn("rss_title");
-    });
-};

db/knex_migrations/2026-01-05-0000-add-tls-monitor.js

@@ -1,11 +0,0 @@
-exports.up = function (knex) {
-    return knex.schema.alterTable("monitor", function (table) {
-        table.string("expected_tls_alert", 50).defaultTo(null);
-    });
-};
-
-exports.down = function (knex) {
-    return knex.schema.alterTable("monitor", function (table) {
-        table.dropColumn("expected_tls_alert");
-    });
-};

db/knex_migrations/2026-01-06-0000-fix-domain-expiry-column-type.js

@@ -1,14 +0,0 @@
-// Ensure domain column is VARCHAR(255) across all database types.
-// This migration ensures MySQL, SQLite, and MariaDB have consistent column type,
-// even if a user installed 2.1.0-beta.0 or 2.1.0-beta.1 which had TEXT type for this column.
-// Maximum domain name length is 253 characters (255 octets on the wire).
-// Note: The unique constraint is already present from the original migration.
-exports.up = function (knex) {
-    return knex.schema.alterTable("domain_expiry", function (table) {
-        table.string("domain", 255).notNullable().alter();
-    });
-};
-
-exports.down = function (knex) {
-    // No rollback needed - keeping VARCHAR(255) is the correct state
-};

db/knex_migrations/2026-01-10-0000-convert-float-precision.js

@@ -1,43 +0,0 @@
-exports.up = function (knex) {
-    return knex.schema
-        .alterTable("heartbeat", function (table) {
-            table.bigInteger("ping").alter();
-        })
-        .alterTable("stat_minutely", function (table) {
-            table.float("ping", 20, 2).notNullable().alter();
-            table.float("ping_min", 20, 2).notNullable().defaultTo(0).alter();
-            table.float("ping_max", 20, 2).notNullable().defaultTo(0).alter();
-        })
-        .alterTable("stat_daily", function (table) {
-            table.float("ping", 20, 2).notNullable().alter();
-            table.float("ping_min", 20, 2).notNullable().defaultTo(0).alter();
-            table.float("ping_max", 20, 2).notNullable().defaultTo(0).alter();
-        })
-        .alterTable("stat_hourly", function (table) {
-            table.float("ping", 20, 2).notNullable().alter();
-            table.float("ping_min", 20, 2).notNullable().defaultTo(0).alter();
-            table.float("ping_max", 20, 2).notNullable().defaultTo(0).alter();
-        });
-};
-
-exports.down = function (knex) {
-    return knex.schema
-        .alterTable("heartbeat", function (table) {
-            table.integer("ping").alter();
-        })
-        .alterTable("stat_minutely", function (table) {
-            table.float("ping").notNullable().alter();
-            table.float("ping_min").notNullable().defaultTo(0).alter();
-            table.float("ping_max").notNullable().defaultTo(0).alter();
-        })
-        .alterTable("stat_daily", function (table) {
-            table.float("ping").notNullable().alter();
-            table.float("ping_min").notNullable().defaultTo(0).alter();
-            table.float("ping_max").notNullable().defaultTo(0).alter();
-        })
-        .alterTable("stat_hourly", function (table) {
-            table.float("ping").notNullable().alter();
-            table.float("ping_min").notNullable().defaultTo(0).alter();
-            table.float("ping_max").notNullable().defaultTo(0).alter();
-        });
-};

db/knex_migrations/2026-01-15-0000-add-json-query-retry-only-status-code.js

@@ -1,12 +0,0 @@
-exports.up = function (knex) {
-    // Add new column to table monitor for json-query retry behavior
-    return knex.schema.alterTable("monitor", function (table) {
-        table.boolean("retry_only_on_status_code_failure").defaultTo(false).notNullable();
-    });
-};
-
-exports.down = function (knex) {
-    return knex.schema.alterTable("monitor", function (table) {
-        table.dropColumn("retry_only_on_status_code_failure");
-    });
-};

db/knex_migrations/2026-01-16-0000-add-screenshot-delay.js

@@ -1,11 +0,0 @@
-exports.up = function (knex) {
-    return knex.schema.alterTable("monitor", function (table) {
-        table.integer("screenshot_delay").notNullable().unsigned().defaultTo(0);
-    });
-};
-
-exports.down = function (knex) {
-    return knex.schema.alterTable("monitor", function (table) {
-        table.dropColumn("screenshot_delay");
-    });
-};

db/knex_migrations/README.md

@@ -11,9 +11,13 @@ https://knexjs.org/guide/migrations.html#knexfile-in-other-languages
 ## Template
 
 ```js
-exports.up = function (knex) {};
+exports.up = function(knex) {
 
-exports.down = function (knex) {};
+};
+
+exports.down = function(knex) {
+
+};
 
 // exports.config = { transaction: false };
 ```
@@ -23,28 +27,29 @@ exports.down = function (knex) {};
 Filename: 2023-06-30-1348-create-user-and-product.js
 
 ```js
-exports.up = function (knex) {
+exports.up = function(knex) {
   return knex.schema
-    .createTable("user", function (table) {
+    .createTable('user', function (table) {
-      table.increments("id");
+        table.increments('id');
-      table.string("first_name", 255).notNullable();
+        table.string('first_name', 255).notNullable();
-      table.string("last_name", 255).notNullable();
+        table.string('last_name', 255).notNullable();
     })
-    .createTable("product", function (table) {
+    .createTable('product', function (table) {
-      table.increments("id");
+        table.increments('id');
-      table.decimal("price").notNullable();
+        table.decimal('price').notNullable();
-      table.string("name", 1000).notNullable();
+        table.string('name', 1000).notNullable();
-    })
+    }).then(() => {
-    .then(() => {
+        knex("products").insert([
-      knex("products").insert([
+            { price: 10, name: "Apple" },
-        { price: 10, name: "Apple" },
+            { price: 20, name: "Orange" },
-        { price: 20, name: "Orange" },
+        ]);
-      ]);
     });
 };
 
-exports.down = function (knex) {
+exports.down = function(knex) {
-  return knex.schema.dropTable("product").dropTable("user");
+  return knex.schema
+      .dropTable("product")
+      .dropTable("user");
 };
 ```
 

db/old_migrations/patch-fix-kafka-producer-booleans.sql

@@ -1,34 +0,0 @@
--- You should not modify if this have pushed to Github, unless it does serious wrong with the db.
-BEGIN TRANSACTION;
-
--- Rename COLUMNs to another one (suffixed by `_old`)
-ALTER TABLE monitor
-    RENAME COLUMN kafka_producer_ssl TO kafka_producer_ssl_old;
-
-ALTER TABLE monitor
-    RENAME COLUMN kafka_producer_allow_auto_topic_creation TO kafka_producer_allow_auto_topic_creation_old;
-
--- Add correct COLUMNs
-ALTER TABLE monitor
-    ADD COLUMN kafka_producer_ssl BOOLEAN default 0 NOT NULL;
-
-ALTER TABLE monitor
-    ADD COLUMN kafka_producer_allow_auto_topic_creation BOOLEAN default 0 NOT NULL;
-
--- These SQL is still not fully safe. See https://github.com/louislam/uptime-kuma/issues/4039.
-
--- Set bring old values from `_old` COLUMNs to correct ones
--- UPDATE monitor SET kafka_producer_allow_auto_topic_creation = monitor.kafka_producer_allow_auto_topic_creation_old
--- WHERE monitor.kafka_producer_allow_auto_topic_creation_old IS NOT NULL;
-
--- UPDATE monitor SET kafka_producer_ssl = monitor.kafka_producer_ssl_old
--- WHERE monitor.kafka_producer_ssl_old IS NOT NULL;
-
--- Remove old COLUMNs
-ALTER TABLE monitor
-    DROP COLUMN kafka_producer_allow_auto_topic_creation_old;
-
-ALTER TABLE monitor
-    DROP COLUMN kafka_producer_ssl_old;
-
-COMMIT;

db/old_migrations/patch-monitor-tls-info-add-fk.sql

@@ -1,18 +0,0 @@
-BEGIN TRANSACTION;
-
-PRAGMA writable_schema = TRUE;
-
-UPDATE
-	SQLITE_MASTER
-SET
-	sql = replace(sql,
-	'monitor_id INTEGER NOT NULL',
-	'monitor_id INTEGER NOT NULL REFERENCES [monitor] ([id]) ON DELETE CASCADE ON UPDATE CASCADE'
-)
-WHERE
-	name = 'monitor_tls_info'
-	AND type = 'table';
-
-PRAGMA writable_schema = RESET;
-
-COMMIT;

db/old_migrations/patch-notification-config.sql

@@ -1,10 +0,0 @@
--- You should not modify if this have pushed to Github, unless it does serious wrong with the db.
-BEGIN TRANSACTION;
-
--- SQLite: Change the data type of the column "config" from VARCHAR to TEXT
-ALTER TABLE notification RENAME COLUMN config TO config_old;
-ALTER TABLE notification ADD COLUMN config TEXT;
-UPDATE notification SET config = config_old;
-ALTER TABLE notification DROP COLUMN config_old;
-
-COMMIT;

db/old_migrations/patch-timeout.sql

@@ -1,7 +0,0 @@
--- You should not modify if this have pushed to Github, unless it does serious wrong with the db.
-BEGIN TRANSACTION;
-
-UPDATE monitor SET timeout = (interval * 0.8)
-WHERE timeout IS NULL OR timeout <= 0;
-
-COMMIT;

db/patch-monitor-tls-info-add-fk.sql

@@ -1,18 +0,0 @@
-BEGIN TRANSACTION;
-
-PRAGMA writable_schema = TRUE;
-
-UPDATE
-	SQLITE_MASTER
-SET
-	sql = replace(sql,
-	'monitor_id INTEGER NOT NULL',
-	'monitor_id INTEGER NOT NULL REFERENCES [monitor] ([id]) ON DELETE CASCADE ON UPDATE CASCADE'
-)
-WHERE
-	name = 'monitor_tls_info'
-	AND type = 'table';
-
-PRAGMA writable_schema = RESET;
-
-COMMIT;