From ad0df04535fb0ab743a4b62db1ab0cb2d5ed03b7 Mon Sep 17 00:00:00 2001 From: liquidrinu Date: Thu, 15 May 2025 18:05:03 +0200 Subject: [PATCH] updated readme --- README.md | 19 ++++--------------- 1 file changed, 4 insertions(+), 15 deletions(-) diff --git a/README.md b/README.md index 21b37e6..e40cc3f 100644 --- a/README.md +++ b/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:**