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
Copy file name to clipboardExpand all lines: development.md
+31-31Lines changed: 31 additions & 31 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,27 +10,15 @@ docker compose watch
10
10
11
11
* Now you can open your browser and interact with these URLs:
12
12
13
-
Frontend, built with Docker, with routes handled based on the path: http://localhost:5173
13
+
Frontend, built with Docker, with routes handled based on the path: <http://localhost:5173>
14
14
15
-
Backend, JSON based web API based on OpenAPI: http://localhost:8000
15
+
Backend, JSON based web API based on OpenAPI: <http://localhost:8000>
16
16
17
-
Automatic interactive documentation with Swagger UI (from the OpenAPI backend): http://localhost:8000/docs
17
+
Automatic interactive documentation with Swagger UI (from the OpenAPI backend): <http://localhost:8000/docs>
18
18
19
-
Adminer, database web administration: http://localhost:8080
19
+
Adminer, database web administration: <http://localhost:8080>
20
20
21
-
Traefik UI, to see how the routes are being handled by the proxy: http://localhost:8090
22
-
23
-
## Mailcatcher
24
-
25
-
Mailcatcher is a simple SMTP server that catches all emails sent by the backend during local development. Instead of sending real emails, they are captured and displayed in a web interface.
26
-
27
-
This is useful for:
28
-
29
-
- Testing email functionality during development
30
-
- Verifying email content and formatting
31
-
- Debugging email-related functionality without sending real emails
32
-
33
-
The backend is automatically configured to use Mailcatcher when running with Docker Compose locally (SMTP on port 1025). All captured emails can be viewed at http://localhost:1080.
21
+
Traefik UI, to see how the routes are being handled by the proxy: <http://localhost:8090>
34
22
35
23
**Note**: The first time you start your stack, it might take a minute for it to be ready. While the backend waits for the database to be ready and configures everything. You can check the logs to monitor it.
36
24
@@ -46,6 +34,18 @@ To check the logs of a specific service, add the name of the service, e.g.:
46
34
docker compose logs backend
47
35
```
48
36
37
+
## Mailcatcher
38
+
39
+
Mailcatcher is a simple SMTP server that catches all emails sent by the backend during local development. Instead of sending real emails, they are captured and displayed in a web interface.
40
+
41
+
This is useful for:
42
+
43
+
* Testing email functionality during development
44
+
* Verifying email content and formatting
45
+
* Debugging email-related functionality without sending real emails
46
+
47
+
The backend is automatically configured to use Mailcatcher when running with Docker Compose locally (SMTP on port 1025). All captured emails can be viewed at <http://localhost:1080>.
48
+
49
49
## Local Development
50
50
51
51
The Docker Compose files are configured so that each of the services is available in a different port in `localhost`.
@@ -186,34 +186,34 @@ The production or staging URLs would use these same paths, but with your own dom
0 commit comments