chore: sync running docker state
Commit the app code currently running in Docker, including scheduler, store status, journal reminder, maintenance mode, and Foodsharing API check updates. Remove generated runtime logs from version control and ignore local runtime captures.
This commit is contained in:
@@ -13,9 +13,18 @@
|
||||
- `npm start` – launch the CRA dev server on port 3000 with live reload.
|
||||
- `npm run build` – emit the production bundle into `build/`; run before `node server.js` or container builds.
|
||||
- `npm test` – run React Testing Library suites in watch mode; append `-- --watch=false` in CI.
|
||||
- `npm run check:foodsharing-api` – verify the Foodsharing endpoints used by the app against `https://foodsharing.de/api/doc`.
|
||||
- `node server.js` – serve the prebuilt UI and REST API using values from `.env` (e.g., `PICKUP_TOPIC`, credentials, ports).
|
||||
- `docker-compose up --build` – rebuild and start the containerized service, syncing the bundled UI and server.
|
||||
|
||||
## Required Close-Out Steps
|
||||
- After changes to `server.js`, `services/`, `src/`, `Dockerfile`, `docker-compose.yml`, or the Foodsharing API integration, always run this sequence completely:
|
||||
- `CI=true npm test -- --watch=false`
|
||||
- `npm run build`
|
||||
- `npm run check:foodsharing-api` when Foodsharing endpoints, payloads, or response mappings are affected
|
||||
- `docker compose up -d --build`
|
||||
- `curl http://localhost:3005/api/health` and confirm the response contains `"status":"ok"`
|
||||
|
||||
## Coding Style & Naming Conventions
|
||||
- Use 2-space indentation and Standard/Prettier-compatible formatting; rely on the CRA ESLint config (`react-app`, `react-app/jest`) for feedback.
|
||||
- Favor functional React components with PascalCase filenames (`PickupConfigEditor.js`) and camelCase props/state keys.
|
||||
|
||||
Reference in New Issue
Block a user