Rename location.

This commit is contained in:
Travis Reeder
2017-05-15 11:00:15 -07:00
parent c0b381eb96
commit 4b9bba352d
106 changed files with 274 additions and 273 deletions

View File

@@ -14,8 +14,8 @@ Listeners are the main way to extend IronFunctions.
The following listener types are supported:
* App Listeners - [GoDoc](https://godoc.org/github.com/kumokit/functions/api/server#AppListener)
* Runner Listeners - [GoDoc](https://godoc.org/github.com/kumokit/functions/api/server#RunnerListener)
* App Listeners - [GoDoc](https://godoc.org/github.com/treeder/functions/api/server#AppListener)
* Runner Listeners - [GoDoc](https://godoc.org/github.com/treeder/functions/api/server#RunnerListener)
### Creating a Listener
@@ -29,8 +29,8 @@ package main
import (
"context"
"github.com/kumokit/functions/api/server"
"github.com/kumokit/functions/api/models"
"github.com/treeder/functions/api/server"
"github.com/treeder/functions/api/models"
)
type myCustomListener struct{}

View File

@@ -21,5 +21,5 @@ TODO: List all metrics we emit to logs.
## Statsd
The [Logspout Statsd Adapter](https://github.com/kumokit/logspout-statsd) adapter can parse the log metrics and forward
The [Logspout Statsd Adapter](https://github.com/treeder/logspout-statsd) adapter can parse the log metrics and forward
them to any statsd server.

View File

@@ -15,7 +15,7 @@ Here's a rough diagram of what a production deployment looks like:
Any load balancer will work, put every instance of IronFunctions that you run behind the load balancer.
**Note**: We will work on a smart load balancer that can direct traffic in a smarter way. See [#151](https://github.com/kumokit/functions/issues/151).
**Note**: We will work on a smart load balancer that can direct traffic in a smarter way. See [#151](https://github.com/treeder/functions/issues/151).
## Database
@@ -33,7 +33,7 @@ The message queue is pluggable and we currently support a few options that can b
## Logging, Metrics and Monitoring
Logging is a particularly important part of IronFunctions. It not only emits logs, but metrics are also emitted to the logs. Ops teams can then decide how they want
to use the logs and metrics without us prescribing a particular technology. For instance, you can [logspout-statsd](https://github.com/kumokit/logspout-statsd) to capture metrics
to use the logs and metrics without us prescribing a particular technology. For instance, you can [logspout-statsd](https://github.com/treeder/logspout-statsd) to capture metrics
from the logs and forward them to statsd.
[More about Metrics](metrics.md)

View File

@@ -6,4 +6,4 @@
docker run --rm -it --link functions:api -p 4000:4000 -e "API_URL=http://api:8080" iron/functions-ui
```
For more information, see: https://github.com/kumokit/functions-ui
For more information, see: https://github.com/treeder/functions-ui