Reed Allman 63796a7c48 change hot containers when route/app vars change
this changes the behavior of hot containers:

1) we are no longer populating a hot container with all of the env vars from the
first request to start up that hot container. this will only populate the
container with any vars that are defined on the app or route.
2) when env vars are changed on the route or app, we will now start up a new
hot container that contains those changes.
3) fixes a bug where we could have a collision if the image and path name
created one, e.g. `/yo/foo` & `oze/yo:latest` collides with `/yo/fo` and
`ooze/yo:latest` (if all other fields are held constant), since we're
name spacing with app name in theory it would happen to the same user (though
we were relying on a comma delimiter there, not great). now we use NULL bytes
which should be hard to get in through a json api ;) i added a sha1 to keep
the size of the (soon to be very large) map down, i don't expect collisions
but, well, it's a hash function.

a small note that we could add a few things to the hot container that will not
change on a request basis, such as `app_name`, `format` and `route` but it's a
bit pedantic. ultimately, it's confusing imo that we have a different set of
vars in the env and in the request itself for hot, which is unavoidable unless
we choose to omit setting env vars entirely, but it seems to be what the
people want (lmk, people, if otherwise).
2017-08-02 15:14:23 -07:00
2017-08-03 10:12:29 -07:00
2017-08-03 18:17:36 +00:00
2017-07-31 16:01:03 -07:00
2017-08-03 18:18:32 +00:00
2017-07-31 21:14:11 +03:00
2017-07-28 07:25:52 -07:00
2017-08-01 20:37:54 +03:00
2017-07-31 16:03:12 -07:00
2017-07-25 10:29:20 -07:00
2017-07-07 01:30:02 -07:00
2017-05-18 18:59:34 +00:00
2017-08-03 08:09:44 -07:00
2017-07-28 07:25:52 -07:00
2017-07-07 10:14:08 -07:00
2017-05-18 18:59:34 +00:00
2017-07-26 10:50:19 -07:00
2017-07-31 21:14:11 +03:00
2017-07-31 19:29:01 -07:00

Fn CircleCI

Fn is an event-driven, open source, functions-as-a-service compute platform that you can run anywhere. Some of it's key features:

Prequisites

  • Docker 17.05 or later installed and running
  • Logged into Docker Hub (docker login)

Quickstart

Install CLI tool

This isn't required, but it sure makes things a lot easier. Just run the following to install:

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.

Run Fn Server

Then fire up an Fn server:

fn start

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.

Your First Function

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.

The following is a simple Go program that outputs a string to STDOUT. Copy and paste the code below into a file called func.go. Currently the function must be named func.your_language_extention (ie func.go, func.js, etc.)

package main

import (
	"fmt"
)

func main() {
	fmt.Println("Hello from Fn!")
}

Now run the following CLI commands:

# Initialize your function
# This detects your runtime from the code above and creates a func.yaml
fn init <DOCKERHUB_USERNAME>/hello

# Test your function
# This will run inside a container exactly how it will on the server
fn run

# Deploy your functions to the Fn server (default localhost:8080)
# This will create a route to your function as well
fn deploy myapp

Now you can call your function:

curl http://localhost:8080/r/myapp/hello

Or in a browser: http://localhost:8080/r/myapp/hello

That's it! You just deployed your first function and called it. Now to update your function you can update your code and run fn deploy myapp again.

To Learn More

Get Involved

User Interface

This is the graphical user interface for Fn. It is currently not buildable.

docker run --rm -it --link functions:api -p 4000:4000 -e "API_URL=http://api:8080" treeder/functions-ui

For more information, see: https://github.com/treeder/functions-ui

Next up

Check out the Tutorial Series.

It will demonstrate some of Fn capabilities through a series of exmaples. We'll try to show examples in most major languages. This is a great place to start!

Description
The container native, cloud agnostic serverless platform.
Readme Apache-2.0 170 MiB
Languages
Go 97.4%
Shell 1.2%
Ruby 0.5%
Makefile 0.4%
Dockerfile 0.4%
Other 0.1%