- Documentation
- About The Project
- Getting Started
- Installing
- Installing with docker
- Usage Examples
- Team
The development process of this project prioritized creating a flexible and user-friendly environment, always taking into account their security.
In its basic use the user needs to fill the profile information, being able to add photos, personal interests and express what they're looking for in their connections, be it a serious or casual relationship, even simple friendship. In this way the algorithm will return the best match option based on the information passed in the profile.
- Express
- bcryptjs
- cloudinary
- express-async-errors
- jsonwebtoken
- multer
- nodemailer
- pg
- typeorm
- yup
- class-transformer
- class-validator
- dotenv
These instructions will get you a copy of the project up and running on your local machine for development and testing purposes.
- Visual Studio Code - IDE
- Clone repository
git clone [email protected]:httTinder/httTinder-Api.git
- Copy the environment variables
cp .env.exemple .env
- Install dependencies
npm install
yarn
- Run the Migrations
npm run typeorm migration:run -d src/data-source.ts
yarn typeorm migration:run -d src/data-source.ts
- Start application
npm run dev
yarn dev
- Build application
docker-compose up --build
- Start application
docker-compose up
https://htttinder.herokuapp.com
Route responsible for creating new user
-
Field Type Description name string User's Name email string User's Email password string User's Passowrd age string user's Age
{
"email" :"[email protected]",
"name" : "fabio jose casanova",
"password" : "2209",
"age" : "33"
}
Route responsible for creating user profile or update any field on the user profile
-
Field Type Description orientation string User's Name gender string User's Gender bio string User's Short biography height string User's Height education string User's Education profession string User's Profession profileImage string User's Photo
If the id is not passed through params, the one provided by the token will be used.
{
"orientation" : "hétero",
"gender" : "Homem",
"bio" : "sou bem legal",
"height": 1.85,
"education" : "Formado",
"profession" : "Dev",
"profileImage" : "12530000"
}
{
"message": "Profile changed successfully"
}
- 400 : errors relating to the data reported in the field, check whether the data respects the maximum size or has been informed.
- 401 : error may refer to the validity of the token, the user, or whether the user was not adm.
- 403 : error regarding lack of authorisation.
- 404 : error user was not found
Route responsible for delete the profile
If the id is not passed through params, the one provided by the token will be used.
{
"message": "Profile deleted with sucess!"
}
- 400 : errors relating to the data reported in the field, check whether the data respects the maximum size or has been informed.
- 401 : error may refer to the validity of the token, the user, or whether the user was not adm.
- 403 : error regarding lack of authorisation.
- 404 : error user was not found
For more examples, please refer to the Documentation
Quality assurance Diego Guimarães |
Tech Lead Fábio Casanova |
Dev | UX/UI Fábio Junior |
Quality assurance Igor Garcia |
PO | UX/UI Mari Spinola |
Scrum master Matheus Freire |