archive/healthchecks_healthchecks
0
0
Fork 0
mirror of https://github.com/healthchecks/healthchecks.git synced 2025-04-08 06:30:05 +00:00
Code Issues Projects Releases Wiki Activity

Replace healtchecks with healthchecks ()

Browse source
This commit is contained in:
Tony F 2023-08-04 01:56:55 -05:00 • committed by GitHub
parent d164e12de3
commit 200a2d1dd7
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
3 changed files with 6 additions and 6 deletions

4
README.md
View file

@ -206,7 +206,7 @@ curl --url 'smtp://127.0.0.1:2525' \
## Sending Alerts and Reports
Healtchecks comes with a `sendalerts` management command, which continuously
Healthchecks comes with a `sendalerts` management command, which continuously
polls database for any checks changing state, and sends out notifications as
needed. Within an activated virtualenv, you can manually run
the `sendalerts` command like so:
@ -311,7 +311,7 @@ from the `django-sslserver` package.
Healthchecks supports external authentication by means of HTTP headers set by
reverse proxies or the WSGI server. This allows you to integrate it into your
existing authentication system (e.g., LDAP or OAuth) via an authenticating proxy.
When this option is enabled, **healtchecks will trust the header's value implicitly**,
When this option is enabled, **healthchecks will trust the header's value implicitly**,
so it is **very important** to ensure that attackers cannot set the value themselves
(and thus impersonate any user). How to do this varies by your chosen proxy,
but generally involves configuring it to strip out headers that normalize to the

4
templates/docs/self_hosted_configuration.html-fragment
View file

@ -397,7 +397,7 @@ setting to integrate Healthchecks with it.</p>
with any dashes replaced with underscores, and prefixed with <code>HTTP_</code>. For
example, if your authentication proxy sets a <code>X-Authenticated-User</code> request
header, you should set <code>REMOTE_USER_HEADER=HTTP_X_AUTHENTICATED_USER</code>.</p>
<p><strong>Important:</strong> When this option is enabled, <strong>Healtchecks will trust the header's
<p><strong>Important:</strong> When this option is enabled, <strong>Healthchecks will trust the header's
value implicitly</strong>, so it is <strong>very important</strong> to ensure that attackers cannot
set the value themselves (and thus impersonate any user). How to do this varies by
your chosen proxy, but generally involves configuring it to strip out headers that
@ -619,4 +619,4 @@ Enabled by default.</p>
<p>A boolean that turns on/off the Webhooks integration. Enabled by default.</p>
<h2 id="ZULIP_ENABLED"><code>ZULIP_ENABLED</code></h2>
<p>Default: <code>True</code></p>
<p>A boolean that turns on/off the Zulip integration. Enabled by default.</p>
<p>A boolean that turns on/off the Zulip integration. Enabled by default.</p>

4
templates/docs/self_hosted_configuration.md
View file

@ -571,7 +571,7 @@ When `REMOTE_USER_HEADER` is set, Healthchecks will:
example, if your authentication proxy sets a `X-Authenticated-User` request
header, you should set `REMOTE_USER_HEADER=HTTP_X_AUTHENTICATED_USER`.
**Important:** When this option is enabled, **Healtchecks will trust the header's
**Important:** When this option is enabled, **Healthchecks will trust the header's
value implicitly**, so it is **very important** to ensure that attackers cannot
set the value themselves (and thus impersonate any user). How to do this varies by
your chosen proxy, but generally involves configuring it to strip out headers that
@ -912,4 +912,4 @@ A boolean that turns on/off the Webhooks integration. Enabled by default.
Default: `True`
A boolean that turns on/off the Zulip integration. Enabled by default.
A boolean that turns on/off the Zulip integration. Enabled by default.