Useful dummy server used for development.
make build
./bin/catfish --config ${YOUR_CONFIG}docker pull ghcr.io/soranoba/catfish
docker run -p 8080:8080 -p 8081:8081 -v ${YOUR_CONFIG}:/etc/catfish/config.yml soranoba/catfish| Field | Type | Required | Description |
|---|---|---|---|
| routes | Array<Route> |
x | When Catfish receives a request, it checks for matching Routes in order from the top, and the first matching Route is used. |
| Field | Type | Required | Example | Description |
|---|---|---|---|---|
| method | String |
o | GET |
HTTP method. Allowed values are GET, POST, PUT, DELETE or *.* means any HTTP method. |
| path | String |
o | /users/:id |
HTTP path. You can include path parameters. |
| parser | String |
x | json |
HTTP request body parser. Allowed value is json. |
| response | Array<Response> |
o | When Catfish receives a request, it decides to whether to use the preset in order from the top. |
| Field | Type | Required | Example | Description |
|---|---|---|---|---|
| name | String |
x | Success |
Response preset name |
| cond | String |
x | totalRequestCount < 2 |
Conditional expression indicating the probability of returning this response. |
| delay | Float |
x | 0.1 |
Delay time before response is returned. (sec) |
| status | Integer |
o | 200 |
HTTP Status code |
| redirect | String |
x | https://example.com/users |
A redirect to url. The status SHOULD be specified in the 3xx range. Request queries are automatically inherited. |
| header | Dictionary<String,String> |
x | HTTP response headers | |
| body | String |
x | {"message":"OK"} |
HTTP response body |
You can use formulas with variables.
The formula should return a probability value which range of [0.0, 1.0].
If the formula returns Boolean value, it means 1.0 or 0.0.
| Variable name | Description |
|---|---|
| routeRequestCount | Number of requests for the route. On the first request for route, this value is 1. |
| totalRequestCount | Total number of requests. On the first request, this value is 1. |
| param | Path parameters. It can access using param["name"]. |
| query | Query parameters. It can access using query["name"][0]. See also url.Values. |
| header | Headers. It can access using header["Content-Type"][0]. |
You can use two kinds of path parameters.
:prefix: Always match one segment.*prefix: Match any segments. (includes 0)
| Config path | Request path |
|---|---|
/users/:id |
✅/users/1✅ /users/1/❌ /users/❌ /users/1/follow |
/users/*path |
✅/users✅ /users/1/follow |
Catfish automatically add some headers in responses to easily debug with.
| Header name | Required | Description |
|---|---|---|
| X-CATFISH-PATH | o | Indicates that Catfish returned the response according to the path setting. |
| X-CATFISH-RESPONSE-PRESET-NAME | o | Indicates that Catfish returned the response according to the preset setting. |
| X-CATFISH-ERROR | x | The descriptions of an error. |
You can use variables, etc with text/template format.
The data passed to the template engine is main.Context.
Please access the admin port (default is 8081).
You can see the config, and confirm variables, etc.
If you want to customize it yourself, you can use the admin API.