Reed Allman 46dfbd362d mask models.Call blank fields in api, sqlx
sqlx has nice facilities for using structs to do queries and using their
fields, so decided to move us all over to this. now when you take a look at
models.Call it's really obvious what's in db and what's not. added omitempty
to some json fields that were bleeding through api too.

deletes a lot of code in the sql package for scanning and made some queries
use struct based sqlx methods now which seem easier to read than what we
previously had. moves all json stuff into sql.Valuer and sql.Scanner methods
in models/config.go, these are the only 2 types that ever need this. sadly,
sqlx would have done this marshaling for us, but to keep compat, I added json.
we can do some migrations later maybe for a more efficient encoding, but did
not want to fuss with it today.

it seems like we should probably aim to keep models.Call as small as possible
in the db as there will be a lot of them. interestingly, most functions
platforms I looked at do not seem to expose this kind of information that I
could find. so, i think only having timestamps, status, id, app, path and
maybe docker stats is really all that should be in here (agree w/ Denys on
284 as these and logs will end up taking up most db space in prod. notably,
payload, headers, and env vars could be extremely large and in the general
case they are always a copy of the routes (this breaks apart when routes are
updated, which would be useful considering we don't have versioning --
versioning may be cheaper).

removed unused field in apps too

this is lined up behind #349 so that I could use the tests...

closes #345
closes #142
closes #284
2017-09-21 03:18:24 -07:00
2017-09-14 10:57:22 -07:00
2017-09-20 11:35:18 -07:00
2017-09-25 17:54:04 +03:00
2017-09-26 02:12:01 +00:00
2017-09-19 14:14:42 -07:00
2017-09-18 23:33:47 -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-09-19 14:14:42 -07:00
2017-09-19 14:14:42 -07:00
2017-09-06 21:48:29 +03:00
2017-05-18 18:59:34 +00:00
2017-07-26 10:50:19 -07:00
2017-08-23 22:51:27 -07:00
2017-09-21 12:33:15 +03:00

Fn CircleCI

GoDoc

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

The command line tool isn't required, but it sure makes things a lot easier. There are a few options to install it:

1. Homebrew

If you're on a Mac and use Homebrew, this one is for you:

brew install fn

2. Shell script

This one works on Linux and MacOS (partially on Windows):

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.

3. Download the bin

Head over to our releases and download it.

Run Fn Server

Now 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.

First, create an empty directory called hello and cd into it.

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.

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

# Set your Docker Hub username
export FN_REGISTRY=<DOCKERHUB_USERNAME>

# 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 --app myapp

Now you can call your function:

curl http://localhost:8080/r/myapp/hello
# or:
fn call myapp /hello

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

That's it! You just deployed your first function and called it. 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%