Merge pull request #1449 from mhkarimi1383/ansible-unofficial

making it functional when you have a minimal host

.devcontainer/README.md

@@ -1,28 +0,0 @@
-# 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

@@ -1,22 +0,0 @@
-{
-    "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"
-            ]
-        }
-    },
-    "forwardPorts": [3000, 3001]
-}

.dockerignore

@@ -1,58 +0,0 @@
-/.idea
-/node_modules
-/data
-/cypress
-/out
-/test
-/kubernetes
-/.do
-**/.dockerignore
-/private
-**/.git
-**/.gitignore
-**/docker-compose*
-**/[Dd]ockerfile*
-LICENSE
-README.md
-.editorconfig
-.vscode
-.eslint*
-.stylelint*
-/.devcontainer
-/.github
-yarn.lock
-app.json
-CODE_OF_CONDUCT.md
-CONTRIBUTING.md
-CNAME
-install.sh
-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
-.DS_Store
-#dist
-dist-ssr
-*.local
-#.idea
-
-#/data
-#!/data/.gitkeep
-#.vscode
-
-### End of .gitignore content

.editorconfig

@@ -1,24 +0,0 @@
-root = true
-
-[*]
-indent_style = space
-indent_size = 4
-end_of_line = lf
-charset = utf-8
-trim_trailing_whitespace = true
-insert_final_newline = true
-
-[*.md]
-trim_trailing_whitespace = false
-
-[*.yaml]
-indent_size = 2
-
-[*.yml]
-indent_size = 2
-
-[*.vue]
-trim_trailing_whitespace = false
-
-[*.go]
-indent_style = tab

.eslintrc.js

@@ -1,128 +0,0 @@
-module.exports = {
-    ignorePatterns: [
-        "test/*",
-        "server/modules/apicache/*",
-        "src/util.js"
-    ],
-    root: true,
-    env: {
-        browser: true,
-        commonjs: true,
-        es2020: true,
-        node: true,
-    },
-    extends: [
-        "eslint:recommended",
-        "plugin:vue/vue3-recommended",
-    ],
-    parser: "vue-eslint-parser",
-    parserOptions: {
-        parser: "@babel/eslint-parser",
-        sourceType: "module",
-        requireConfigFile: false,
-    },
-    rules: {
-        "yoda": "error",
-        eqeqeq: [ "warn", "smart" ],
-        "linebreak-style": [ "error", "unix" ],
-        "camelcase": [ "warn", {
-            "properties": "never",
-            "ignoreImports": true
-        }],
-        "no-unused-vars": [ "warn", {
-            "args": "none"
-        }],
-        indent: [
-            "error",
-            4,
-            {
-                ignoredNodes: [ "TemplateLiteral" ],
-                SwitchCase: 1,
-            },
-        ],
-        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/attribute-hyphenation": "off",     // This change noNL to "no-n-l" unexpectedly
-        "vue/multi-word-component-names": "off",
-        "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",
-        "key-spacing": "warn",
-        "keyword-spacing": "warn",
-        "space-infix-ops": "warn",
-        "arrow-spacing": "warn",
-        "no-trailing-spaces": "error",
-        "no-constant-condition": [ "error", {
-            "checkLoops": false,
-        }],
-        "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",
-        "array-bracket-newline": [ "error", "consistent" ],
-        "eol-last": [ "error", "always" ],
-        //"prefer-template": "error",
-        "template-curly-spacing": [ "warn", "never" ],
-        "comma-dangle": [ "warn", "only-multiline" ],
-        "no-empty": [ "error", {
-            "allowEmptyCatch": true
-        }],
-        "no-control-regex": "off",
-        "one-var": [ "error", "never" ],
-        "max-statements-per-line": [ "error", { "max": 1 }]
-    },
-    "overrides": [
-        {
-            "files": [ "src/languages/*.js", "src/icon.js" ],
-            "rules": {
-                "comma-dangle": [ "error", "always-multiline" ],
-            }
-        },
-
-        // Override for jest puppeteer
-        {
-            "files": [
-                "**/*.spec.js",
-                "**/*.spec.jsx"
-            ],
-            env: {
-                jest: true,
-            },
-            globals: {
-                page: true,
-                browser: true,
-                context: true,
-                jestPuppeteer: true,
-            },
-        }
-    ]
-};

.github/FUNDING.yml

@@ -1,12 +0,0 @@
-# These are supported funding model platforms
-
-github: louislam # Replace with up to 4 GitHub Sponsors-enabled usernames e.g., [user1, user2]
-#patreon: # Replace with a single Patreon username
-open_collective: uptime-kuma # Replace with a single Open Collective username
-#ko_fi: # Replace with a single Ko-fi username
-#tidelift: # Replace with a single Tidelift platform-name/package-name e.g., npm/babel
-#community_bridge: # Replace with a single Community Bridge project-name e.g., cloud-foundry
-#liberapay: # Replace with a single Liberapay username
-#issuehunt: # Replace with a single IssueHunt username
-#otechie: # Replace with a single Otechie username
-#custom: # Replace with up to 4 custom sponsorship URLs e.g., ['link1', 'link2']

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

@@ -1,74 +0,0 @@
-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/bug_report.yaml

@@ -1,99 +0,0 @@
-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/feature_request.yaml

@@ -1,59 +0,0 @@
-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/security.md

@@ -1,19 +0,0 @@
----
-
-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/PULL_REQUEST_TEMPLATE.md

@@ -1,34 +0,0 @@
-⚠️⚠️⚠️ 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
-
-Tick the checkbox if you understand [x]: 
-- [ ] I have read and understand the pull request rules.
-
-# Description
-
-Fixes #(issue)
-
-## Type of change
-
-Please delete any options that are not relevant.
-
-- Bug fix (non-breaking change which fixes an issue)
-- User interface (UI)
-- New feature (non-breaking change which adds functionality)
-- Breaking change (fix or feature that would cause existing functionality to not work as expected)
-- Other
-- This change requires a documentation update
-
-## Checklist
-
-- [ ] 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)
-
-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.

.github/config/exclude.txt

@@ -1 +0,0 @@
-# This is a .gitignore style file for 'GrantBirki/json-yaml-validate' Action workflow

.github/workflows/auto-test.yml

@@ -1,107 +0,0 @@
-# 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
-
-name: Auto Test
-
-on:
-  push:
-    branches: [ master, 1.23.X ]
-    paths-ignore:
-      - '*.md'
-  pull_request:
-    branches: [ master, 1.23.X ]
-    paths-ignore:
-      - '*.md'
-
-jobs:
-  auto-test:
-    needs: [ check-linters ]
-    runs-on: ${{ matrix.os }}
-    timeout-minutes: 15
-
-    strategy:
-      matrix:
-        os: [macos-latest, ubuntu-latest, windows-latest, ARM64]
-        node: [ 16, 20.5 ]
-        # See supported Node.js release schedule at https://nodejs.org/en/about/releases/
-
-    steps:
-    - run: git config --global core.autocrlf false  # Mainly for Windows
-    - uses: actions/checkout@v4
-
-    - name: Use Node.js ${{ matrix.node }}
-      uses: actions/setup-node@v4
-      with:
-        node-version: ${{ matrix.node }}
-    - run: npm ci
-    - run: npm run build
-    - run: npm test
-      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:
-    needs: [ check-linters ]
-    runs-on: ${{ matrix.os }}
-    timeout-minutes: 15
-
-    strategy:
-      matrix:
-        os: [ ARMv7 ]
-        node: [ 16, 20.5 ]
-        # See supported Node.js release schedule at https://nodejs.org/en/about/releases/
-
-    steps:
-      - run: git config --global core.autocrlf false  # Mainly for Windows
-      - uses: actions/checkout@v4
-
-      - name: Use Node.js ${{ matrix.node }}
-        uses: actions/setup-node@v4
-        with:
-          node-version: ${{ matrix.node }}
-      - run: npm ci --production
-
-  check-linters:
-    runs-on: ubuntu-latest
-
-    steps:
-    - run: git config --global core.autocrlf false  # Mainly for Windows
-    - uses: actions/checkout@v4
-
-    - name: Use Node.js 20
-      uses: actions/setup-node@v4
-      with:
-        node-version: 20.5
-    - run: npm ci
-    - run: npm run lint:prod
-
-  e2e-tests:
-    needs: [ check-linters ]
-    runs-on: ubuntu-latest
-    steps:
-    - run: git config --global core.autocrlf false  # Mainly for Windows
-    - uses: actions/checkout@v4
-
-    - name: Use Node.js 16
-      uses: actions/setup-node@v4
-      with:
-        node-version: 16
-    - run: npm ci
-    - run: npm run build
-    - run: npm run cy:test
-
-  frontend-unit-tests:
-    needs: [ check-linters ]
-    runs-on: ubuntu-latest
-    steps:
-    - run: git config --global core.autocrlf false  # Mainly for Windows
-    - uses: actions/checkout@v4
-
-    - name: Use Node.js 16
-      uses: actions/setup-node@v4
-      with:
-        node-version: 16
-    - run: npm ci
-    - run: npm run build
-    - run: npm run cy:run:unit

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

@@ -1,25 +0,0 @@
-name: Close Incorrect Issue
-
-on:
-  issues:
-    types: [opened]
-
-jobs:
-  close-incorrect-issue:
-    runs-on: ${{ matrix.os }}
-
-    strategy:
-      matrix:
-        os: [ubuntu-latest]
-        node-version: [16]
-
-    steps:
-    - uses: actions/checkout@v4
-
-    - name: Use Node.js ${{ matrix.node-version }}
-      uses: actions/setup-node@v4
-      with:
-        node-version: ${{ matrix.node-version }}
-        cache: 'npm'
-    - run: npm ci
-    - run: node extra/close-incorrect-issue.js ${{ secrets.GITHUB_TOKEN }} ${{ github.event.issue.number }} ${{ github.event.issue.user.login }}

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

@@ -1,27 +0,0 @@
-name: json-yaml-validate
-on:
-  push:
-    branches:
-      - master
-  pull_request:
-    branches:
-      - master
-      - 1.23.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@v4
-
-      - name: json-yaml-validate
-        id: json-yaml-validate
-        uses: GrantBirki/json-yaml-validate@v2.4.0
-        with:
-          comment: "true" # enable comment mode
-          exclude_file: ".github/config/exclude.txt" # gitignore style file for exclusions

.github/workflows/stale-bot.yml

@@ -1,22 +0,0 @@
-name: 'Automatically close stale issues and PRs'
-on:
-  workflow_dispatch:
-  schedule:
-    - cron: '0 */6 * * *'
-#Run every 6 hours
-
-jobs:
-  stale:
-    runs-on: ubuntu-latest
-    steps:
-      - uses: actions/stale@v8
-        with:
-          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.'
-          close-issue-message: 'This issue was closed because it has been stalled for 2 days with no activity.'
-          days-before-stale: 90
-          days-before-close: 2
-          days-before-pr-stale: 999999999
-          days-before-pr-close: 1
-          exempt-issue-labels: 'News,Medium,High,discussion,bug,doc,feature-request'
-          exempt-issue-assignees: 'louislam'
-          operations-per-run: 200

.gitignore

@@ -1,28 +0,0 @@
-node_modules
-.DS_Store
-dist
-dist-ssr
-*.local
-.idea
-
-/data
-!/data/.gitkeep
-.vscode
-
-/private
-/out
-/tmp
-.env
-
-cypress/videos
-cypress/screenshots
-
-/extra/healthcheck.exe
-/extra/healthcheck
-/extra/healthcheck-armv7
-
-extra/exe-builder/bin
-extra/exe-builder/obj
-
-.vs
-.vscode

.npmrc

@@ -1 +0,0 @@
-legacy-peer-deps=true

.stylelintrc

@@ -1,16 +0,0 @@
-{
-    "extends": "stylelint-config-standard",
-    "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",
-        "shorthand-property-no-redundant-values": null,
-        "color-hex-length": null,
-        "declaration-block-no-redundant-longhand-properties": null,
-        "at-rule-no-unknown": null
-    }
-}

CNAME

@@ -1 +0,0 @@
-git.kuma.pet

CODE_OF_CONDUCT.md

@@ -1,128 +0,0 @@
-# Contributor Covenant Code of Conduct
-
-## Our Pledge
-
-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, religion, or sexual identity
-and orientation.
-
-We pledge to act and interact in ways that contribute to an open, welcoming,
-diverse, inclusive, and healthy community.
-
-## Our Standards
-
-Examples of behavior that contributes to a positive environment for our
-community include:
-
-* Demonstrating empathy and kindness toward other people
-* Being respectful of differing opinions, viewpoints, and experiences
-* Giving and gracefully accepting constructive feedback
-* 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 community
-
-Examples of unacceptable behavior include:
-
-* The use of sexualized language or imagery, and sexual attention or
-  advances of any kind
-* Trolling, insulting or derogatory comments, and personal or political attacks
-* Public or private harassment
-* Publishing others' private information, such as a physical or email
-  address, without their explicit permission
-* Other conduct which could reasonably be considered inappropriate in a
-  professional setting
-
-## Enforcement Responsibilities
-
-Community leaders are responsible for clarifying and enforcing our standards of
-acceptable behavior and will take appropriate and fair corrective action in
-response to any behavior that they deem inappropriate, threatening, offensive,
-or harmful.
-
-Community leaders have the right and responsibility to remove, edit, or reject
-comments, commits, code, wiki edits, issues, and other contributions that are
-not aligned to this Code of Conduct, and will communicate reasons for moderation
-decisions when appropriate.
-
-## Scope
-
-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 e-mail address,
-posting via an official social media account, or acting as an appointed
-representative at an online or offline event.
-
-## Enforcement
-
-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 fairly.
-
-All community leaders are obligated to respect the privacy and security of the
-reporter of any incident.
-
-## Enforcement Guidelines
-
-Community leaders will follow these Community Impact Guidelines in determining
-the consequences for any action they deem in violation of this Code of Conduct:
-
-### 1. Correction
-
-**Community Impact**: Use of inappropriate language or other behavior deemed
-unprofessional or unwelcome in the community.
-
-**Consequence**: A private, written warning from community leaders, providing
-clarity around the nature of the violation and an explanation of why the
-behavior was inappropriate. A public apology may be requested.
-
-### 2. Warning
-
-**Community Impact**: A violation through a single incident or series
-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 ban.
-
-### 3. Temporary Ban
-
-**Community Impact**: A serious violation of community standards, including
-sustained inappropriate behavior.
-
-**Consequence**: A temporary ban from any sort of interaction or public
-communication with the community for a specified period of time. No public or
-private interaction with the people involved, including unsolicited interaction
-with those enforcing the Code of Conduct, is allowed during this period.
-Violating these terms may lead to a permanent ban.
-
-### 4. Permanent Ban
-
-**Community Impact**: Demonstrating a pattern of violation of community
-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 community.
-
-## Attribution
-
-This Code of Conduct is adapted from the [Contributor Covenant][homepage],
-version 2.0, available at
-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](https://github.com/mozilla/diversity).
-
-[homepage]: https://www.contributor-covenant.org
-
-For answers to common questions about this code of conduct, see the FAQ at
-https://www.contributor-covenant.org/faq. Translations are available at
-https://www.contributor-covenant.org/translations.

CONTRIBUTING.md

@@ -1,286 +0,0 @@
-# Project Info
-
-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.
-
-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 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.
-
-## Key Technical Skills
-
-- 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)
-- data (App data)
-- db (Base database and migration scripts)
-- dist (Frontend build)
-- docker (Dockerfiles)
-- extra (Extra useful scripts)
-- public (Frontend resources for dev only)
-- server (Server source code)
-- src (Frontend source code)
-- test (unit test)
-
-## Can I create a pull request for Uptime Kuma?
-
-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.
-
-Here are some references:
-
-### ✅ Usually accepted:
-- Bug fix
-- 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("...")`
-
-### ⚠️ Discussion required:
-- Large pull requests
-- New features
-
-### ❌ Won't be merged:
-- A dedicated PR for translating existing languages (see [these instructions](https://github.com/louislam/uptime-kuma/blob/master/src/lang/README.md))
-- 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.
-
-The above cases may not cover all possible situations.
-
-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.
-
-I will assign your pull request to a [milestone](https://github.com/louislam/uptime-kuma/milestones), if I plan to review and merge it.
-
-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.
-
-
-### Recommended Pull Request Guideline
-
-Before deep into coding, discussion first is preferred. Creating an empty pull request for discussion would be recommended.
-
-1. Fork the project
-1. Clone your fork repo to local
-1. Create a new branch
-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
-
-## Project Styles
-
-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.
-
-- 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
-- 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`
-- Easy to use
-- The web UI styling should be consistent and nice
-
-## Coding Styles
-
-- 4 spaces indentation
-- Follow `.editorconfig`
-- Follow ESLint
-- Methods and functions should be documented with JSDoc
-
-## Name Conventions
-
-- Javascript/Typescript: camelCaseType
-- SQLite: snake_case (Underscore)
-- CSS/SCSS: kebab-case (Dash)
-
-## Tools
-
-- [`Node.js`](https://nodejs.org/) >= 14
-- [`npm`](https://www.npmjs.com/) >= 8.5
-- [`git`](https://git-scm.com/)
-- IDE that supports [`ESLint`](https://eslint.org/) and EditorConfig (I am using [`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/))
-
-## Install Dependencies for Development
-
-```bash
-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.
-
-```bash
-npm run dev
-```
-
-But sometimes, you would like to restart the server, but not the frontend, you can run these commands in two terminals:
-```
-npm run start-frontend-dev
-npm run start-server-dev
-```
-
-## Backend Server
-
-It binds to `0.0.0.0:3001` by default.
-
-
-It is mainly a socket.io app + express.js.
-
-express.js is used for: 
-- 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
-
-
-### Structure in /server/
-
-- jobs/ (Jobs that are running in another process)
-- model/ (Object model, auto-mapping to the database table name)
-- modules/ (Modified 3rd-party modules)
-- monitor_types (Monitor Types)
-- notification-providers/ (individual notification logic)
-- routers/ (Express Routers)
-- socket-handler (Socket.io Handlers)
-- 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 development only. 
-
-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 by Vue Router.
-
-The router is in `src/router.js`
-
-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
-
-1. Create `patch-{name}.sql` in `./db/`
-2. Add your patch filename in the `patchList` list in `./server/database.js`
-
-## Unit Test
-
-```bash
-npm run build
-npm test
-```
-
-## Dependencies
-
-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:
-
-- Frontend dependencies = "devDependencies"
-  - Examples: vue, chart.js
-- Backend dependencies = "dependencies"
-  - Examples: socket.io, sqlite3
-- Development dependencies = "devDependencies"
-  - Examples: eslint, sass
-
-### Update Dependencies
-
-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.
-
-Patch release = the third digit ([Semantic Versioning](https://semver.org/))
-
-If for security / bug / other reasons, a library must be updated, breaking 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 grammar in the documentation or code.
-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 wiki's repo, I have set up another repo to do that.
-
-https://github.com/louislam/uptime-kuma-wiki
-
-## Maintainer
-
-Check the latest issues and pull requests:
-https://github.com/louislam/uptime-kuma/issues?q=sort%3Aupdated-desc
-
-### Release Procedures
-
-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`
-3. `npm run release-final with env vars: `VERSION` and `GITHUB_TOKEN`
-4. Wait until the `Press any key to continue`
-5. `git push`
-6. Publish the release note as 1.X.X 
-7. Press any key to continue
-8. Deploy to the demo server: `npm run deploy-demo-server`
-
-Checking:
-
-- 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
-
-### Release Beta Procedures
-
-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
-
-### Release Wiki
-
-#### 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
-```

LICENSE

@@ -1,21 +0,0 @@
-MIT License
-
-Copyright (c) 2021 Louis Lam
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-SOFTWARE.

README.md

@@ -1,193 +0,0 @@
-<div align="center" width="100%">
-    <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" /></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="" />
-
-## 🥔 Live Demo
-
-Try it!
-
-- 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. 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 / 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
-* [Multi Languages](https://github.com/louislam/uptime-kuma/tree/master/src/lang)
-* Multiple status pages
-* Map status pages to specific domains
-* Ping chart
-* Certificate info
-* Proxy support
-* 2FA support
-
-## 🔧 How to Install
-
-### 🐳 Docker
-
-```bash
-docker run -d --restart=always -p 3001:3001 -v uptime-kuma:/app/data --name uptime-kuma louislam/uptime-kuma:1
-```
-
-⚠️ Please use a **local volume** only. Other types such as NFS are not supported.
-
-Uptime Kuma is now running on http://localhost:3001
-
-### 💪🏻 Non-Docker
-
-Requirements:
-- Platform
-  - ✅ Major Linux distros such as Debian, Ubuntu, CentOS, Fedora and ArchLinux etc.
-  - ✅ Windows 10 (x64), Windows Server 2012 R2 (x64) or higher
-  - ❌ Replit / Heroku
-- [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 to the latest version
-npm install npm -g
-
-git clone https://github.com/louislam/uptime-kuma.git
-cd uptime-kuma
-npm run setup
-
-# Option 1. Try it
-node server/server.js
-
-# (Recommended) Option 2. Run in the background using PM2
-# Install PM2 if you don't have it:
-npm install pm2 -g && pm2 install pm2-logrotate
-
-# Start Server
-pm2 start server/server.js --name uptime-kuma
-
-
-```
-Uptime Kuma is now running on http://localhost:3001
-
-More useful PM2 Commands
-
-```bash
-# If you want to see the current console output
-pm2 monit
-
-# If you want to add it to startup
-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.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
-
-## 🆙 How to Update
-
-Please read:
-
-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
-
-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 />
-
-## 🖼 More Screenshots
-
-Light Mode:
-
-<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="" />
-
-Settings Page:
-
-<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="" />
-
-## 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 close ones is statping. Unfortunately, it is not stable and no longer maintained.
-* 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 REST API.
-* Deploy my first Docker image to Docker Hub.
-
-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 response 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:
-
-- [GitHub Issues](https://github.com/louislam/uptime-kuma/issues)
-- [Subreddit r/Uptime kuma](https://www.reddit.com/r/UptimeKuma/)
-
-My Reddit account: [u/louislamlam](https://reddit.com/u/louislamlam).  
-You can mention me if you ask a question on Reddit.
-
-
-## Contribute
-
-### 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
-
-### Test Beta Version
-
-Check out the latest beta release here: https://github.com/louislam/uptime-kuma/releases
-
-### Bug Reports / Feature Requests
-If you want to report a bug or request a new feature, feel free to open a [new issue](https://github.com/louislam/uptime-kuma/issues).
-
-### Translations
-If you want to translate Uptime Kuma into your language, please visit [Weblate Readme](https://github.com/louislam/uptime-kuma/blob/master/src/lang/README.md).
-
-## 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.
-
-### 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

@@ -1,30 +0,0 @@
-# Security Policy
-
-## Reporting a Vulnerability
-
-1. Please report security issues to 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
-
-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 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. All `1.X.X` versions are upgradable to the latest version.
-
-### Upgradable Docker Tags
-
-| Tag | Supported          |
-| ------- | ------------------ |
-| 1 | :white_check_mark: |
-| 1-debian | :white_check_mark: |
-| latest | :white_check_mark: |
-| debian | :white_check_mark: |
-| 1-alpine | ⚠️ Deprecated |
-| alpine | ⚠️ Deprecated |
-| All other tags  | ❌ |

ansible/.gitignore

@@ -0,0 +1 @@
+roles/nginx/files/ssl/*

ansible/README.md

@@ -0,0 +1,39 @@
+# Ansible Playbook to install uptime kuma using docker
+
+This playbook comes with three tags
+
+1. requirements (will install anything needed to make next parts working)
+2. docker (to install docker)
+3. nginx (to install nginx using docker with ssl)
+4. uptime kuma (to install uptime kuma using docker)
+
+To see more info see docker-compose, tasks and config files 
+I will try to make this readme better
+
+## To run it
+1. install ansible see [here](https://docs.ansible.com/ansible/latest/installation_guide/intro_installation.html)
+2. run `ansible-galaxy install -r ansible-requirements.yml` to get requirements
+3. prepare inventory hosts
+4. put your certificates in files section in nginx role with this structure below:
+```
+ansible -> roles -> nginx -> files -> ssl -> <uptime kuma domain>.fullchain.pem
+ansible -> roles -> nginx -> files -> ssl -> <uptime kuma domain>.privkey.pem
+```
+5. to run playbook
+```bash
+ansible-playbook ./playbook.yml -i <your inventory path> -e "kuma_domain=<uptime kuma domain>" -e "kuma_image_os=<alpine or debian>" -e "kuma_image_version=<version>"
+```
+you can use other ansible playbook options too
+
+> Note: Replace `<uptime kuma domain>` with your desired domain for uptime kuma
+
+> replace `<version>` with a version from https://github.com/louislam/uptime-kuma/releases
+> replace `<alpine or debian>` with one of options
+
+> `-e "kuma_image_os=<alpine or debian>" -e "kuma_image_version=<version>"` is not required and you can remove this part or change only one of them (kuma_image_os is debian & kuma_image_version is 1 by default)
+
+> If you are not using root user as your ansible_user use -bK option to become root
+
+> instead of `-e "kuma_image_os=<alpine or debian>" -e "kuma_image_version=<version>"` You can use `-e kuma_tag=<uptime kuma full tag>` and replace `<uptime kuma full tag>` with your desired tag (e.g. `latest`)
+
+> you can also create a yaml file with variables that you want to set & use it (also: ansible-vars)

ansible/ansible-requirements.yml

@@ -0,0 +1,6 @@
+roles:
+  - src: geerlingguy.docker
+  - src: geerlingguy.pip
+
+collections:
+  - name: community.docker

ansible/playbook.yml

@@ -0,0 +1,20 @@
+- name: install uptime kuma with nginx connected
+  hosts: all
+
+  vars:
+    pip_install_packages:
+      - name: wheel
+      - name: pip
+        state: latest
+      - name: setuptools
+      - name: cffi
+      - name: docker
+      - name: dockerpty
+    docker_compose_version: "v2.0.1"
+
+  roles:
+    - {role: requirements,            tags: ["docker", "requirements"]}
+    - {role: geerlingguy.docker,      tags: ["docker"]}
+    - {role: geerlingguy.pip,         tags: ["docker"]}
+    - {role: nginx,                   tags: ["nginx"]}
+    - {role: uptime-kuma,             tags: ["kuma"]}

ansible/roles/nginx/tasks/main.yml

@@ -0,0 +1,22 @@
+- name: Ensure Volumes & Files directories exists
+  file:
+    dest: "{{item}}"
+    state: directory
+  loop:
+    - /compose
+    - /compose/volumes
+    - /compose/volumes/nginx
+    - /compose/volumes/nginx/log/{{ kuma_domain }}
+
+- name: Ensure nginx SSL certificates exist
+  copy:
+    src: ssl
+    dest: /compose/volumes/nginx
+    mode: 'preserve'
+    group: root
+    owner: root
+
+- name: Ensure config files are updated
+  template:
+    src: "nginx.conf"
+    dest: /compose/volumes/nginx/nginx.conf

ansible/roles/nginx/templates/nginx.conf

@@ -0,0 +1,88 @@
+user nginx;
+worker_processes auto;
+
+pid         /var/run/nginx.pid;
+error_log   /var/log/nginx/error.log;
+
+events {
+    worker_connections 2048;
+}
+
+http {
+    sendfile on;
+    tcp_nopush on;
+    tcp_nodelay on;
+    keepalive_timeout 65;
+    types_hash_max_size 2048;
+    server_tokens off;
+
+    default_type application/octet-stream;
+
+    ### SSL Settings for all servers (https://ssl-config.mozilla.org/#server=nginx&server-version=1.17.2&config=intermediate)
+    # certs sent to the client in SERVER HELLO are concatenated in ssl_certificate
+    ssl_certificate     /etc/nginx/ssl/{{ kuma_domain }}.fullchain.pem;
+    ssl_certificate_key /etc/nginx/ssl/{{ kuma_domain }}.privkey.pem;
+    ssl_session_timeout 1d;
+    ssl_session_cache shared:MozSSL:10m;  # about 40000 sessions
+    ssl_session_tickets off;
+
+    # intermediate configuration
+    ssl_protocols TLSv1.2 TLSv1.3;
+    ssl_ciphers ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:DHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-GCM-SHA384;
+    ssl_prefer_server_ciphers off;
+
+    # curl https://ssl-config.mozilla.org/ffdhe2048.txt > /etc/nginx/ssl/dhparam.pem (TODO: check if it's secure to use others DH parameters!)
+    # openssl dhparam -out /etc/nginx/ssl/dhparam.pem 4096
+    ssl_dhparam /etc/nginx/ssl/dhparam.pem;
+
+    # HSTS (ngx_http_headers_module is required) (63072000 seconds)
+    add_header Strict-Transport-Security "max-age=63072000" always;
+
+    # OCSP stapling
+    ssl_stapling on;
+    ssl_stapling_verify on;
+
+    log_format main '$remote_addr - $remote_user [$time_local] "$request_method $scheme://$host$request_uri $server_protocol" $status $body_bytes_sent '
+                 '"$http_referer" "$http_user_agent" $request_time $upstream_response_time UPA:$upstream_addr BYS:$bytes_sent BYR:$request_length';
+    access_log  /var/log/nginx/access.log main;
+
+    ### Set additional headers to be send to upstream
+    proxy_set_header    Host                $http_host;
+    proxy_set_header    X-Real-IP           $remote_addr;
+    proxy_set_header    X-Forwarded-For     $proxy_add_x_forwarded_for;
+    proxy_set_header    X-Forwarded-Proto   $scheme;
+
+    # Remove Headers that gonna be sent to client
+    proxy_hide_header   X-Powered-By;
+    proxy_hide_header   Server;
+
+    # Redirect HTTP request to HTTPS
+    server {
+      listen              80 default_server;
+      server_name         {{ kuma_domain }};
+      return 302 https://$host$request_uri;
+    }
+
+    server {
+        server_name     {{ kuma_domain }};
+        listen          443 ssl http2 default_server;
+
+        access_log      /var/log/nginx/{{ kuma_domain }}/access.log main;
+        error_log       /var/log/nginx/{{ kuma_domain }}/error.log;
+
+        location / {
+            # rewrite ^/(.*)/$ /$1 permanent;
+            ### redirect urls with trailing slash to non-trailing slash
+            # https://serverfault.dev/questions/597302/removing-the-trailing-slash-from-a-url-with-nginx
+            # location ~ (?<no_slash>.+)/$ {
+            #     return 302 https://$host$no_slash;
+            # }
+            proxy_set_header   X-Real-IP $remote_addr;
+            proxy_set_header   X-Forwarded-For $proxy_add_x_forwarded_for;
+            proxy_pass         http://uptime-kuma:3001/;
+            proxy_http_version 1.1;
+            proxy_set_header   Upgrade $http_upgrade;
+            proxy_set_header   Connection "upgrade";
+        }
+    }
+}

ansible/roles/requirements/tasks/main.yml

@@ -0,0 +1,11 @@
+---
+- name: Ensure {{inventory_hostname}} is set as hostname
+  hostname:
+    name: "{{inventory_hostname}}"
+  tags: ["hostname"]
+
+- include_tasks: setup-RedHat.yml
+  when: ansible_os_family == 'RedHat'
+
+- include_tasks: setup-Debian.yml
+  when: ansible_os_family == 'Debian'

ansible/roles/requirements/tasks/setup-Debian.yml

@@ -0,0 +1,9 @@
+- name: Ensure packages for some requirements are installed
+  apt:
+    pkg:
+      - libffi-dev
+      - libzbar-dev
+      - libzbar0
+      - python3-docopt
+    update_cache: yes
+    state: present

ansible/roles/requirements/tasks/setup-RedHat.yml

@@ -0,0 +1,9 @@
+- name: Ensure packages for some requirements are installed
+  dnf:
+    name:
+      - libffi-devel
+      - zbar-devel
+      - zbar
+      - python3-docopt
+    update_cache: yes
+    state: present

ansible/roles/uptime-kuma/defaults/main.yml

@@ -0,0 +1,4 @@
+---
+kuma_image_version: '1'
+kuma_image_os: 'debian'
+kuma_tag: "{{kuma_image_version}}-{{kuma_image_os}}"

ansible/roles/uptime-kuma/tasks/main.yml

@@ -0,0 +1,23 @@
+- name: Ensure Volumes & Files directories exists
+  file:
+    dest: "{{item}}"
+    state: directory
+  loop:
+    - /compose
+    - /compose/kuma
+    - /compose/volumes
+    - /compose/volumes/kuma
+
+- name: Ensure docker-compose file has been updated
+  template:
+    src: "{{item}}"
+    dest: /compose/kuma/
+  loop:
+    - docker-compose.yml
+
+- name: Ensure uptime-kuma is up
+  community.docker.docker_compose:
+    state: present
+    project_src: /compose/kuma
+    pull: yes
+    recreate: always

ansible/roles/uptime-kuma/templates/docker-compose.yml

@@ -0,0 +1,29 @@
+version: '3.3'
+services:
+    uptime-kuma:
+        restart: always
+        networks:
+            - uptime-kuma
+        expose:
+            - 3001
+        volumes:
+            - '/compose/volumes/uptime-kuma:/app/data'
+        container_name: uptime-kuma
+        image: 'louislam/uptime-kuma:{{kuma_tag}}'
+
+    nginx:
+        ports:
+            - 443:443
+            - 80:80
+        networks:
+            - uptime-kuma
+        depends_on:
+            - uptime-kuma
+        restart: always
+        image: nginx:stable-alpine
+        volumes:
+            - '/compose/volumes/nginx/:/etc/nginx/'
+            - '/compose/volumes/nginx/log/{{ kuma_domain }}:/var/log/nginx/{{ kuma_domain }}/'
+
+networks:
+    uptime-kuma:

babel.config.js

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

config/cypress.config.js

@@ -1,28 +0,0 @@
-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

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

config/jest-backend.config.js

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

config/vite.config.js

@@ -1,59 +0,0 @@
-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";
-
-const postCssScss = require("postcss-scss");
-const postcssRTLCSS = require("postcss-rtlcss");
-
-const viteCompressionFilter = /\.(js|mjs|json|css|html|svg)$/i;
-
-// https://vitejs.dev/config/
-export default defineConfig({
-    server: {
-        port: 3000,
-    },
-    define: {
-        "FRONTEND_VERSION": JSON.stringify(process.env.npm_package_version),
-        "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: [
-        vue(),
-        legacy({
-            targets: [ "since 2015" ],
-        }),
-        visualizer({
-            filename: "tmp/dist-stats.html"
-        }),
-        viteCompression({
-            algorithm: "gzip",
-            filter: viteCompressionFilter,
-        }),
-        viteCompression({
-            algorithm: "brotliCompress",
-            filter: viteCompressionFilter,
-        }),
-    ],
-    css: {
-        postcss: {
-            "parser": postCssScss,
-            "map": false,
-            "plugins": [ postcssRTLCSS ]
-        }
-    },
-    build: {
-        commonjsOptions: {
-            include: [ /.js$/ ],
-        },
-        rollupOptions: {
-            output: {
-                manualChunks(id, { getModuleInfo, getModuleIds }) {
-
-                }
-            }
-        },
-    }
-});

db/patch-2fa-invalidate-used-token.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;
-
-ALTER TABLE user
-    ADD twofa_last_token VARCHAR(6);
-
-COMMIT;

db/patch-2fa.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;
-
-ALTER TABLE user
-    ADD twofa_secret VARCHAR(64);
-
-ALTER TABLE user
-    ADD twofa_status BOOLEAN default 0 NOT NULL;
-
-COMMIT;

db/patch-add-certificate-expiry-status-page.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;
-
-ALTER TABLE status_page
-    ADD show_certificate_expiry BOOLEAN default 0 NOT NULL;
-
-COMMIT;

db/patch-add-clickable-status-page-link.sql

@@ -1,5 +0,0 @@
--- You should not modify if this have pushed to Github, unless it does serious wrong with the db.
-BEGIN TRANSACTION;
-ALTER TABLE monitor_group
-    ADD send_url BOOLEAN DEFAULT 0 NOT NULL;
-COMMIT;

db/patch-add-description-monitor.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;
-
-ALTER TABLE monitor
-    ADD description TEXT default null;
-
-COMMIT;

db/patch-add-docker-columns.sql

@@ -1,18 +0,0 @@
--- You should not modify if this have pushed to Github, unless it does serious wrong with the db.
-BEGIN TRANSACTION;
-
-CREATE TABLE docker_host (
-	id INTEGER NOT NULL PRIMARY KEY AUTOINCREMENT,
-	user_id INT NOT NULL,
-	docker_daemon VARCHAR(255),
-	docker_type VARCHAR(255),
-	name VARCHAR(255)
-);
-
-ALTER TABLE monitor
-	ADD docker_host INTEGER REFERENCES docker_host(id);
-
-ALTER TABLE monitor
-	ADD docker_container VARCHAR(255);
-
-COMMIT;

db/patch-add-gamedig-given-port.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;
-
-ALTER TABLE monitor
-    ADD gamedig_given_port_only BOOLEAN default 1 not null;
-
-COMMIT;

db/patch-add-gamedig-monitor.sql

@@ -1,5 +0,0 @@
-BEGIN TRANSACTION;
-
- ALTER TABLE monitor
-     ADD game VARCHAR(255);
- COMMIT

db/patch-add-google-analytics-status-page-tag.sql

@@ -1,4 +0,0 @@
--- You should not modify if this have pushed to Github, unless it does serious wrong with the db.
-BEGIN TRANSACTION;
-ALTER TABLE status_page ADD google_analytics_tag_id VARCHAR;
-COMMIT;

db/patch-add-invert-keyword.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;
-
-ALTER TABLE monitor
-    ADD invert_keyword BOOLEAN default 0 not null;
-
-COMMIT;

db/patch-add-other-auth.sql

@@ -1,18 +0,0 @@
-BEGIN TRANSACTION;
-
-  ALTER TABLE monitor
-      ADD auth_method VARCHAR(250);
-
-  ALTER TABLE monitor
-      ADD auth_domain TEXT;
-  ALTER TABLE monitor
-
-      ADD auth_workstation TEXT;
-
-COMMIT;
-
-BEGIN TRANSACTION;
-  UPDATE monitor
-        SET auth_method = 'basic'
-        WHERE basic_auth_user is not null;
-COMMIT;

db/patch-add-parent-monitor.sql

@@ -1,6 +0,0 @@
-BEGIN TRANSACTION;
-
-ALTER TABLE monitor
-    ADD parent INTEGER REFERENCES [monitor] ([id]) ON DELETE SET NULL ON UPDATE CASCADE;
-
-COMMIT

db/patch-add-radius-monitor.sql

@@ -1,18 +0,0 @@
-BEGIN TRANSACTION;
-
-ALTER TABLE monitor
-    ADD radius_username VARCHAR(255);
-
-ALTER TABLE monitor
-    ADD radius_password VARCHAR(255);
-
-ALTER TABLE monitor
-    ADD radius_calling_station_id VARCHAR(50);
-
-ALTER TABLE monitor
-    ADD radius_called_station_id VARCHAR(50);
-
-ALTER TABLE monitor
-    ADD radius_secret VARCHAR(255);
-
-COMMIT

db/patch-add-retry-interval-monitor.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;
-
-ALTER TABLE monitor
-    ADD retry_interval INTEGER default 0 not null;
-
-COMMIT;

db/patch-add-sqlserver-monitor.sql

@@ -1,10 +0,0 @@
-BEGIN TRANSACTION;
-
- ALTER TABLE monitor
-     ADD database_connection_string VARCHAR(2000);
-
- ALTER TABLE monitor
-     ADD database_query TEXT;
-
-
- COMMIT

db/patch-add-timeout-monitor.sql

@@ -1,6 +0,0 @@
--- You should not modify if this have pushed to Github, unless it does serious wrong with the db.
-BEGIN TRANSACTION;
-
-ALTER TABLE monitor
-    ADD timeout DOUBLE default 0 not null;
-COMMIT;

db/patch-added-json-query.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;
-
-ALTER TABLE monitor
-	ADD json_path TEXT;
-
-ALTER TABLE monitor
-	ADD expected_value VARCHAR(255);
-
-COMMIT;

db/patch-added-kafka-producer.sql

@@ -1,22 +0,0 @@
--- You should not modify if this have pushed to Github, unless it does serious wrong with the db.
-BEGIN TRANSACTION;
-
-ALTER TABLE monitor
-	ADD kafka_producer_topic VARCHAR(255);
-
-ALTER TABLE monitor
-	ADD kafka_producer_brokers TEXT;
-
-ALTER TABLE monitor
-	ADD kafka_producer_ssl INTEGER;
-
-ALTER TABLE monitor
-	ADD kafka_producer_allow_auto_topic_creation VARCHAR(255);
-
-ALTER TABLE monitor
-	ADD kafka_producer_sasl_options TEXT;
-
-ALTER TABLE monitor
-	ADD kafka_producer_message TEXT;
-
-COMMIT;

db/patch-added-mqtt-monitor.sql

@@ -1,16 +0,0 @@
--- You should not modify if this have pushed to Github, unless it does serious wrong with the db.
-BEGIN TRANSACTION;
-
-ALTER TABLE monitor
-	ADD mqtt_topic TEXT;
-
-ALTER TABLE monitor
-	ADD mqtt_success_message VARCHAR(255);
-
-ALTER TABLE monitor
-	ADD mqtt_username VARCHAR(255);
-
-ALTER TABLE monitor
-	ADD mqtt_password VARCHAR(255);
-
-COMMIT;

db/patch-api-key-table.sql

@@ -1,13 +0,0 @@
--- You should not modify if this have pushed to Github, unless it does serious wrong with the db.
-BEGIN TRANSACTION;
-CREATE TABLE [api_key] (
-    [id] INTEGER NOT NULL PRIMARY KEY AUTOINCREMENT,
-    [key] VARCHAR(255) NOT NULL,
-    [name] VARCHAR(255) NOT NULL,
-    [user_id] INTEGER NOT NULL,
-    [created_date] DATETIME DEFAULT (DATETIME('now')) NOT NULL,
-    [active] BOOLEAN DEFAULT 1 NOT NULL,
-    [expires] DATETIME DEFAULT NULL,
-    CONSTRAINT FK_user FOREIGN KEY ([user_id]) REFERENCES [user]([id]) ON DELETE CASCADE ON UPDATE CASCADE
-);
-COMMIT;

db/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/patch-group-table.sql

@@ -1,30 +0,0 @@
--- You should not modify if this have pushed to Github, unless it does serious wrong with the db.
-BEGIN TRANSACTION;
-
-create table `group`
-(
-    id           INTEGER      not null
-        constraint group_pk
-            primary key autoincrement,
-    name         VARCHAR(255) not null,
-    created_date DATETIME              default (DATETIME('now')) not null,
-    public       BOOLEAN               default 0 not null,
-    active       BOOLEAN               default 1 not null,
-    weight       BOOLEAN      NOT NULL DEFAULT 1000
-);
-
-CREATE TABLE [monitor_group]
-(
-    [id]         INTEGER PRIMARY KEY AUTOINCREMENT NOT NULL,
-    [monitor_id] INTEGER                           NOT NULL REFERENCES [monitor] ([id]) ON DELETE CASCADE ON UPDATE CASCADE,
-    [group_id]   INTEGER                           NOT NULL REFERENCES [group] ([id]) ON DELETE CASCADE ON UPDATE CASCADE,
-    weight BOOLEAN NOT NULL DEFAULT 1000
-);
-
-CREATE INDEX [fk]
-    ON [monitor_group] (
-                        [monitor_id],
-                        [group_id]);
-
-
-COMMIT;

db/patch-grpc-monitor.sql

@@ -1,25 +0,0 @@
--- You should not modify if this have pushed to Github, unless it does serious wrong with the db.
-BEGIN TRANSACTION;
-
-ALTER TABLE monitor
-    ADD grpc_url VARCHAR(255) default null;
-
-ALTER TABLE monitor
-    ADD grpc_protobuf TEXT default null;
-
-ALTER TABLE monitor
-    ADD grpc_body TEXT default null;
-
-ALTER TABLE monitor
-    ADD grpc_metadata TEXT default null;
-
-ALTER TABLE monitor
-    ADD grpc_method VARCHAR(255) default null;
-
-ALTER TABLE monitor
-    ADD grpc_service_name VARCHAR(255) default null;
-
-ALTER TABLE monitor
-    ADD grpc_enable_tls BOOLEAN default 0 not null;
-
-COMMIT;

db/patch-http-body-encoding.sql

@@ -1,12 +0,0 @@
--- You should not modify if this have pushed to Github, unless it does serious wrong with the db.
-BEGIN TRANSACTION;
-
-ALTER TABLE monitor ADD http_body_encoding VARCHAR(25);
-
-COMMIT;
-
-BEGIN TRANSACTION;
-
-UPDATE monitor SET http_body_encoding = 'json' WHERE (type = 'http' or type = 'keyword') AND http_body_encoding IS NULL;
-
-COMMIT;

db/patch-http-monitor-method-body-and-headers.sql

@@ -1,13 +0,0 @@
--- You should not modify if this have pushed to Github, unless it does serious wrong with the db.
-BEGIN TRANSACTION;
-
-ALTER TABLE monitor
-    ADD method TEXT default 'GET' not null;
-
-ALTER TABLE monitor
-    ADD body TEXT default null;
-
-ALTER TABLE monitor
-    ADD headers TEXT default null;
-
-COMMIT;

db/patch-improve-performance.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;
-
--- For sendHeartbeatList
-CREATE INDEX monitor_time_index ON heartbeat (monitor_id, time);
-
--- For sendImportantHeartbeatList
-CREATE INDEX monitor_important_time_index ON heartbeat (monitor_id, important,time);
-
-COMMIT;

db/patch-incident-table.sql

@@ -1,18 +0,0 @@
--- You should not modify if this have pushed to Github, unless it does serious wrong with the db.
-BEGIN TRANSACTION;
-
-create table incident
-(
-    id INTEGER not null
-        constraint incident_pk
-            primary key autoincrement,
-    title VARCHAR(255) not null,
-    content TEXT not null,
-    style VARCHAR(30) default 'warning' not null,
-    created_date DATETIME default (DATETIME('now')) not null,
-    last_updated_date DATETIME,
-    pin BOOLEAN default 1 not null,
-    active BOOLEAN default 1 not null
-);
-
-COMMIT;

db/patch-maintenance-cron.sql

@@ -1,11 +0,0 @@
--- You should not modify if this have pushed to Github, unless it does serious wrong with the db.
-BEGIN TRANSACTION;
-
-DROP TABLE maintenance_timeslot;
-
--- 999 characters. https://stackoverflow.com/questions/46134830/maximum-length-for-cron-job
-ALTER TABLE maintenance ADD cron TEXT;
-ALTER TABLE maintenance ADD timezone VARCHAR(255);
-ALTER TABLE maintenance ADD duration INTEGER;
-
-COMMIT;

db/patch-maintenance-table2.sql

@@ -1,83 +0,0 @@
--- You should not modify if this have pushed to Github, unless it does serious wrong with the db.
-BEGIN TRANSACTION;
-
--- Just for someone who tested maintenance before (patch-maintenance-table.sql)
-DROP TABLE IF EXISTS maintenance_status_page;
-DROP TABLE IF EXISTS monitor_maintenance;
-DROP TABLE IF EXISTS maintenance;
-DROP TABLE IF EXISTS maintenance_timeslot;
-
--- maintenance
-CREATE TABLE [maintenance] (
-    [id] INTEGER PRIMARY KEY AUTOINCREMENT NOT NULL,
-    [title] VARCHAR(150) NOT NULL,
-    [description] TEXT NOT NULL,
-    [user_id] INTEGER REFERENCES [user]([id]) ON DELETE SET NULL ON UPDATE CASCADE,
-    [active] BOOLEAN NOT NULL DEFAULT 1,
-    [strategy] VARCHAR(50) NOT NULL DEFAULT 'single',
-    [start_date] DATETIME,
-    [end_date] DATETIME,
-    [start_time] TIME,
-    [end_time] TIME,
-    [weekdays] VARCHAR2(250) DEFAULT '[]',
-    [days_of_month] TEXT DEFAULT '[]',
-    [interval_day] INTEGER
-);
-
-CREATE INDEX [manual_active] ON [maintenance] (
-    [strategy],
-    [active]
-);
-
-CREATE INDEX [active] ON [maintenance] ([active]);
-
-CREATE INDEX [maintenance_user_id] ON [maintenance] ([user_id]);
-
--- maintenance_status_page
-CREATE TABLE maintenance_status_page (
-    id INTEGER NOT NULL PRIMARY KEY AUTOINCREMENT,
-    status_page_id INTEGER NOT NULL,
-    maintenance_id INTEGER NOT NULL,
-    CONSTRAINT FK_maintenance FOREIGN KEY (maintenance_id) REFERENCES maintenance (id) ON DELETE CASCADE ON UPDATE CASCADE,
-    CONSTRAINT FK_status_page FOREIGN KEY (status_page_id) REFERENCES status_page (id) ON DELETE CASCADE ON UPDATE CASCADE
-);
-
-CREATE INDEX [status_page_id_index]
-    ON [maintenance_status_page]([status_page_id]);
-
-CREATE INDEX [maintenance_id_index]
-    ON [maintenance_status_page]([maintenance_id]);
-
--- maintenance_timeslot
-CREATE TABLE [maintenance_timeslot] (
-    [id] INTEGER PRIMARY KEY AUTOINCREMENT NOT NULL,
-    [maintenance_id] INTEGER NOT NULL CONSTRAINT [FK_maintenance] REFERENCES [maintenance]([id]) ON DELETE CASCADE ON UPDATE CASCADE,
-    [start_date] DATETIME NOT NULL,
-    [end_date] DATETIME,
-    [generated_next] BOOLEAN DEFAULT 0
-);
-
-CREATE INDEX [maintenance_id] ON [maintenance_timeslot] ([maintenance_id] DESC);
-
-CREATE INDEX [active_timeslot_index] ON [maintenance_timeslot] (
-    [maintenance_id] DESC,
-    [start_date] DESC,
-    [end_date] DESC
-);
-
-CREATE INDEX [generated_next_index] ON [maintenance_timeslot] ([generated_next]);
-
--- monitor_maintenance
-CREATE TABLE monitor_maintenance (
-    id INTEGER NOT NULL PRIMARY KEY AUTOINCREMENT,
-    monitor_id INTEGER NOT NULL,
-    maintenance_id INTEGER NOT NULL,
-    CONSTRAINT FK_maintenance FOREIGN KEY (maintenance_id) REFERENCES maintenance (id) ON DELETE CASCADE ON UPDATE CASCADE,
-    CONSTRAINT FK_monitor FOREIGN KEY (monitor_id) REFERENCES monitor (id) ON DELETE CASCADE ON UPDATE CASCADE
-);
-
-CREATE INDEX [maintenance_id_index2] ON [monitor_maintenance]([maintenance_id]);
-
-CREATE INDEX [monitor_id_index] ON [monitor_maintenance]([monitor_id]);
-
-COMMIT;

db/patch-monitor-add-resend-interval.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;
-
-ALTER TABLE monitor
-    ADD resend_interval INTEGER default 0 not null;
-
-ALTER TABLE heartbeat
-    ADD down_count INTEGER default 0 not null;
-
-COMMIT;

db/patch-monitor-basic-auth.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;
-
-ALTER TABLE monitor
-    ADD basic_auth_user TEXT default null;
-
-ALTER TABLE monitor
-    ADD basic_auth_pass TEXT default null;
-
-COMMIT;

db/patch-monitor-expiry-notification.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;
-
-ALTER TABLE monitor
-    ADD expiry_notification BOOLEAN default 1;
-
-COMMIT;

db/patch-monitor-oauth-cc.sql

@@ -1,19 +0,0 @@
--- You should not modify if this have pushed to Github, unless it does serious wrong with the db.
-BEGIN TRANSACTION;
-
-ALTER TABLE monitor
-    ADD oauth_client_id TEXT default null;
-
-ALTER TABLE monitor
-    ADD oauth_client_secret TEXT default null;
-
-ALTER TABLE monitor
-    ADD oauth_token_url TEXT default null;
-
-ALTER TABLE monitor
-    ADD oauth_scopes TEXT default null;
-
-ALTER TABLE monitor
-    ADD oauth_auth_method TEXT default null;
-
-COMMIT;

db/patch-monitor-push_token.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;
-
-ALTER TABLE monitor
-    ADD push_token VARCHAR(20) DEFAULT NULL;
-
-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;

db/patch-monitor-tls.sql

@@ -1,13 +0,0 @@
--- You should not modify if this have pushed to Github, unless it does serious wrong with the db.
-BEGIN TRANSACTION;
-
-ALTER TABLE monitor
-    ADD tls_ca TEXT default null;
-
-ALTER TABLE monitor
-    ADD tls_cert TEXT default null;
-
-ALTER TABLE monitor
-    ADD tls_key TEXT default null;
-
-COMMIT;

db/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/patch-notification_sent_history.sql

@@ -1,18 +0,0 @@
--- You should not modify if this have pushed to Github, unless it does serious wrong with the db.
-BEGIN TRANSACTION;
-
-CREATE TABLE [notification_sent_history] (
-    [id] INTEGER PRIMARY KEY AUTOINCREMENT NOT NULL,
-    [type] VARCHAR(50) NOT NULL,
-    [monitor_id] INTEGER NOT NULL,
-    [days] INTEGER NOT NULL,
-    UNIQUE([type], [monitor_id], [days])
-);
-
-CREATE INDEX [good_index] ON [notification_sent_history] (
-    [type],
-    [monitor_id],
-    [days]
-);
-
-COMMIT;

db/patch-ping-packet-size.sql

@@ -1,5 +0,0 @@
--- You should not modify if this have pushed to Github, unless it does serious wrong with the db.
-BEGIN TRANSACTION;
-ALTER TABLE monitor
-    ADD packet_size INTEGER DEFAULT 56 NOT NULL;
-COMMIT;

db/patch-proxy.sql

@@ -1,23 +0,0 @@
--- You should not modify if this have pushed to Github, unless it does serious wrong with the db.
-BEGIN TRANSACTION;
-
-CREATE TABLE proxy (
-    id INTEGER NOT NULL PRIMARY KEY AUTOINCREMENT,
-    user_id INT NOT NULL,
-    protocol VARCHAR(10) NOT NULL,
-    host VARCHAR(255) NOT NULL,
-    port SMALLINT NOT NULL,
-    auth BOOLEAN NOT NULL,
-    username VARCHAR(255) NULL,
-    password VARCHAR(255) NULL,
-    active BOOLEAN NOT NULL DEFAULT 1,
-    'default' BOOLEAN NOT NULL DEFAULT 0,
-    created_date DATETIME DEFAULT (DATETIME('now')) NOT NULL
-);
-
-ALTER TABLE monitor ADD COLUMN proxy_id INTEGER REFERENCES proxy(id);
-
-CREATE INDEX proxy_id ON monitor (proxy_id);
-CREATE INDEX proxy_user_id ON proxy (user_id);
-
-COMMIT;

db/patch-setting-value-type.sql

@@ -1,22 +0,0 @@
--- You should not modify if this have pushed to Github, unless it does serious wrong with the db.
-BEGIN TRANSACTION;
-
--- Generated by Intellij IDEA
-create table setting_dg_tmp
-(
-    id INTEGER
-        primary key autoincrement,
-    key VARCHAR(200) not null
-        unique,
-    value TEXT,
-    type VARCHAR(20)
-);
-
-insert into setting_dg_tmp(id, key, value, type) select id, key, value, type from setting;
-
-drop table setting;
-
-alter table setting_dg_tmp rename to setting;
-
-
-COMMIT;

db/patch-status-page-footer-css.sql

@@ -1,6 +0,0 @@
--- You should not modify if this have pushed to Github, unless it does serious wrong with the db.
-BEGIN TRANSACTION;
-ALTER TABLE status_page ADD footer_text TEXT;
-ALTER TABLE status_page ADD custom_css TEXT;
-ALTER TABLE status_page ADD show_powered_by BOOLEAN NOT NULL DEFAULT 1;
-COMMIT;

db/patch-status-page.sql

@@ -1,31 +0,0 @@
--- You should not modify if this have pushed to Github, unless it does serious wrong with the db.
-BEGIN TRANSACTION;
-
-CREATE TABLE [status_page](
-    [id] INTEGER PRIMARY KEY AUTOINCREMENT NOT NULL,
-    [slug] VARCHAR(255) NOT NULL UNIQUE,
-    [title] VARCHAR(255) NOT NULL,
-    [description] TEXT,
-    [icon] VARCHAR(255) NOT NULL,
-    [theme] VARCHAR(30) NOT NULL,
-    [published] BOOLEAN NOT NULL DEFAULT 1,
-    [search_engine_index] BOOLEAN NOT NULL DEFAULT 1,
-    [show_tags] BOOLEAN NOT NULL DEFAULT 0,
-    [password] VARCHAR,
-    [created_date] DATETIME NOT NULL DEFAULT CURRENT_TIMESTAMP,
-    [modified_date] DATETIME NOT NULL DEFAULT CURRENT_TIMESTAMP
-);
-
-CREATE UNIQUE INDEX [slug] ON [status_page]([slug]);
-
-
-CREATE TABLE [status_page_cname](
-    [id] INTEGER PRIMARY KEY AUTOINCREMENT NOT NULL,
-    [status_page_id] INTEGER NOT NULL REFERENCES [status_page]([id]) ON DELETE CASCADE ON UPDATE CASCADE,
-    [domain] VARCHAR NOT NULL UNIQUE
-);
-
-ALTER TABLE incident ADD status_page_id INTEGER;
-ALTER TABLE [group] ADD status_page_id INTEGER;
-
-COMMIT;

db/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/patch1.sql

@@ -1,37 +0,0 @@
--- You should not modify if this have pushed to Github, unless it does serious wrong with the db.
--- Change Monitor.created_date from "TIMESTAMP" to "DATETIME"
--- SQL Generated by Intellij Idea
-PRAGMA foreign_keys=off;
-
-BEGIN TRANSACTION;
-
-create table monitor_dg_tmp
-(
-    id INTEGER not null
-        primary key autoincrement,
-    name VARCHAR(150),
-    active BOOLEAN default 1 not null,
-    user_id INTEGER
-        references user
-                   on update cascade on delete set null,
-    interval INTEGER default 20 not null,
-    url TEXT,
-    type VARCHAR(20),
-    weight INTEGER default 2000,
-    hostname VARCHAR(255),
-    port INTEGER,
-    created_date DATETIME,
-    keyword VARCHAR(255)
-);
-
-insert into monitor_dg_tmp(id, name, active, user_id, interval, url, type, weight, hostname, port, created_date, keyword) select id, name, active, user_id, interval, url, type, weight, hostname, port, created_date, keyword from monitor;
-
-drop table monitor;
-
-alter table monitor_dg_tmp rename to monitor;
-
-create index user_id on monitor (user_id);
-
-COMMIT;
-
-PRAGMA foreign_keys=on;

db/patch10.sql

@@ -1,19 +0,0 @@
--- You should not modify if this have pushed to Github, unless it does serious wrong with the db.
-CREATE TABLE tag (
-	id INTEGER NOT NULL PRIMARY KEY AUTOINCREMENT,
-	name VARCHAR(255) NOT NULL,
-    color VARCHAR(255) NOT NULL,
-	created_date DATETIME DEFAULT (DATETIME('now')) NOT NULL
-);
-
-CREATE TABLE monitor_tag (
-	id INTEGER NOT NULL PRIMARY KEY AUTOINCREMENT,
-	monitor_id INTEGER NOT NULL,
-	tag_id INTEGER NOT NULL,
-	value TEXT,
-	CONSTRAINT FK_tag FOREIGN KEY (tag_id) REFERENCES tag(id) ON DELETE CASCADE ON UPDATE CASCADE,
-	CONSTRAINT FK_monitor FOREIGN KEY (monitor_id) REFERENCES monitor(id) ON DELETE CASCADE ON UPDATE CASCADE
-);
-
-CREATE INDEX monitor_tag_monitor_id_index ON monitor_tag (monitor_id);
-CREATE INDEX monitor_tag_tag_id_index ON monitor_tag (tag_id);

db/patch2.sql

@@ -1,9 +0,0 @@
-BEGIN TRANSACTION;
-
-CREATE TABLE monitor_tls_info (
-	id INTEGER NOT NULL PRIMARY KEY AUTOINCREMENT,
-	monitor_id INTEGER NOT NULL,
-	info_json TEXT
-);
-
-COMMIT;

db/patch3.sql

@@ -1,37 +0,0 @@
--- You should not modify if this have pushed to Github, unless it does serious wrong with the db.
--- Add maxretries column to monitor
-PRAGMA foreign_keys=off;
-
-BEGIN TRANSACTION;
-
-create table monitor_dg_tmp
-(
-    id INTEGER not null
-        primary key autoincrement,
-    name VARCHAR(150),
-    active BOOLEAN default 1 not null,
-    user_id INTEGER
-        references user
-                   on update cascade on delete set null,
-    interval INTEGER default 20 not null,
-    url TEXT,
-    type VARCHAR(20),
-    weight INTEGER default 2000,
-    hostname VARCHAR(255),
-    port INTEGER,
-    created_date DATETIME,
-    keyword VARCHAR(255),
-    maxretries INTEGER NOT NULL DEFAULT 0
-);
-
-insert into monitor_dg_tmp(id, name, active, user_id, interval, url, type, weight, hostname, port, created_date, keyword) select id, name, active, user_id, interval, url, type, weight, hostname, port, created_date, keyword from monitor;
-
-drop table monitor;
-
-alter table monitor_dg_tmp rename to monitor;
-
-create index user_id on monitor (user_id);
-
-COMMIT;
-
-PRAGMA foreign_keys=on;

db/patch4.sql

@@ -1,40 +0,0 @@
--- You should not modify if this have pushed to Github, unless it does serious wrong with the db.
--- OK.... serious wrong, missing maxretries column
--- Developers should patch it manually if you have missing the maxretries column
-PRAGMA foreign_keys=off;
-
-BEGIN TRANSACTION;
-
-create table monitor_dg_tmp
-(
-    id INTEGER not null
-        primary key autoincrement,
-    name VARCHAR(150),
-    active BOOLEAN default 1 not null,
-    user_id INTEGER
-        references user
-                   on update cascade on delete set null,
-    interval INTEGER default 20 not null,
-    url TEXT,
-    type VARCHAR(20),
-    weight INTEGER default 2000,
-    hostname VARCHAR(255),
-    port INTEGER,
-    created_date DATETIME,
-    keyword VARCHAR(255),
-    maxretries INTEGER NOT NULL DEFAULT 0,
-    ignore_tls BOOLEAN default 0 not null,
-    upside_down BOOLEAN default 0 not null
-);
-
-insert into monitor_dg_tmp(id, name, active, user_id, interval, url, type, weight, hostname, port, created_date, keyword, maxretries) select id, name, active, user_id, interval, url, type, weight, hostname, port, created_date, keyword, maxretries from monitor;
-
-drop table monitor;
-
-alter table monitor_dg_tmp rename to monitor;
-
-create index user_id on monitor (user_id);
-
-COMMIT;
-
-PRAGMA foreign_keys=on;

db/patch5.sql

@@ -1,70 +0,0 @@
--- You should not modify if this have pushed to Github, unless it does serious wrong with the db.
-PRAGMA foreign_keys = off;
-
-BEGIN TRANSACTION;
-
-create table monitor_dg_tmp (
-	id INTEGER not null primary key autoincrement,
-	name VARCHAR(150),
-	active BOOLEAN default 1 not null,
-	user_id INTEGER references user on update cascade on delete
-	set
-		null,
-		interval INTEGER default 20 not null,
-		url TEXT,
-		type VARCHAR(20),
-		weight INTEGER default 2000,
-		hostname VARCHAR(255),
-		port INTEGER,
-		created_date DATETIME default (DATETIME('now')) not null,
-		keyword VARCHAR(255),
-		maxretries INTEGER NOT NULL DEFAULT 0,
-		ignore_tls BOOLEAN default 0 not null,
-		upside_down BOOLEAN default 0 not null
-);
-
-insert into
-	monitor_dg_tmp(
-		id,
-		name,
-		active,
-		user_id,
-		interval,
-		url,
-		type,
-		weight,
-		hostname,
-		port,
-		keyword,
-		maxretries,
-		ignore_tls,
-		upside_down
-	)
-select
-	id,
-	name,
-	active,
-	user_id,
-	interval,
-	url,
-	type,
-	weight,
-	hostname,
-	port,
-	keyword,
-	maxretries,
-	ignore_tls,
-	upside_down
-from
-	monitor;
-
-drop table monitor;
-
-alter table
-	monitor_dg_tmp rename to monitor;
-
-create index user_id on monitor (user_id);
-
-COMMIT;
-
-PRAGMA foreign_keys = on;

db/patch6.sql

@@ -1,74 +0,0 @@
--- You should not modify if this have pushed to Github, unless it does serious wrong with the db.
-PRAGMA foreign_keys = off;
-
-BEGIN TRANSACTION;
-
-create table monitor_dg_tmp (
-	id INTEGER not null primary key autoincrement,
-	name VARCHAR(150),
-	active BOOLEAN default 1 not null,
-	user_id INTEGER references user on update cascade on delete
-	set
-		null,
-		interval INTEGER default 20 not null,
-		url TEXT,
-		type VARCHAR(20),
-		weight INTEGER default 2000,
-		hostname VARCHAR(255),
-		port INTEGER,
-		created_date DATETIME default (DATETIME('now')) not null,
-		keyword VARCHAR(255),
-		maxretries INTEGER NOT NULL DEFAULT 0,
-		ignore_tls BOOLEAN default 0 not null,
-		upside_down BOOLEAN default 0 not null,
-        maxredirects INTEGER default 10 not null,
-        accepted_statuscodes_json TEXT default '["200-299"]' not null
-);
-
-insert into
-	monitor_dg_tmp(
-		id,
-		name,
-		active,
-		user_id,
-		interval,
-		url,
-		type,
-		weight,
-		hostname,
-		port,
-        created_date,
-		keyword,
-		maxretries,
-		ignore_tls,
-		upside_down
-	)
-select
-	id,
-	name,
-	active,
-	user_id,
-	interval,
-	url,
-	type,
-	weight,
-	hostname,
-	port,
-    created_date,
-	keyword,
-	maxretries,
-	ignore_tls,
-	upside_down
-from
-	monitor;
-
-drop table monitor;
-
-alter table
-	monitor_dg_tmp rename to monitor;
-
-create index user_id on monitor (user_id);
-
-COMMIT;
-
-PRAGMA foreign_keys = on;

db/patch7.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;
-
-ALTER TABLE monitor
-	ADD dns_resolve_type VARCHAR(5);
-
-ALTER TABLE monitor
-	ADD dns_resolve_server VARCHAR(255);
-
-COMMIT;

db/patch8.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;
-
-ALTER TABLE monitor
-    ADD dns_last_result VARCHAR(255);
-
-COMMIT;

db/patch9.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;
-
-ALTER TABLE notification
-    ADD is_default BOOLEAN default 0 NOT NULL;
-
-COMMIT;

docker/alpine-base.dockerfile

@@ -1,8 +0,0 @@
-# DON'T UPDATE TO alpine3.13, 1.14, see #41.
-FROM node:16-alpine3.12
-WORKDIR /app
-
-# Install apprise, iputils for non-root ping, setpriv
-RUN apk add --no-cache iputils setpriv dumb-init python3 py3-cryptography py3-pip py3-six py3-yaml py3-click py3-markdown py3-requests py3-requests-oauthlib git && \
-    pip3 --no-cache-dir install apprise==1.4.0 && \
-    rm -rf /root/.cache

docker/builder-go.dockerfile

@@ -1,16 +0,0 @@
-############################################
-# Build in Golang
-# Run npm run build-healthcheck-armv7 in the host first, another it will be super slow where it is building the armv7 healthcheck
-############################################
-FROM golang:1.19-buster
-WORKDIR /app
-ARG TARGETPLATFORM
-COPY ./extra/ ./extra/
-
-# Compile healthcheck.go
-RUN apt update && \
-    apt --yes --no-install-recommends install curl && \
-    curl -sL https://deb.nodesource.com/setup_18.x | bash && \
-    apt --yes --no-install-recommends install nodejs && \
-    node ./extra/build-healthcheck.js $TARGETPLATFORM && \
-    apt --yes remove nodejs

docker/debian-base.dockerfile

@@ -1,48 +0,0 @@
-# DON'T UPDATE TO bullseye-slim, see #372.
-# There is no 20-buster-slim for armv7 unfortunately, 18-buster-slim is the last one for Uptime Kuma v1.
-FROM node:18-buster-slim
-ARG TARGETPLATFORM
-
-WORKDIR /app
-
-# Specify --no-install-recommends to skip unused dependencies, make the base much smaller!
-# python3* = apprise's dependencies
-# sqlite3 = for debugging
-# iputils-ping = for ping
-# util-linux = for setpriv (Should be dropped in 2.0.0?)
-# dumb-init = avoid zombie processes (#480)
-# curl = for debugging
-# ca-certificates = keep the cert up-to-date
-# sudo = for start service nscd with non-root user
-# nscd = for better DNS caching
-# (pip) apprise = for notifications
-RUN apt-get update && \
-    apt-get --yes --no-install-recommends install  \
-        python3 python3-pip python3-cryptography python3-six python3-yaml python3-click python3-markdown python3-requests python3-requests-oauthlib \
-        sqlite3  \
-        iputils-ping  \
-        util-linux  \
-        dumb-init  \
-        curl  \
-        ca-certificates \
-        sudo \
-        nscd && \
-    pip3 --no-cache-dir install apprise==1.6.0 && \
-    rm -rf /var/lib/apt/lists/* && \
-    apt --yes autoremove
-
-# Install cloudflared
-RUN set -eux && \
-    mkdir -p --mode=0755 /usr/share/keyrings && \
-    curl --fail --show-error --silent --location --insecure https://pkg.cloudflare.com/cloudflare-main.gpg --output /usr/share/keyrings/cloudflare-main.gpg && \
-    echo 'deb [signed-by=/usr/share/keyrings/cloudflare-main.gpg] https://pkg.cloudflare.com/cloudflared buster main' | tee /etc/apt/sources.list.d/cloudflared.list && \
-    apt-get update && \
-    apt-get install --yes --no-install-recommends cloudflared && \
-    cloudflared version && \
-    rm -rf /var/lib/apt/lists/* && \
-    apt --yes autoremove
-
-# For nscd
-COPY ./docker/etc/nscd.conf /etc/nscd.conf
-COPY ./docker/etc/sudoers /etc/sudoers
-