Reed Allman 2d8c528b48 S3 loggyloo (#511)
* add minio-go dep, update deps

* add minio s3 client

minio has an s3 compatible api and is an open source project and, notably, is
not amazon, so it seems best to use their client (fwiw the aws-sdk-go is a
giant hair ball of things we don't need, too). it was pretty easy and seems
to work, so rolling with it. also, minio is a totally feasible option for fn
installs in prod / for demos / for local.

* adds 's3' package for s3 compatible log storage api, for use with storing
logs from calls and retrieving them.
* removes DELETE /v1/apps/:app/calls/:call/log endpoint
* removes internal log deletion api
* changes the GetLog API to use an io.Reader, which is a backwards step atm
due to the json api for logs, I have another branch lined up to make a plain
text log API and this will be much more efficient (also want to gzip)
* hooked up minio to the test suite and fixed up the test suite
* add how to run minio docs and point fn at it docs

some notes: notably we aren't cleaning up these logs. there is a ticket
already to make a Mr. Clean who wakes up periodically and nukes old stuff, so
am punting any api design around some kind of TTL deletion of logs. there are
a lot of options really for Mr. Clean, we can notably defer to him when apps
are deleted, too, so that app deletion is fast and then Mr. Clean will just
clean them up later (seems like a good option).

have not tested against BMC object store, which has an s3 compatible API. but
in theory it 'just works' (the reason for doing this). in any event, that's
part of the service land to figure out.

closes #481
closes #473

* add log not found error to minio land
2017-11-20 17:39:45 -08:00
2017-11-20 17:39:45 -08:00
2017-11-20 17:39:45 -08:00
2017-11-18 16:03:50 +00:00
2017-10-31 15:37:13 +00:00
2017-11-17 15:53:44 -08:00
2017-11-20 17:39:45 -08:00
2017-07-25 10:29:20 -07:00
2017-11-17 15:53:44 -08:00
2017-05-18 18:59:34 +00:00
2017-11-17 15:59:36 +00:00
2017-11-20 17:39:45 -08:00
2017-11-20 17:39:45 -08:00
2017-10-06 08:42:33 -07:00
2017-05-18 18:59:34 +00:00
2017-07-26 10:50:19 -07:00
2017-11-17 15:53:44 -08:00
2017-10-11 06:50:32 -07:00
2017-11-18 07:09:43 -08:00
2017-11-20 17:39:45 -08:00

Fn Project

CircleCI GoDoc Go Report Card

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
  • A Docker Hub account (Docker Hub) (or other Docker-compliant registry)
  • Log Docker into your Docker Hub account: 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 - MacOS

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.

User Interface

We also have an open source graphical user interface for Fn. It's very easy to use, simply run the command below:

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

For more information, see: https://github.com/fnproject/ui

Learn More

Get Help

Get Involved

Stay Informed

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%