mirror of
https://github.com/healthchecks/healthchecks.git
synced 2026-04-25 06:55:53 +03:00
[GH-ISSUE #467] Move self-hosting instructions from README to online docs #350
Labels
No labels
bug
bug
bug
feature
good-first-issue
new integration
pull-request
question
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/healthchecks#350
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 @Romanmir on GitHub (Jan 11, 2021).
Original GitHub issue: https://github.com/healthchecks/healthchecks/issues/467
I'm not seeing where to configure options for Pushover notifications.
I already have a notification set up that pings me on backup failure, but I'd like to set up a new notification for a separate project that notifies me in an emergency fashion when an important process is missed.
Can you expand on the notes that you have in the "Configuring Notifications" page?
Here are the questions that should be expanded; "Where do I configure the push settings for pushover?", "Are the settings for pushover per project?", "Can multiple settings 'profiles' be used within a specific project?"
Thanks for making this software, I use it consistently.
@cuu508 commented on GitHub (Jan 11, 2021):
Thanks for the feedback!
You can set the push settings (priority) when adding the Pushover integration. Once the integration is added, there is currently no option to go back in and edit the integration settings.
You can assign checks to integrations (tell which checks should use which integrations) at any time from 3 places:
They are per-integration (integration = "settings profile"). Each integration belongs to a specific project. If you have multiple projects, and want to use Pushover in each, you must add a Pushover integration to each project.
Yes, you can add multiple integrations (settings profiles) of the same type to a single project. For example, you can have three Pushover integrations for low, medium and high priority within a single project. Or you can have multiple Pushover notifications that notify different people.
--
Some of the above is already in the docs, some isn't. I'll review the docs and see what can be improved.
@Romanmir commented on GitHub (Jan 11, 2021):
Ok, but how do I change the settings when setting up the integration?
Maybe I'm missing something. On my integrations list, I do not see Pushover. I've been using the Site Administration interface to do this. I'm using the linuxserver/healthchecks docker image. What am I missing?
@cuu508 commented on GitHub (Jan 11, 2021):
Ah, sorry, I didn't realize you don't see the integration in the list at all!
README has instructions for setting up the Pushover integration: https://github.com/healthchecks/healthchecks#pushover
@Romanmir commented on GitHub (Jan 12, 2021):
Ok, I think I'm on the right track now. I think my feedback would change to be: I feel like the contents of the README.md file should be fully integrated into the online docs.
@cuu508 commented on GitHub (Jan 18, 2021):
The primary audience of the online docs is the end users of the service. I think publishing README as part of the online docs would just cause confusion.
Perhaps there could be a page titled "Self-hosting" in the docs, giving a quick idea of what's involved in self-hosting, when it makes sense to do it, and where to get the code.
@cuu508 commented on GitHub (Jan 19, 2021):
Gave it some more thought, perhaps moving some of the README content to online docs does make sense after all. The README is getting rather long, and would need to be split into sub-documents at some point anyway. Online docs would probably be more discoverable than a /docs/ folder in the repository or wiki pages.
I'll update the title of this issue.
@Romanmir commented on GitHub (Jan 19, 2021):
Thank you for reconsidering.