A creative solution to deal with issues some councils face. Creating a community app that allows and aids in getting the residence more involved as a community and helping the council reach their residence better. From creating a complaints board and a sort of reusable marketplace, to an event boards and important bin dates. All visible on a personal profile for the user to see what they're involved in
Deployed on https://florin-api.onrender.com/
- add an
.envfile with DB_URL= and PORT= to add your own database URL (e.g a ElephantSQL instance) and port- DB_URL like so
postgres://username:password@horton.db.elephantsql.com/instance
- DB_URL like so
npm installnpm run setup-dbnpm run dev, app will run on port in.envfile or 3000 if none is specified (http://localhost:[3000])
| Events | Complaints | Recycling | User | User Events |
|---|---|---|---|---|
GET /events |
GET /complaints |
GET /recycling |
POST /users/register |
GET /userevents |
GET /events/:id |
GET /complaints/:id |
GET /recycling/:id |
POST /users/login |
GET /userevents/:id |
POST /events |
POST /complaints |
POST /recycling |
GET /users/profile |
POST /userevents |
PATCH /events/:id |
PATCH /complaints/:id |
PATCH /recycling/:id |
GET /users/profile/:id |
PATCH /userevents/:id |
DELETE /events/:id |
DELETE /complaints/:id |
DELETE /recycling/:id |
GET /users/profile/:id/bin |
DELETE /userevents/:id |
GET /users/profile/:id/complaints |
||||
GET /users/events/:id |
- run
npm run init - run
npm run install - make sure you have a
.envwith the db_url - make sure there is data stored in the database before testing
- use
npm run test - or
npm run coverage