Skip to content

Commit 8266ec7

Browse files
authored
Updated README with relevant docs
* ENG-1578 updated README * ENG-1578 added docker version badge
1 parent f0e1f25 commit 8266ec7

File tree

2 files changed

+71
-3
lines changed

2 files changed

+71
-3
lines changed

.github/workflows/dockerhub.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -16,6 +16,6 @@ jobs:
1616
- name: Update DockerHub Description
1717
uses: peter-evans/dockerhub-description@e98e4d1628a5f3be2be7c231e50981aee98723ae # v4.0.0
1818
with:
19-
username: ${{ secrets.DOCKERHUB_USERNAME }}
19+
username: ${{ secrets.DOCKERHUB_USER }}
2020
password: ${{ secrets.DOCKERHUB_TOKEN }}
2121
repository: amplifysecurity/smee-client

README.md

Lines changed: 70 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,2 +1,70 @@
1-
# smee-client image
2-
A minimal, secure docker image for [probot/smee-client](https://github.com/probot/smee-client).
1+
# `smee-client` Image
2+
3+
[![Amplify Security](https://github.com/amplify-security/smee-client-image/actions/workflows/amplify.yml/badge.svg?branch=main)](https://github.com/amplify-security/smee-client-image/actions/workflows/amplify.yml)
4+
[![Release](https://github.com/amplify-security/smee-client-image/actions/workflows/release.yml/badge.svg?branch=main)](https://github.com/amplify-security/amplify-security/actions/workflows/release.yml)
5+
[![Docker Pulls](https://img.shields.io/docker/pulls/amplifysecurity/smee-client?logo=docker)](https://hub.docker.com/r/amplifysecurity/smee-client)
6+
[![Image Size](https://img.shields.io/docker/image-size/amplifysecurity/smee-client?logo=docker)](https://hub.docker.com/r/amplifysecurity/smee-client)
7+
[![Image Version](https://img.shields.io/docker/v/amplifysecurity/smee-client?sort=semver&logo=docker)](https://hub.docker.com/r/amplifysecurity/smee-client/tags)
8+
9+
A minimal, secure docker image for [probot/smee-client](https://github.com/probot/smee-client). Currently, the
10+
[`amplifysecurity/smee-client`](https://hub.docker.com/r/amplifysecurity/smee-client)
11+
image size is under 93MB uncompressed.
12+
13+
## How to use this image
14+
15+
### Run `smee-client` using docker run
16+
17+
Running the image with no parameters will print the `smee-client` help message:
18+
19+
```
20+
$ docker run --rm amplifysecurity/smee-client
21+
Usage: smee [options]
22+
23+
Options:
24+
-v, --version output the version number
25+
-u, --url <url> URL of the webhook proxy service. Default:
26+
https://smee.io/new
27+
-t, --target <target> Full URL (including protocol and path) of the target
28+
service the events will forwarded to. Default:
29+
http://127.0.0.1:PORT/PATH
30+
-p, --port <n> Local HTTP server port (default: 3000)
31+
-P, --path <path> URL path to post proxied requests to` (default: "/")
32+
-h, --help display help for command
33+
```
34+
35+
Use the `-u` and `-t` parameters to connect to your [Smee.io](https://smee.io/) channel and forward
36+
events to your local target.
37+
38+
```
39+
$ docker run --rm amplifysecurity/smee-client -u $SMEE_URL -t http://localhost:8080/webhook
40+
Forwarding https://smee.io/******** to http://localhost:8080/webhook
41+
Connected https://smee.io/********
42+
```
43+
44+
### Run `smee-client` using docker compose
45+
46+
To use the image in docker compose, ensure that the smee service is linked to your receiving service.
47+
This image also specifies a non-root user (UID 1000) and so can be run with `no-new-privileges:true`.
48+
49+
```yaml
50+
services:
51+
smee:
52+
image: amplifysecurity/smee-client
53+
links:
54+
- api:api
55+
command: -u https://smee.io/******** -t http://api:8080/webhook
56+
security_opt:
57+
- no-new-privileges:true
58+
api:
59+
build:
60+
context: .
61+
ports:
62+
- "8080:8080"
63+
```
64+
65+
## Inspiration
66+
67+
This project was inspired by [deltaprojects/smee-client-docker](https://github.com/deltaprojects/smee-client-docker),
68+
which we have used in the past. However, this project was seemingly no longer maintained, and included several high-severity
69+
security issues. We plan to maintain this image by keeping up to date with upstream `smee-client` releases and security
70+
patches.

0 commit comments

Comments
 (0)