The container native, cloud agnostic serverless platform.
Fn is an event-driven, open source, Functions-as-a-Service (FaaS) compute platform that you can run anywhere. Some of its key features:
docker login(Not required for local development)
The command line tool isn't required, but it makes things a lot easier. There are a few options to install it:
If you're on a Mac and use Homebrew:
brew update && brew install fn
This one works on Linux and macOS (partially on Windows).
If you are running behind a proxy first set your httpproxy and httpsproxy environment vars:
curl -LSs https://raw.githubusercontent.com/fnproject/cli/master/install | sh
This will download a shell script and execute it. If the script asks for a password, that is because it invokes sudo.
Head over to our releases and download it.
First, start up an Fn server locally:
This will start Fn in single server mode, using an embedded database and message queue. You can find all the configuration options here. If you are on Windows, check here. If you are on a Linux system where the SELinux security policy is set to "Enforcing", such as Oracle Linux 7, check here.
Functions are small but powerful blocks of code that generally do one simple thing. Forget about monoliths when using functions, just focus on the task that you want the function to perform. Our CLI tool will help you get started quickly.
Let's create your function. You can use any runtime (ie go, node, java, python, etc.)
hellowill be the name of your function as well as create a directory called
hello. You can name your function anything.
fn init --runtime go hello cd hello
We need to create an "app" which acts as a top-level collection of functions and other elements:
fn create app myapp
Deploy your function:
fn deploy --app myapp --local
--localflag will skip the push to remote container registry making local development faster
Now let's actually run your function using the
fn invoke myapp hello
That's it! You just deployed and ran your first function! Try updating the function code in
func.go(or .js, .java, etc.) then deploy it again to see the change.