Skip to content

Commit 9810994

Browse files
Merge pull request #33 from go-kit/examples
Update links to examples
2 parents cf81d0b + fe1271a commit 9810994

File tree

3 files changed

+11
-11
lines changed

3 files changed

+11
-11
lines changed

_src/examples/index.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -12,22 +12,22 @@ Here you can find some examples that will orient you to Go kit idioms,
1212
writing a service from first principles. It can help you understand
1313
the decisions that went into Go kit's design.
1414

15-
- **[addsvc](https://github.com/go-kit/kit/blob/master/examples/addsvc)**
15+
- **[addsvc](https://github.com/go-kit/examples/blob/master/addsvc)**
1616
is the original example service.
1717
It exposes a set of operations over all supported transports.
1818
It's fully logged, instrumented, and uses distributed tracing.
1919
It also demonstrates how to create and use client packages.
2020
It demonstrates almost all of Go kit's features.
2121

22-
- **[profilesvc](https://github.com/go-kit/kit/blob/master/examples/profilesvc)**
22+
- **[profilesvc](https://github.com/go-kit/examples/blob/master/profilesvc)**
2323
demonstrates how to use Go kit
2424
to write a microservice with a REST-ish API.
2525
It uses net/http and the excellent Gorilla web toolkit.
2626

27-
- **[shipping](https://github.com/go-kit/kit/blob/master/examples/shipping)**
27+
- **[shipping](https://github.com/go-kit/examples/blob/master/shipping)**
2828
is a complete, "real-world" application composed of multiple microservices,
2929
based on Domain Driven Design principles.
3030

31-
- **[apigateway](https://github.com/go-kit/kit/blob/master/examples/apigateway)**
31+
- **[apigateway](https://github.com/go-kit/examples/blob/master/apigateway)**
3232
demonstrates how to implement the [API gateway pattern](http://microservices.io/patterns/apigateway.html)
3333
backed by a Consul service discovery system.

_src/examples/stringsvc.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -179,7 +179,7 @@ func encodeResponse(_ context.Context, w http.ResponseWriter, response interface
179179

180180
## stringsvc1
181181

182-
The complete service so far is [stringsvc1](https://github.com/go-kit/kit/blob/master/examples/stringsvc1).
182+
The complete service so far is [stringsvc1](https://github.com/go-kit/examples/blob/master/stringsvc1).
183183

184184
```
185185
$ go get github.com/go-kit/kit/examples/stringsvc1
@@ -200,7 +200,7 @@ No service can be considered production-ready without thorough logging and instr
200200
## Separation of concerns
201201

202202
Separating each layer of the call graph into individual files makes a go-kit project easier to read as you increase the number of service endpoints.
203-
Our first example [stringsvc1](https://github.com/go-kit/kit/blob/master/examples/stringsvc1) had all of these layers in a single main file.
203+
Our first example [stringsvc1](https://github.com/go-kit/examples/blob/master/stringsvc1) had all of these layers in a single main file.
204204
Before we add more complexity, let's separate our code into the following files and leave all remaining code in main.go
205205

206206
Place your **services** into a service.go file with the following functions and types.
@@ -475,7 +475,7 @@ func main() {
475475

476476
## stringsvc2
477477

478-
The complete service so far is [stringsvc2](https://github.com/go-kit/kit/blob/master/examples/stringsvc2).
478+
The complete service so far is [stringsvc2](https://github.com/go-kit/examples/blob/master/stringsvc2).
479479

480480
```
481481
$ go get github.com/go-kit/kit/examples/stringsvc2
@@ -661,7 +661,7 @@ func proxyingMiddleware(instances string, logger log.Logger) ServiceMiddleware {
661661

662662
## stringsvc3
663663

664-
The complete service so far is [stringsvc3](https://github.com/go-kit/kit/blob/master/examples/stringsvc3).
664+
The complete service so far is [stringsvc3](https://github.com/go-kit/examples/blob/master/stringsvc3).
665665

666666
```
667667
$ go get github.com/go-kit/kit/examples/stringsvc3
@@ -728,6 +728,6 @@ It's possible to use Go kit to create a client package to your service,
728728
to make consuming your service easier from other Go programs.
729729
Effectively, your client package will provide an implementation of your service interface,
730730
which invokes a remote service instance using a specific transport.
731-
See [addsvc/cmd/addcli](https://github.com/go-kit/kit/blob/master/examples/addsvc/cmd/addcli)
732-
or [package profilesvc/client](https://github.com/go-kit/kit/blob/master/examples/profilesvc/client)
731+
See [addsvc/cmd/addcli](https://github.com/go-kit/examples/blob/master/addsvc/cmd/addcli)
732+
or [package profilesvc/client](https://github.com/go-kit/examples/blob/master/profilesvc/client)
733733
for examples.

_src/faq/index.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -210,7 +210,7 @@ It's unlikely that a business-domain error from your service
210210
should cause a circuit breaker to trip in a client.
211211
So, it's likely that you want to encode errors in your response struct.
212212

213-
[addsvc](http://github.com/go-kit/kit/tree/master/examples/addsvc)
213+
[addsvc](http://github.com/go-kit/examples/tree/master/addsvc)
214214
contains examples of both methods.
215215

216216
# More specific topics

0 commit comments

Comments
 (0)