alexellisuk

Thanks Ian, do you want to get in touch via email? alex@openfaas.com?

We have 28 people participating now, with live-previews, lots of Twitter activity and prizes to give away for folks who complete the various parts of the challenge.

The code is open source and includes a data logger and Grafana dashboard that's fun to use even if you are not growing things.

Thanks for mentioning K3sup [0]

I used Microk8s on a client project late last year and it was really painful, but I am sure it serves a particular set of users who are very much into the Snap/Canonical ecosystem.

In contrast, K3s is very light-weight and can be run in a container via the K3d project.

If folks want to work with K8s upstream or development patches against Kubernetes, they will probably find that KinD is much quicker and easier.

Minikube has also got a lot of love recently, and can run without having a dependency on Virtual Box too.

[0] https://k3sup.dev/ [1] https://kind.sigs.k8s.io/docs/user/quick-start/

Yes it's changed massively, but it's recent - only since 2019.

I am the creator of the k3sup (k3s installer) tool that was mentioned and have a fair amount of experience with K3s on Raspberry Pi too.

You might also like my video "Exploring K3s with K3sup" - https://www.youtube.com/watch?v=_1kEF-Jd9pw

https://k3sup.dev/

One of the earliest things the community did with inlets was to run a tunnel server on Heroku, but their free tier left a lot to be desired.

Fly's new PaaS gets you up to 3x tunnels hosted for free. It might be useful if you use inlets or some other server software that runs in containers.

You can also connect this to Kubernetes for Ingress.

A super cool project, but it's so easy to self-host a Raspberry Pi at home now with a public IP - even behind NAT and firewalls.

I'm the creator of inlets (self-hosted tunnels - L4/L7)

https://docs.inlets.dev/#/

But Argo Tunnels from Cloudflare, and reverse SSH (for those with too much time on their hands) also work.

For more on a teeny K3s cluster: https://blog.alexellis.io/state-of-netbooting-raspberry-pi-i...

I asked a couple of the members of the cert-manager team why they use inlets for local/private Kubernetes Ingress. The answer: it just works and was the easiest option.

I wrote up how it works and new options with helm for short-lived clusters.

I've just published my third eBook, and the first one on Go, but I've been writing blog posts on Go for years, several of which are top ranking on Google. That was part of the driving force putting the book together.

> It's a compilation of practical examples, lessons and techniques for Go developers. The topics cover the software lifecycle from learning the fundamentals, to software testing, to distribution and monitoring.

There's been 280 copies sold so far, and I'm open to feedback and improvements, having already incorporated changes received over email from readers.

If you're a Go expert, this might be one to recommend to a friend, but if you're starting out, or want to level up in unit-testing, Goroutines, or metrics/instrumentation, it may also be for you.

Why is this Show HN? The post is sample driven about a less understood way to work with openfaas.

The faas-cli generate command is really what is being shown off, that and the operator, which you can also checkout on GitHub

https://github.com/openfaas/faas-netes/

I'm not sure where you're getting your numbers from, there are 94 code samples, I've just checked. Are you getting confused with "example applications", as in what's in the zip file?

Here we are also talking about A4 pages, in an epub format it's 180 pages on a standard font size, but we digress. More is not more, less is more when it's useful and you can learn something and apply it.

I've reviewed several of the books you've mentioned, and have them on my desk. They are huge and unwieldy, with much of their content available in the Go docs or standard library.

This book is use-case driven, and some of those examples are for different skill levels. Certainly, editing is likely to be more thorough with a large publisher, but the feedback loop and the ability to iterate are an advantage here.

An example: the part of unit-testing in Go (originally a blog post) was referenced in the Kubernetes documentation as an example of how to learn to unit test.

Serverless For Everyone Else has sold ~ 450+ copies with a similar structure and very high ratings. It's not about page count.

250 USD is for 5 people :-) "Team edition = 5 people", so it is less than the base price.

To be fair, this is the first time I've tried 79USD, but when you talk about page numbers you are missing the point.

If the content and examples are useful to you, then it's worth much more than 79 Dollars and today's launch price is 50 USD, so far 82 people have bought at that price and a few on the Premium tier.

I posted a link to a blog post to the other posters, have a read of it where I mention price. See also DynamoDB book's pricing - https://www.dynamodbbook.com/

Agreed, but for SEO, unfortunately it must be written that way. I wrote up why here: https://blog.alexellis.io/i-wrote-a-book-about-golang/

There's a 7 day money-back guarantee and sample screenshots :)

> Offers and discounts: > Not entirely satisfied? Ask for your money back within 7 days of purchase, no questions asked.

So far 82 sales, and positive reviews on Twitter.

The base price is 50 USD today, 79USD normal price, find out more about that here:

https://blog.alexellis.io/i-wrote-a-book-about-golang/

The 250 USD tier is for 5 people, not for one. That's why it's called Team Edition. So it's a saving of 145 USD vs buying individual copies, or saving 395 USD vs 5 copies of the Premium edition.

This is excellent and reminds me of the style of The Richest Man in Babylon. Is it available in print format?

I didn't write this blog post, but helped Carlos with some editing. It was great chatting to him about how he planned it out and got it up and running in a short period of time.

If you're wanting to keep your infrastructure lean, you can use OpenFaaS on a single VM with "faasd" instead of K3s/K8s.

https://github.com/openfaas/faasd

I didn't write this blog post, but helped Carlos with some editing. It was great chatting to him about how he planned it out and got it up and running in a short period of time.

What bots and automation do you run, and where do you host yours?

Funnily enough for openfaas/faas - only the Google product showed dependencies. Both different tools also showed different "dependents"

If the exercise is to capture / mediate GPL2/3 dependencies, then having results missing kind of defeats the purpose.

Alex from the OpenFaaS open source project here. We recently had some help from the Istio team to update the compatibility and support for OpenFaaS + Istio. I went on to then write it up in as much detail as I could and show some of my own thoughts. Hope you enjoy, and feel free to ask me questions on Twitter - https://twitter.com/alexellisuk or CNCF/OpenFaaS Slack

Right, it's "just" a VM like Multipass which is another alternative we use in the faasd project for developing against containerd on Macs. You need a full Linux host.

https://blog.alexellis.io/containerd-development-multipass/

It's going to be pretty bad because it's using SSHFS - but your mileage may vary.

For Docker Desktop, hopefully Justin Cormack will stop by and answer.

The workflow for building an OpenFaaS function involves creating a container image, pushing it into a registry and then deploying it into a cluster. That cluster could be remote, or running on your own PC, but during development this push and pull phase can cause a significant lag for testing changes.

In this blog post we’ll explore how to test out kim, a new project written at Rancher Labs which can build a container image directly into a node’s image library. That means that we can shave off several seconds whenever we want to build a new function and deploy it compared to using faas-cli up with Docker or buildkit.

I also think it's important to cover prior art, so we do that where it belongs - in the introduction.

I'd be interested to know what you all are using to build images and accelerate your "inner loop". Are there any limitations or downsides?

> It is often said that Open Source Software is not sustainable, because it has no inherent business model, but I believe there are other pressures that leaders experience which when left unchecked may lead to "burn-out".

> I'll briefly describe what I believe leadership means before introducing each of the pressures and how they may be experienced. It's my opinion that the examples apply beyond Open Source Software and the technology industry. I will then sum up the pressures and make a case for sustainable leadership.

I had Matt Farina join me from Rancher to chat about the two new open source projects that came out of Rancher at KubeCon EU including Rancher Desktop and kim. Expect demos and some chatter on open source funding.

kim surprised me and I think it could potentially make building images for openfaas and K8s clusters a much, much faster workflow by bypassing a registry and going directly into containerd.

Disclaimer: This is not paid or promoted content, just two developers chatting. As you know - I developed https:/k3sup.dev/ so keep an eye on what's coming out of the community over there. Hope you enjoy it.

kim - https://github.com/rancher/kim

I'm sharing the new website and domain, let me know what you think? The barrier to entry is already quite low, but what would make it easier / more convincing to participate?

Hacker News tends to really get behind these kinds of indie founder types of posts, so I'm hoping to inspire a few folks to step out and have a go at self-publishing.

I also mention a couple of independent authors who inspired me in this write-up.

If you're thinking of doing it, maybe you should go ahead?

I did this in early 2019 to be able to work on OpenFaaS. Consulting is going well, monetising OSS, less well.

Craig Box has me on the Kubernetes Podcast to talk about the journey and career from FTE to having a company

https://kubernetespodcast.com/episode/116-independent-open-s...

With regards to your current revenue, it takes time to build up your client list and for you to understand what people are willing to pay for, that you can do. As you'll see in my journey, I quit to offer support to commercial users of OpenFaaS, many were happy supporting it themselves because we err on the side of simple / documented. Developer brand and experience is something almost every company with a product needs help with.

As a user of NATS and having it integrated into openfaas and faasd, I'm excited to see what the team have done with JetStream.

These particular highlights would be very welcome to our users:

* At-least-once delivery and exactly once within a window * Wildcard support * Cleanse specific messages (GDPR)

Let me know if I can help with anything - there's a parts list on the blog post. The easiest way to do it is just to tape a camera onto a piece of wood or the side of a plastic container. From there you can get more creative with wood and other tools, but you may need to do that part.

Hi folks, if you checkout the Twitter hashtag #growlab you can see what people are up where they are not quite able to send a PR in yet but are doing interesting stuff.

My time is limited for the project, but the best part for me is seeing others participate and come up with different things to grow and ways to capture and monitor the plants.

Lots of work went into this, impressed with how quickly Docker turned this around. I've been using it on my Apple M1 MBA since the initial preview - it just works (tm) - subject to you understanding how multi-arch works.

Even better, the Docker Hub has multi-arch images for most things you'll need whilst building applications.