updated readme
This commit is contained in:
parent
8d952febf0
commit
ad0df04535
19
README.md
19
README.md
@ -26,27 +26,16 @@ The PostgreSQL database must always run in Docker, regardless of your developmen
|
||||
|
||||
To start the database:
|
||||
```bash
|
||||
docker-compose -f docker-compose.dev.yml up db
|
||||
docker-compose up db
|
||||
```
|
||||
|
||||
### Option 1: Running Everything in Docker (Recommended for Development)
|
||||
### Running Services Separately (Recommended for Development)
|
||||
|
||||
1. **Start the Development Environment**
|
||||
```bash
|
||||
docker-compose -f docker-compose.dev.yml up
|
||||
```
|
||||
This will start:
|
||||
- Frontend on http://localhost:3000
|
||||
- Backend on http://localhost:14000
|
||||
- PostgreSQL database on port 19090
|
||||
|
||||
### Option 2: Running Services Separately (Recommended for Debugging)
|
||||
|
||||
For better debugging experience, you can run the frontend and backend in separate terminal windows, while keeping the database in Docker:
|
||||
For better debugging experience, run the frontend and backend in separate terminal windows, while keeping the database in Docker:
|
||||
|
||||
1. **First, ensure the database is running in Docker**
|
||||
```bash
|
||||
docker-compose -f docker-compose.dev.yml up db
|
||||
docker-compose up db
|
||||
```
|
||||
|
||||
2. **Then, in separate terminal windows:**
|
||||
|
Loading…
Reference in New Issue
Block a user