Our great sponsors
-
piku
The tiniest PaaS you've ever seen. Piku allows you to do git push deployments to your own servers.
-
-
SurveyJS
Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App. With SurveyJS form UI libraries, you can build and style forms in a fully-integrated drag & drop form builder, render them in your JS app, and store form submission data in any backend, inc. PHP, ASP.NET Core, and Node.js.
-
-
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
Sorry OT, but TIL about piku [0]
I have a old laptop in need of a new purpose. Might have a play with that.
[0] https://github.com/piku/piku
Thanks! Piku has been my go-to for dev environments, Linux IoT and general-purpose stuff for a long while now, as it is simpler to iterate (no container build cycles, no need for a registry, relies on rock solid nginx/uwsgi, etc.).
I usually start with that and then containerize as needed, but this time it was actually the other way around -- since I didn't know what Node-RED modules I'd need and didn't see much point in going beyond a single core, I just sidestepped my custom Node-RED containers* and pushed out a Node-RED deployment to a underused, single-core piku instance.
(FWIW, I have a running k3s setup with the Azure equivalent of spot instances, but Node-RED can't take advantage of that setup and I mostly wanted the GUI and higher-level abstractions. You'd be surprised how much mileage you can get from something like this...)
* - https://github.com/insightfulsystems/node-red
node-red is another thing I think of when I think about modern yahoo pipes
https://nodered.org/
The runtime controller is uwsgi, which acts as supervisor for all processes of an app _or_ embeds the right interpreter-it's pretty much perfect for that, as it also has a cron scheduler and an on-demand, fire-up-an-interpreter-upon-request mode.
As to the k3s stuff, it's all here: https://github.com/rcarmo/azure-k3s-cluster. I update this from time to time as I occasionally nuke the entire cluster and rebuild it (I use AKS for non-hobby workloads, but a single master is just fine for most of my stuff).
Great writeup, especially with all the workflow canvas screenshots. Makes me want to try out Node-RED.
From a few weeks ago on HN:
https://github.com/pipes-digital/pipes
“pipes.digital is a spiritual successor to Yahoo Pipes, a graphical interface to get data from the web and to manipulate it by connecting block”
These look like great tools.
I think calling these low-code / no-code frameworks is however quite misleading though, because there is actually code, it’s just inside the component! Code still has to be written.
One thing that these low-code / no-code frameworks do well is provide a structure that you can easily show visually.
This is particularity useful when you have to work with clients that aren’t that technical. It makes creating specifications much easier, which can be reviewed and revised before embarking on a big development effort.