Selfhosted
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil.
-
No spam.
-
Posts are to be related to self-hosting.
-
Don't duplicate the full text of your blog or readme if you're providing a link.
-
Submission headline should match the article title.
-
No trolling.
-
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.
-
AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
view the rest of the comments
Since there's no native ntfy notification built in to LubeLogger I figured out a way to do it using Node-RED. If you don't have Node-RED set up, It's pretty great for automating things. I mostly use it for Home Assistant. There's certainly a way to accomplish this without Node-RED, but I would have no clue where to start.
The basic idea of the flow attached below is:
You'll of course have to go through and change settings in each node to match your LubeLogger URL and vehicle ID's, and preferred ntfy server and topic. You can also add your username/password for LubeLogger and ntfy (or a bearer token, if that's what you have set up with ntfy).
Node-RED flow
If you're not familiar with Node-RED, you'd import the above JSON and edit it from there. Stuff "flows" through nodes, stopping and doing what you tell it along the way.