Nest.js CRUD Development with User Auth
Budget: $10 – $30 USD
I am seeking a skilled developer to join my team. The primary responsibility will be creating CRUD endpoints for our backend using Nest.js, TypeScript, and MongoDB.
Budget: circa $20 per module
The CRUD operations will be handling user data. This will involve:
- Creating new user records
- Reading user data
- Updating existing user information
- Deleting user records
Additionally, the project requires the setup of both authentication and authorization processes. The ideal candidate should have experience in:
- Creating and managing data endpoints
- Implementing secure authentication and authorisation protocols
- Working with Nest.js, TypeScript, and MongoDB
Your expertise in these areas will be crucial for the success of this project.
Nest.js, typescript, mongodb work. I have a project that is existing and you'll be joining other developers.
The project is about adding modules to the backend with their own set of CRUD endpoints
Example
An example of a request would be:
We need to add CRUD operations to manage a users profile. I will typically share a `schema/model` with all the fields. Then you would work as follows:
1. Clone the Repository
Only done once when setting up the project locally.
2. Fetch Latest from Main
Always start by updating your local `main` branch with the latest changes from the remote repository.
3. Create Your Feature Branch
Create a new branch from the updated `main` branch. Use a clear and descriptive name for the branch.
4. Make Changes
Implement your updates, whether it’s new features, bug fixes, or other changes.
5. Stage and Commit Your Changes
Add your changes and commit with a meaningful message summarising what you’ve done.
6. Push Your Branch to GitHub
Upload your branch to the remote repository to make it available for review.
7. Create a Pull Request (PR)
Open a PR from your feature branch into the `main` branch. Include a descriptive title and summary of changes.
8. Review and Merge
Another developer reviews your PR. Once approved, they merge the changes into `main`.
9. Sync Your Local Main Branch
After your PR is merged, update your local `main` branch to stay current with the latest code.
Budget: circa $20 per module
The CRUD operations will be handling user data. This will involve:
- Creating new user records
- Reading user data
- Updating existing user information
- Deleting user records
Additionally, the project requires the setup of both authentication and authorization processes. The ideal candidate should have experience in:
- Creating and managing data endpoints
- Implementing secure authentication and authorisation protocols
- Working with Nest.js, TypeScript, and MongoDB
Your expertise in these areas will be crucial for the success of this project.
Nest.js, typescript, mongodb work. I have a project that is existing and you'll be joining other developers.
The project is about adding modules to the backend with their own set of CRUD endpoints
Example
An example of a request would be:
We need to add CRUD operations to manage a users profile. I will typically share a `schema/model` with all the fields. Then you would work as follows:
1. Clone the Repository
Only done once when setting up the project locally.
2. Fetch Latest from Main
Always start by updating your local `main` branch with the latest changes from the remote repository.
3. Create Your Feature Branch
Create a new branch from the updated `main` branch. Use a clear and descriptive name for the branch.
4. Make Changes
Implement your updates, whether it’s new features, bug fixes, or other changes.
5. Stage and Commit Your Changes
Add your changes and commit with a meaningful message summarising what you’ve done.
6. Push Your Branch to GitHub
Upload your branch to the remote repository to make it available for review.
7. Create a Pull Request (PR)
Open a PR from your feature branch into the `main` branch. Include a descriptive title and summary of changes.
8. Review and Merge
Another developer reviews your PR. Once approved, they merge the changes into `main`.
9. Sync Your Local Main Branch
After your PR is merged, update your local `main` branch to stay current with the latest code.