[backend] stabilise codebase

This commit is contained in:
2025-10-11 20:09:05 +02:00
parent 2886fa9f0c
commit 1e812c93a6
36 changed files with 487 additions and 212 deletions
+8 -2
View File
@@ -13,7 +13,8 @@ This repository hosts a proof-of-concept "points of interest" application compos
- npm 10+
- PHP 8.2+
- Composer 2+
- A running database supported by Doctrine (SQLite is used by default for local development)
- Docker (to run the bundled Postgres + PostGIS service)
- PostgreSQL 16 with the PostGIS extension (a ready-to-use container is provided via Docker Compose)
## Running the API server
@@ -21,9 +22,13 @@ This repository hosts a proof-of-concept "points of interest" application compos
cd server
composer install
# Create the database schema (SQLite by default)
# Boot the Postgres + PostGIS container
docker compose up -d postgres
# Prepare the database schema
php bin/console doctrine:database:create --if-not-exists
php bin/console doctrine:migrations:migrate --no-interaction
php bin/console doctrine:fixtures:load
# Start the Symfony development server
symfony server:start
@@ -49,4 +54,5 @@ The client starts on `http://localhost:5173`. Set the `VITE_API_BASE`, `VITE_MER
## Additional notes
- The API uses Mercure for real-time updates. Ensure a Mercure hub is running and reachable by the client when testing streaming features.
- The default `DATABASE_URL` now targets the bundled PostgreSQL/PostGIS container. Update it if you run the database elsewhere, and rerun migrations after switching databases.
- Review the individual `README.md` files inside `client/` and `server/` for more detailed configuration guidance.