mirror of
https://github.com/louislam/uptime-kuma.git
synced 2026-03-02 22:57:00 -05:00
[Feature]: CLI for configuring and managing uptime kuma #509
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#509
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 @digitalbricklayer on GitHub (Nov 1, 2021).
🏷️ Feature Request Type
API, Other
🔖 Feature description
I am currently setting Uptime Kuma via an Ansible script. Whilst installing the software is easy enough even this node nube can do it, actually configuring Uptime Kuma is more problematic.
Add a command line program to do the following:
✔️ Solution
Write an API or command line program to implement the features suggested above.
❓ Alternatives
No response
📝 Additional Context
No response
⚠️ Please verify that this feature request has NOT been suggested before.
@arch1v1st commented on GitHub (Nov 1, 2021):
+1 for a REST API based approach here!
@gabrielefronze commented on GitHub (Nov 2, 2021):
+1 on my side as well!
@louislam commented on GitHub (Nov 2, 2021):
duplicate of #118