Replied in thread
@Dokza #activepieces is your way to go
#activepieces
0 posts0 participants0 posts today
Replied in thread
@linuxelf @technotim I did the switch from #Gitea to #Forgejo. There are some similarities in your stack but also ideas for me to explore. #Jellyfin has gotten great. If I’d put one more in front of you both to deep dive on… #ActivePieces is my favorite recent addition.
Replied in thread
@magnus919 Ummm I use both (#N8N it’s running since …¿2021?) It’s more versatile than #ActivePieces or maybe it just fits better to my needs
Continued thread
Aaaand I can process #Mastodon activity in here, too. Snap. #ActivePieces #selfHosting
Continued thread
Ermahgerd! Now I'm putting #UptimeKuma and #ActivePieces together. Or really all of my #selfhosting services. So many of them can send webhooks. And I'm processing them in ActivePieces to do things.
Like I can queue up all of the payloads over the day, spit them to an AI API, and get back an HTML formatted daily summary that gets emailed to me.
I'm staying up late working on #ActivePieces and re-deploying #UptimeKuma (better this time around).
Here are my notes on deploying Uptime Kuma. #selfhosting #homelab #docker
Notes from the Rabbit Hole · Deploying Uptime Kuma with DockerA guide for self-hosters to deploy Uptime Kuma using Docker and Docker Compose.
Here's my notes on #selfhosting #ActivePieces on #docker with #DockerCompose. I'll update this as I go.
Notes from the Rabbit Hole · Deploying ActivePieces with Docker ComposeGuide to deploying ActivePieces with Docker Compose, including customizations and future improvements.
Replied in thread
@magnus919 just use #activepieces instead of n8n ¯\_(ツ)_/¯
Replied in thread
@anders I tried but I don’t like it.
I cannot explain it, but I prefer #activepieces
Fudge Sunday