Need to document our project. As a part of that, we need to start off by documenting the API.
I suggest to use a standard technology like OpenAPI or Swagger.

Use Docker and Docker Compose to containerize this.

• Use mysql:5.7-debian for MySQL
• Use node:18.18.2-alpine3.18 for Node

Make sure to write the YAML configuration, along with networking for Docker Compose

Create a Post component (React.js) in the client application.

It should have the following functionalities.

• On top bar - left: there should be the avatar of the user's profile picture, followed by the user's name
• On top bar - rigt: there should be the more icon (tripple-dot) for options
• In the middle, there should be the photo of the post. Note that there can be posts without a photo, so this part can be null in some cases.
• On the bottom, there should be two buttons for likes and comments
• Like and comment buttons should have a number value on them that displays the current like count / comment count of the post

If you have any questions, please use discussions.
Happy coding ❤️

Need a page in the client application for editing a user profile.
It should have input fields for the following:

• Profile picture
• First name, Last name
• Profile Bio
• Date of birth

If any of the above mentioned fields are not visible in the Profile component, please make them available there too.

A post should contain comments

The client application should support the authentication mechanisms provided by the server. It uses OAuth 2.0 bearer token system for authentication and authorization.

• The client should store the token info locally and securely upon login
• At each API call, the authorization header should be included

The response data of most endpoints are not filered. They just return everything in the table. This is a vulnerability of our platform and need immediate attention.

eg: get profile returns password hashes

Create a page for resetting the user's password in the client application.

• It should have input fields for password and confirm password
• Should send a get request to {baseurl}/auth/forgot?code={verification-code} with the new password as body form-data
• The verification code comes to the page as a query parameter

Need to make post, react, comment entities depend on the user entity. If a user is deleted, all his comments, reactions and posts should be deleted too.

Posts of users should be editable, so we need to provide the users with the ability to edit their posts

We need to integrate the client and the server applications.
The API documentation is available at Postman.

We are hoping to use React.js to create a client web application. Please get started with that.
@UdariAdhikaram @isurudayananda @NadeeTharuka

When a new user is registered, we need to send him a verification email. The user can click on the link in the email to verify his account. Non-verified accounts are not allowed to login.
A code is used for the verification purpose.

• An email should be designed with HTML, with a link in the page.
• That link should contain {baseurl}/auth/confirm?code={code}

This process will verify the user account.

• Use nodemailer for email sending.
• Can use Gmail service with app passwords in the environment.

As per the requirement, we need to use MySQL triggers in our application.
And, I have designed the server application that would just fit that.
We can use triggers to

• handle the post cont for users
• handle the comment and react count for a post

Please get on with this.
Make sure to handle the decrement as well as the increment.

Need to create a landing page after successful signup. The user still is not able to login, since the account is not verified, so need to tell the user to verify his/her account.
Need to create a landing page for that.

We also need to create a landing page after user's request to reset password.
The user can click on 'forgot password' in login page. After that, we need a page for the user to be directed. It should say something like 'please check your emails for a password reset link'.

Create a way to show error messages to the user in the client application. For example, when an API reqeust fails, or credentials are invalid, at the moment, we do nothing. A descriptive error message should be prompted.