📟 Personal DiscordOps to keep deployed things in check
This repository has been archived on 2024-07-19. You can view files and clone it, but cannot push or open issues or pull requests.
Find a file
Marc Cataford 717de087a5
Some checks failed
CI/CD / Static Analysis (push) Failing after 1m14s
CI/CD / Deploy (push) Has been skipped
ci: migrate to forgejo actions
fix: use self-hosted runner
2024-03-31 13:41:48 -04:00
.forgejo/workflows ci: migrate to forgejo actions 2024-03-31 13:41:48 -04:00
src chore(tools): add biomejs, apply lint+formatting fixes 2024-03-14 01:16:53 -04:00
.gitignore feat: scheduled healthchecks with reporting via Discord webhook 2024-03-14 00:41:01 -04:00
.yarnrc.yml feat: scheduled healthchecks with reporting via Discord webhook 2024-03-14 00:41:01 -04:00
biome.json chore(tools): add biomejs, apply lint+formatting fixes 2024-03-14 01:16:53 -04:00
netlify.toml feat: scheduled healthchecks with reporting via Discord webhook 2024-03-14 00:41:01 -04:00
package.json chore(tools): add biomejs, apply lint+formatting fixes 2024-03-14 01:16:53 -04:00
README.md feat: scheduled healthchecks with reporting via Discord webhook 2024-03-14 00:41:01 -04:00
yarn.lock chore(tools): add biomejs, apply lint+formatting fixes 2024-03-14 01:16:53 -04:00

healthcheck

Personal DiscordOps to keep things I deploy in check

Configuration

A configuration file should be manually pushed and made accessible to the functions. This can be done via netlify blobs:set test config -i ./config.json provided that config.json has content that matches the configuration schema:

{
  "endpoints": [
    { "name": <service-name>, "url": <endpoint-url> },
    ...
  ],
  "webhook_url": <webhook-url>
}

The webhook-url is expected to contain $DISCORD_WEBHOOK_ID and $DISCORD_WEBHOOK_TOKEN placeholders.