Twisk is a starter kit for Twirp - a framework for service-to-service communication emphasizing simplicity and minimalism.
It contains things you need to kickstart your project - structured packaging, logging, autogenerated swagger docs, handlers for login/refresh and user CRUD.
I made this project as a preparation for Gophercon 2018 Lightning Talk - Building robust APIs with Twirp.
Read more about Twirp on the official repo, release blog post and documentation website.
Twisk currently has:
- Fully featured RESTful endpoints for authentication and CRUD operations on the user entity
- Session handling using JWT claims
- JWT Based authentication
- Application configuration via config file (yaml)
- RBAC (role-based access control)
- Structured logging
- Request marshaling and data validation
- Autogenerated API Docs using SwaggerUI
- Mocking using stdlib
- Basic test coverage
The following dependencies are used in this project (generated using Glice):
|---------------------------------------|-----------------------------------------------|-------------|
| DEPENDENCY | REPOURL | LICENSE |
|---------------------------------------|-----------------------------------------------|-------------|
| github.com/golang/protobuf | https://github.com/golang/protobuf | bsd-3-clause|
| gopkg.in/yaml.v2 | https://github.com/go-yaml/yaml | Apache-2.0 |
| github.com/mwitkow/go-proto-validators| https://github.com/mwitkow/go-proto-validators| Apache-2.0 |
| github.com/twitchtv/twirp | https://github.com/twitchtv/twirp | Other |
| github.com/gorilla/mux | https://github.com/gorilla/mux | bsd-3-clause|
| github.com/justinas/alice | https://github.com/justinas/alice | MIT |
| github.com/go-pg/pg | https://github.com/go-pg/pg | bsd-2-clause|
| github.com/rs/xid | https://github.com/rs/xid | MIT |
| github.com/nbutton23/zxcvbn-go | https://github.com/nbutton23/zxcvbn-go | MIT |
| github.com/rakyll/statik | https://github.com/rakyll/statik | Apache-2.0 |
| github.com/dgrijalva/jwt-go | https://github.com/dgrijalva/jwt-go | MIT |
| github.com/rs/zerolog | https://github.com/rs/zerolog | MIT |
|---------------------------------------|-----------------------------------------------|-------------|
- Protobuf - Proto formats (timestamp)
- Yaml - Unmarshalling YAML config file
- Twirp - RPC Framework
- Mux - Router
- Alice - Chaining middlewares
- PG - PostgreSQL ORM
- Statik - Static files to binary generator
- JWT-GO - JWT Authentication
- Zerolog - Logging
- XID - Refresh token generation
- ZXCVBN-Go - Password strength checker
Most of these can easily be replaced with your own choices since their usage is abstracted and localized. In addition to these, the following tools were used:
- Retool - Go executables vendoring
- GoValidators - Proto (request/response) validation
- TwirpSwagger - Swagger docs generator from proto definitions
Twisk's project structure mostly follows THIS example repository.
Twisk doesn't follow all best practices advices by Twirp. For example, functions are named List
, Create
and Delete
instead of ListUsers
, CreateUser
and DeleteUser
(I prefer shorter function names, handlers and functions named user.List
istead of user.ListUsers
). You can read on Twirp's best practices here.
Using Twisk requires having Go 1.7 or above. Once you downloaded Twisk (either using Git or go get) you need to configure the following:
-
To use Twisk as a starting point of a real project whose package name is something like
github.com/author/project
, move the directory$GOPATH/omolle.com/fnd/server
to$GOPATH/github.com/author/project
and do a global replacement of the stringomolle.com/fnd/server
withgithub.com/author/project
. -
Change the configuration file according to your needs. The local config file is found in
cmd/api/conf.local.yaml
. You'll need to configuredatabase/psn
at least. -
In cmd/migration/main.go set up psn variable and then run it (go run main.go). It will create all tables, and necessary data, with a new account username/password admin/admin.
-
Run the app using:
go run cmd/api/main.go
The application runs as an HTTP server at port 8080. It exposes the following endpoints:
GET /openapi/swaggerui
: returns list of swagger specs in browserPOST /twirp/twisk.iam.IAM/Auth
: accepts username or email and password. Returns jwt token and refresh tokenPOST /twirp/twisk.iam.IAM/Refresh
: refreshes sessions and returns new jwt tokenPOST /twirp/twisk.user.User/Create
: creates a new userPOST /twirp/twisk.user.User/List
: returns list of usersPOST /twirp/twisk.user.User/View
: returns single userPOST /twirp/twisk.user.User/Delete
: deletes a userPOST /twirp/twisk.user.User/Update
: updates user's contact info
You can log in as admin to the application by sending a post request to localhost:8080/twirp/twisk.iam.IAM/Auth with auth admin
and password admin
in JSON body.
-
Under
proto
folder, create a new one named after your service. For exampletenant
. Inside it createservice.proto
-
Define your proto file. If you are not familiar with Protobufs, you can read more about it here. You can use already existing proto files (
proto/user/service.proto
&proto/iam/service.proto
) as a template. -
Run
make twirp -B
. -
Implement the Tenant interface from
service.twirp.go
ininternal/tenant
. -
Tenant service integrations are located in
internal/tenant/platform
. For example cloud storage, database, message queue etc. -
Implement the interface in logging.go, wrapping around the service implementation.
-
Add service link to
openapi/swagger.html
. Alternatively, use build-links in your CI/CD pipeline to auto-generate theswagger.html
fromswagger.html.template
. -
Wire up everything in
cmd/api/main.go
. If neeeded, you can easily skip auth checking on certain routes by passing the service name tohooks.WithJWTAuth()
. For examplehooks.WithJWTAuth(j, "View","List")
.
Twisk is licensed under the MIT license. Check the LICENSE file for details.
Special thanks to @tonto for previously creating some parts of this project.