mirror of
https://github.com/louislam/uptime-kuma.git
synced 2026-03-02 22:57:00 -05:00
[Suggestion] Document ENV variables #204
Labels
No labels
A:accessibility
A:api
A:cert-expiry
A:core
A:dashboard
A:deployment
A:documentation
A:domain expiry
A:incidents
A:maintenance
A:metrics
A:monitor
A:notifications
A:reports
A:settings
A:status-page
A:ui/ux
A:user-management
Stale
ai-slop
blocked
blocked-upstream
bug
cannot-reproduce
dependencies
discussion
duplicate
feature-request
feature-request
good first issue
hacktoberfest
help
help wanted
house keeping
invalid
invalid-format
invalid-format
question
releaseblocker 🚨
security
spam
type:enhance-existing
type:new
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/uptime-kuma#204
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @gaby on GitHub (Sep 7, 2021).
Would it be possible to get all the ENV variables supported by uptime-kuma documented in the Wiki section?
Is it a duplicate question?
No
Info
Uptime Kuma Version: latest
Using Docker?: Yes
OS: Ubuntu 20.04 LTS
Browser: Firefox
@gaby commented on GitHub (Sep 15, 2021):
Doing a simple search on the repo, these are the variables that I could find.
@gaby commented on GitHub (Sep 19, 2021):
With #436 now merged, the following variables were added:
@erwineverts commented on GitHub (Mar 28, 2022):
Link to MR to improve the documentation wiki: https://github.com/louislam/uptime-kuma-wiki/pull/5
@gaby commented on GitHub (Mar 28, 2022):
@erwineverts i dont understand why the wiki is in a separate repo. Makes things super confusing. Also
NODE_TLS_REJECT_UNAUTHORIZEDis missing from the list.@erwineverts commented on GitHub (Mar 28, 2022):
I guess it's because wiki git repository can't be forked and thus by creating a separate repository, people can contribute.
Sorry, missed that one. My MR is already merged, so I won't add it now.
We could also argue to not include it because it's strongly discouraged to use it (https://nodejs.org/api/cli.html#node_tls_reject_unauthorizedvalue)
@gaby commented on GitHub (Mar 28, 2022):
@erwineverts Sounds good, closing this.