mirror of
https://github.com/jhillyerd/inbucket.git
synced 2025-12-18 10:07:02 +00:00
update tag
@@ -91,7 +91,7 @@ The development server features hot code loading, so most changes you make to th
|
||||
Build the container from the root `inbucket` directory:
|
||||
|
||||
```sh
|
||||
docker build . -t inbucket/inbucket:latest
|
||||
docker build . -t inbucket/inbucket:edge
|
||||
```
|
||||
|
||||
The `Dockerfile` uses a multi-stage build, the first container installs all the Go and Elm dependencies and builds Inbucket. The output of the build is then copied to a minimal container.
|
||||
@@ -108,7 +108,7 @@ which is equivalent to the following docker command:
|
||||
docker run -p 9000:9000 -p 2500:2500 -p 1100:1100 \
|
||||
-v /tmp/inbucket/config:/config \
|
||||
-v /tmp/inbucket/storage:/storage \
|
||||
inbucket/inbucket
|
||||
inbucket/inbucket:edge
|
||||
```
|
||||
|
||||
This forwards the default HTTP (9000), SMTP (2500) and POP3 (1100) ports into the container, and maps the storage volumes into `/tmp/inbucket`. Using the same default ports means you can still run `etc/swaks-tests/run-tests.sh` to populate it with email.
|
||||
|
||||
Reference in New Issue
Block a user