All source is organised under two repositories on GitHub: openfaas and openfaas-incubator.
OpenFaaS started as a single mono-repo called
faas and has been broken out into separate repositories in the openfaas organisation.
For this reason you should always collate statistics from the
openfaas organisation, rather than the repository of a single component, which would provide invalid data. So whether counting issues, PRs, contributors, stars, or any other metric, use the whole organisation.
|certifier||End-to-end tests written in Go for verifying OpenFaaS with Swarm or Kubernetes after a release, this also runs through CI for the
|docs||Official docs repository for this site - i.e. https://docs.openfaas.com|
|faas||Main repository for project issues, suggestions, documentation and roadmap/backlog items. Also includes UI portal and API gateway|
|faas-netes||Kubernetes provider for OpenFaaS contains YAML and helm for deployment|
|faas-swarm||Docker Swarm provider for OpenFaaS contains a stack file for deployment|
|faas-cli||CLI for operating with OpenFaaS similar to
|templates||Official templates for OpenFaaS CLI used to scaffold a new function|
|nats-queue-worker||Asynchronous processing for deferred / queued work with OpenFaaS, based upon NATS Streaming|
|media||Press-kit and media for the project branding and swag|
|openfaas.github.io||Source for https://www.openfaas.com and blog|
|openfaas-cloud||OpenFaaS Cloud - portable, multi-user Serverless Functions powered by GitOps|
|workshop||Practical training and hands-on labs for learning OpenFaaS|
The openfaas-incubator organisation contains projects which are under active development.
Some people have wrongly assumed that the "incubator" organisation means that these projects have a special status, or that they are unsuitable for production. Projects that are unsuitable for production usage will say so in their readme file as part of the project status.
|of-watchdog||The OpenFaaS watchdog re-written with mode-abstractions for both STDIO & HTTP|
|faas-idler||Scale OpenFaaS functions to zero replicas after specified period of inactivity|
|openfaas-operator||The OpenFaaS CRD Operator for Kubernetes|
|kafka-connector||The Kafka connector connects OpenFaaS functions to Kafka topics|
|ofc-bootstrap||"one-click" CLI to install OpenFaaS Cloud on Kubernetes|
|connector-sdk||Build your own event connectors for OpenFaaS|
|vcenter-connector||Trigger OpenFaaS Functions from events in VMware vCenter|
|faas-federation||Federate two OpenFaaS installations into one API|
|faas-memory||An OpenFaaS Provider example using memory for state.|
Training & tutorials¶
|workshop-vscode||Run a Kubernetes workshop with VSCode in the browser|
|openfaas-linkerd2||Lightweight Serverless on Kubernetes with mTLS and traffic-splitting with Linkerd2|
|openfaas-function-auth||Examples of authentication in OpenFaaS Serverless functions.|
|node10-express-template||Node.js 10 Express template providing additional context and control over the HTTP response from your function|
|node10-express-service||Template with Node.js and Express.js exposed fully|
|node8-express-template||Node.js 8 template for OpenFaaS with HTTP via Express.js|
|golang-http-template||Golang template providing additional control over the HTTP request and response.|
|powershell-http||PowerShell HTTP template|
|ruby-http||A Ruby HTTP template for OpenFaaS|
|python-flask-template||OpenFaaS templates for Python 2.7/3.6 with Flask|
|python3-debian||Template for Python3 on Debian for data-science / compiled pip modules|
|perl-template||Perl template for OpenFaaS|