Live data from Hacker News

Fair-Code Automation with n8n.io

tech.davidfield.co.uk

31–40 of 43 posts

Re: Fair-Code Automation with n8n.io

#31
Huginn [0] is also very powerful, free, and open source. You can run it locally, in a VPS, or on Heroku for free.

I pay for IFTTT Pro, but I still use Huginn for things that IFTTT can't do, and I highly recommend it.

I've tried Node-Red and while it can definitely do the job, I couldn't get along with it.

0. https://github.com/huginn/huginn

Re: Fair-Code Automation with n8n.io

#33

Earlier quoted context omitted.

Four instances? What kind of tasks are you using them for?

Want a breakdown, ok. My server, my raspberry pi in my house, my desktop and my phone all run an instance, with my server hosting a Mosca MQTT which they all use to send messages between. My server runs anything web-facing, so the web-hooks and random API projects. The PI does things like Wake-on-lan the Desktop, working with Alexa ( https://flows.nodered.org/node/node-red-contrib-alexa-home ) and acting as a pi-hole…

> and my phone

you are running it with termux?

Re: Fair-Code Automation with n8n.io

#34

When talking about an open-source IFTTT please always consider Node-Red. I host four instances of it around my life and it's my go-to solution for almost everything. https://nodered.org/

Four instances? What kind of tasks are you using them for?

I have 10 setups running now I think, may have missed some too.

1- Homeassistant on ODroidC4 2- Raspberry Pi controlling my chicken coop in barn 3- Docker 1, not sure what it does anymore 4- Docker 2, used to run chicken coop, has a bunch of legacy stuff I don't want to move, like my discord firewall connection to block/allow kids Internet and kids pi-hole 5- Docker 3, fresh setup to standardize my data collection via MQTT to influxDB and Ignition Maker Edition 6- Raspberrypi at cousins restaurant, monitors temps, send alerts to discord and POS printers, runs the door dingers out speakers, different per door and volume changes by time of day/day of week 7- Docker on resturant camera server, don't think it does anything really 8- RaspberryPi at resturant in the shed, watches the freezer temp and building temp, was going to watch power and the door also, never got around to it 9- Raspberrypi at Buddies shop, watches his boiler temps 10- Docker at buddies house, collects the shop boiler data and pushes to influxdb for Grafana, I think, I may have bypassed that part of it

Re: Fair-Code Automation with n8n.io

#35

Earlier quoted context omitted.

Four instances? What kind of tasks are you using them for?

I have 10 setups running now I think, may have missed some too. 1- Homeassistant on ODroidC4 2- Raspberry Pi controlling my chicken coop in barn 3- Docker 1, not sure what it does anymore 4- Docker 2, used to run chicken coop, has a bunch of legacy stuff I don't want to move, like my discord firewall connection to block/allow kids Internet and kids pi-hole 5- Docker 3, fresh setup to standardize my data collection vi…

Sorry, I apparently can't format very well on n my phone

Re: Fair-Code Automation with n8n.io

#36
post #14

Thanks a lot for creating this tutorial! I am the creator & CEO of n8n. If anybody has any questions simply ask. Happy to answer!

Hi, I really don’t want to sound lazy but might as well ask the creator: where does n8n cloud fit compared to Pipedream or Autocode? I use pipedream a lot but curious if n8n is an alternative or solves something else.

Re: Fair-Code Automation with n8n.io

#37
post #8
post #2

N8n.io is not open source. It even says so on the landing page. Edit: the article has since been updated

"Apache 2.0 with Commons Clause" They are free to choose whatever license works for them but this reference to Apache 2.0 is problematic.

Why is it problematic to reference Apache 2.0?

I am curios as I read some resources about various OSS licenses and after I was thinking that Apache 2.0 license is a good one.

Re: Fair-Code Automation with n8n.io

#38
post #37
post #8

Earlier quoted context omitted.

"Apache 2.0 with Commons Clause" They are free to choose whatever license works for them but this reference to Apache 2.0 is problematic.

Why is it problematic to reference Apache 2.0? I am curios as I read some resources about various OSS licenses and after I was thinking that Apache 2.0 license is a good one.

It's not problematic to reference Apache 2.0, it's a fine license. I assume what berkay is talking about is this wording of " with Commons Clause" - e.g. the Apache foundation has explicitly requested that this not be done (which the creators of the Commons Clause conveniently ignore), because it changes what the license means a lot and sounds like it's an official variant of the license. Apache only wants if any "Apache 2.0 with addons" licenses if they give more rights to the recipient, not less.

Re: Fair-Code Automation with n8n.io

#39
post #36
post #14

Thanks a lot for creating this tutorial! I am the creator & CEO of n8n. If anybody has any questions simply ask. Happy to answer!

Hi, I really don’t want to sound lazy but might as well ask the creator: where does n8n cloud fit compared to Pipedream or Autocode? I use pipedream a lot but curious if n8n is an alternative or solves something else.

Some of the advantages of n8n.cloud compared to Pipedream/Autocode are (disclaimer do not know any of them too well): - Easy to use but powerful even without coding skills (but even more possibilities if you can code) - Build complex workflows easily and fast via a node-based editor - Split data into different branches and merge them again - No lock-in (you can take your workflows anytime and run n8n yourself where ever you want) - Peace of mind that if the company (n8n) would ever go out of business you would not lose all your work as you would still be able to run it yourself - Amazing community that helps each other and improves n8n on a daily basis

Re: Fair-Code Automation with n8n.io

#40
post #38
post #37

Earlier quoted context omitted.

Why is it problematic to reference Apache 2.0? I am curios as I read some resources about various OSS licenses and after I was thinking that Apache 2.0 license is a good one.

It's not problematic to reference Apache 2.0, it's a fine license. I assume what berkay is talking about is this wording of " with Commons Clause" - e.g. the Apache foundation has explicitly requested that this not be done (which the creators of the Commons Clause conveniently ignore), because it changes what the license means a lot and sounds like it's an official variant of the license. Apache only wants if any "Ap…

ah got it. thanks for the clarity.

I remember that I read some things about mixing Apache 2.0 with other restrictions (like Commons Clause in this context) and a lot of debates about the wording of such mix.

Post reply on HN