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
+18-18Lines changed: 18 additions & 18 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,15 +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:5174>
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:8001>
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:8001/docs>
18
18
19
-
Adminer, database web administration: <http://localhost:8080>
19
+
Adminer, database web administration: <http://localhost:8082>
20
20
21
-
Traefik UI, to see how the routes are being handled by the proxy: <http://localhost:8090>
21
+
Traefik UI, to see how the routes are being handled by the proxy: <http://localhost:8091>
22
22
23
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.
24
24
@@ -44,13 +44,13 @@ This is useful for:
44
44
* Verifying email content and formatting
45
45
* Debugging email-related functionality without sending real emails
46
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>.
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:1081>.
48
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`.
52
52
53
-
For the backend and frontend, they use the same port that would be used by their local development server, so, the backend is at `http://localhost:8000` and the frontend at `http://localhost:5173`.
53
+
For the backend and frontend, they use the same port that would be used by their local development server, so, the backend is at `http://localhost:8001` and the frontend at `http://localhost:5174`.
54
54
55
55
This way, you could turn off a Docker Compose service and start its local development service, and everything would keep working, because it all uses the same ports.
56
56
@@ -76,7 +76,7 @@ And then you can run the local development server for the backend:
76
76
77
77
```bash
78
78
cd backend
79
-
fastapi dev app/main.py
79
+
fastapi dev app/main.py --port 8001
80
80
```
81
81
82
82
## Docker Compose in `localhost.tiangolo.com`
@@ -188,19 +188,19 @@ The production or staging URLs would use these same paths, but with your own dom
Copy file name to clipboardExpand all lines: frontend/README.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,7 +13,7 @@ bun install
13
13
bun run dev
14
14
```
15
15
16
-
* Then open your browser at http://localhost:5173/.
16
+
* Then open your browser at http://localhost:5174/.
17
17
18
18
Notice that this live server is not running inside Docker, it's for local development, and that is the recommended workflow. Once you are happy with your frontend, you can build the frontend Docker image and start it, to test it in a production-like environment. But building the image at every change will not be as productive as running the local development server with live reload.
0 commit comments