alexellisuk

I've been running one of these for a few months too and was excited when I saw an ARMv7 CPU. In the open source and container world, many projects have stopped supporting the Zero and RPi1 due to its lack of RAM and slow CPU speed. Even running "go build" can take multiple seconds on a simple program. Starting Node.js was also fairly slow.

The RPi zero shines for Python scripts that access hardware - for sensors and camera projects that are low power and cheap to make. It was actually perfect for the GrowLab project that we did over the summer with 20 others from the community https://growlab.dev - sensor data and camera images were aggregated to a more powerful RPi3/4 and then either uploaded to a static GitHub Pages site, fed into InfluxDB to create beautiful charts with Grafana.

The new Zero 2 means that I can start to run ARMv7 or even ARM64 containers on the zero again, but with the limit of 512GB of RAM. The launch blog post explains why this couldn't be made higher.

The first thing I tried out was not K3s, which I knew already suffers on a Raspberry Pi 3, but faasd. Faasd is OpenFaaS but built for pure containerd, no multi-node networking and no Kubernetes. It works fairly well for a few functions, even with NATS and Prometheus being deployed as part of the stack.

So whilst you're not going to be building K3s clusters with these, they can run containers - with Docker, containerd, nerdctl and even as a full application stack with faasd.

Where this gets more interesting for me, is hosting small applications, integrations or APIs. Perhaps with Ingress via a tunnel that can penetrate NAT/firewalls like Inlets, Argo or Ngrok.

I've ordered one of the release models to see how it performs. Look out for a blog post from me soon.

This feature in GitHub was made official at GitHub Universe yesterday. https://github.blog/2021-10-27-everything-new-from-universe-...

So who knows what all that WASM is for in the Neovim plugin? Is there source for it? https://github.com/github/copilot.vim/tree/release/copilot/d...

This is one of the biggest releases for inlets so far, which adds monitoring and metrics support with a new status command and Prometheus instrumentation: for a more detailed write-up with more info on the metrics see: https://inlets.dev/blog/2021/08/18/measure-and-monitor.html

How does inlets compare to other tunnels? https://inlets.dev/blog/2021/07/27/monthly-subscription.html

This release adds to the apps (helm charts, CLI installers) for Kubernetes clusters, plus DevOps / Infra CLIs using "arkade get"

New `arkade get` superpowers:

``` arkade get faas-cli

arkade get kubectl@v1.22.0

arkade get kubectl@v1.22.0 \ faas-cli \ inlets-pro@0.9.0 \ helm ```

New CockroachDB app:

``` arkade install cockroachdb ```

New Kasten sponsored app functionality for preflight checks

``` arkade kasten k10 preflight arkade kasten k10 preflight --dry-run ```

> Kevin Lindsay is a Full Stack Web Developer at Surge and an OpenFaaS community member. Whilst building OpenFaaS functions, he wanted to customise his local workflow and decided on Tilt. Learn how Kevin uses Tilt with his functions to get live updates and smart rebuilds of his code.

This is one of the biggest releases for inlets so far, which adds monitoring and metrics support with a new status command and Prometheus instrumentation: for a more detailed write-up with more info on the metrics see: https://inlets.dev/blog/2021/08/18/measure-and-monitor.html

I'm in two minds whether this goes into HN or Show HN as it's involved writing a lot of code and exploring an undocumented system. I wouldn't exactly call it reverse engineering as I don't want to attract that kind of attention. I also created a new OpenFaaS auth plugin as part of this, so it feels like "Show".

The magic is: federating / trusting GitHub Actions for deploying to various clouds or REST APIs. Hope you enjoy this and it may help you to build an integration for your own project or product.

You may also enjoy the links to AWS / GCP for your daily work.

I'm in two minds whether this goes into HN or Show HN as it's involved writing a lot of code and exploring an undocumented system. I wouldn't exactly call it reverse engineering as I don't want to attract that kind of attention.

The magic is: federating / trusting GitHub Actions for deploying to various clouds or REST APIs. Hope you enjoy this and it may help you to build an integration for your own project or product.

I wrote up how we migrated Derek away from Docker Swarm and onto a new bare-metal host on Equinix Metal using Terraform and the new faasd project.

You may benefit from trying out Derek for delegating permissions to your community on open source projects, or for helping with governance and the quality of PRs submitted.

There's also a Hacktoberfest filtering function to help with spam, and a release notes generation tool that works on any project or repo.

Also slow here. I can't see anything on the AWS Service Dashboard https://status.aws.amazon.com

I'm seeing "Don't know" for fuel status for everything in the city where I live. I guess this is really relying on crowd-sourcing the data?

Disclosure: I reviewed this blog post and provided technical support whilst Nathan built this out. Other than that it's an end-user write-up. Happy to answer questions folks may have here or on Twitter @alexellisuk.

This sample repo has examples for OpenFaaS and Cassandra (open source or managed on Astra DB/Aiven) and then specific examples for Astra DB's Document SDK (similar interface to Mongo)

Astra's add-ons for Cassandra are open-source via https://stargate.io/

I was chatting to community member about a live stream we have planned on OpenFaaS later today and both of us may have to tether due to ISP issues. I wrote this up to help him quickly install OpenFaaS to a cloud provider, so that he can save on bandwidth and have a reliable installation with a public IP.

Disclosure: Linode also sponsored our homepage for 6 months. They did not pay for, request or commission this post.

Hope you find this useful.

Disclosure: This is a blog post from an inlets user, but I am the author of inlets and have an interest in folks knowing more about its use cases.

In this new release of inlets, you can now get insights into your tunnel servers through the status command and new Prometheus monitoring.

The inlets 0.9.0 releases adds:

* A new status CLI command to monitor tunnels

* Load-balancing of requests between clients using TCP tunnels

* An ARM64 Darwin binary for Apple M1 users

* Prometheus metrics for TCP and HTTP tunnels

Thanks to the community, customer and to contributors for their support.

> In this new release of inlets, you can now get insights into your tunnel servers through the status command and new Prometheus monitoring. I’ll walk you through why inlets was built as a Cloud Native tunnel, followed by the various changes and features introduced in this release.

The main changes are both the status endpoint and command and the Prometheus metrics which were added for reliability / observability.

> The launch of the Raspberry Pi Compute Module 4 family (reviewed in Issue 209) last year sparked an entirely unsurprising explosion of interest in designing carrier boards. This was aided in no small part by the Raspberry Pi Foundation’s decision to release its own in-house carrier board design under a permissive licence from which others could springboard with their own creations.

> Smartly designed with some clever features, the Tofu is a great carrier for a Raspberry Pi CM4 or compatible boards

I was asked by a user on Twitter to provide a tutorial for users of other SaaS tunnel services like Ngrok, that would get them started quickly with a HTTPS tunnel.

inlets does other things like TCP tunnels and Kubernetes integration, but this should get folks up and running.

So far the monthly subscription has been popular - combining a SaaS billing concept with a self-hosted piece of software.

Have you checked out some of the other options for remote access to your Raspberry Pi, like Tailscale (no affiliation) and inlets https://johansiebens.dev/posts/2020/11/quake-iii-arena-k3s-a...?

> In this post I’ll show you how to invoke your functions using Aiven’s managed Kafka service and the OpenFaaS PRO connector. A sample function and setup are included, so you can follow along with a free trial, or your existing Aiven account.

The Kafka integration is part of the strategy to sustain openfaas in the long run, since most commercial users refuse to sponsor the project or support it in any other way, this offers them something of value that they can pay for, along with a few other features useful for companies:

http://docs.openfaas.com/openfaas-pro/introduction/

https://github.com/openfaas/faas/blob/master/ADOPTERS.md

faasd is openfaas but instead of running on Kubernetes in a cluster, it runs as an appliance on a VM and can run stateful services in a docker-compose file along with functions.

This release brought containerd v1.5.4, Alpine Linux 3.14 and NATS Streaming 0.22.0 into the stack to fix high and medium vulnerabilities in the earlier versions of those components.

Do upgrade as soon as you can.

This is something that's been requested by the community and trial users, it's now here thanks to Gumroad's licensing integration.

I also took some time to explain why I built inlets and what it sets out to do differently from SaaS tunnels like Ngrok.

If you've not had a chance to play with it yet, it's now fully up to date with containerd's latest release.

A very low-hassle and speedy way to run self-hosted faas.

You asked for a monthly subscription for inlets PRO, so here it is. I also took time time to explain what problems inlets PRO solves that managed tunnels like Ngrok does not.

SaaS tunnels are immensely convenient and cheap. But I specifically, I want to show what pain is still unresolved like Kubernetes integration and rate-limiting.

It's a very common phrase in the UK: "Grow your own" means food. But I can get that updated for our international speakers.

Thanks for commenting.

https://github.com/alexellis/growlab.dev/commit/a349972b977b...

Fancy trying out one of the experiments we have listed? Like the data logger or live preview?

Sure, you can use a Raspberry Pi Zero. That's part of the build instructions in the repo

We have _no kit_ for sale, so it's clearly any kit :-)

We do have open source code available for you to use for free, and three varied experiments you can take part in. Feel free to browse the code and README