You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
# overrides to use existing images in local Docker, otherwise will pull from repository
30
32
backend_pull_policy: "Never"
31
-
+emails_pull_policy: "Never"
33
+
emails_pull_policy: "Never"
32
34
frontend_pull_policy: "Never"
33
35
```
34
36
2. If you'd like to view emails in a service such as [smtp4dev](https://github.com/rnwood/smtp4dev) locally (see [Using smtp4dev](#using-smtp4dev)), rather than just viewing emails in pod logs, update your `chart/local.yaml` to include email sending options:
35
-
```diff
36
-
+email:
37
-
+ smtp_host: "host.docker.internal"
38
-
+ smtp_port: 2525
39
-
+ sender_email: example@example.com
40
-
+ password: password
41
-
+ reply_to_email: example@example.com
42
-
+ use_tls: false
37
+
```yaml hl_lines="1-7"
38
+
email:
39
+
smtp_host: "host.docker.internal"
40
+
smtp_port: 2525
41
+
sender_email: example@example.com
42
+
password: password
43
+
reply_to_email: example@example.com
44
+
use_tls: false
43
45
```
44
46
3. Build the updated backend and new emails images:
45
47
```sh
46
48
./scripts/build-backend.sh
49
+
```
50
+
```sh
47
51
./scripts/build-emails.sh
48
52
```
49
53
4. Deploy the changes you've made:
@@ -58,6 +62,6 @@ If you're using Docker Desktop or a similar Docker-compatible Kubernetes runtime
58
62
docker run --rm -it -p 5000:80 -p 2525:25 rnwood/smtp4dev
59
63
```
60
64
61
-
After a few seconds, you can then open http://localhost:3000.
65
+
After a few seconds, you can then open [localhost:3000](http://localhost:3000).
62
66
63
67
If you're using a different Kubernetes runtime (e.g. k3d, microk8s, etc) you may need to set `smtp_host` to something other than `host.docker.internal` in your `chart/local.yaml`, and you may also need to configure other options. k3d likely uses `host.k3d.internal`, and microk8s `10.0.1.1`, but double check with your Kubernetes runtime documentation.
0 commit comments