mirror of
https://github.com/louislam/uptime-kuma.git
synced 2026-03-02 22:57:00 -05:00
Systemd Unit #10
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#10
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 @12nick12 on GitHub (Jul 11, 2021).
Any chance someone might be able to get a systemd unit to work? I tried, but was failing. I ended up creating a basic bash script then calling that via systemd. Not the greatest, but works. I'd love to get that script out of the picture.
@louislam commented on GitHub (Jul 11, 2021):
PM2 did a great job for this, it is recommended.
More info: https://pm2.keymetrics.io/docs/usage/startup/
@TheGuyDanish commented on GitHub (Jul 12, 2021):
Tested by putting it into /etc/systemd/system/uptime-kama.service, running systemctl daemon-reload, systemctl enable uptime-kama.service and restarting. Works a charm.
@12nick12 commented on GitHub (Jul 12, 2021):
Thank you. My issue was the PATH wasn't configured correctly since I have my node in a different path