kavicastelo / job_seeker

This project is built on only educational purpose. Job seeker is a free consultation company for seekers. This is in all around the world and seekers can select country, job category and best matching counsultant for their job target.

JobSeeker

JobSeeker is a web application developed as a university assignment. It is designed to facilitate the interaction between job seekers and consultants. The project uses Angular 15 for the frontend and Spring Boot 3 for the backend.

Demo

Table of Contents

• Technologies
• Getting Started
• Usage
• Login Credentials
• Functionality
• Deployment
• Security
• Local Setup

Technologies

• Frontend: Angular 15
• Backend: Spring Boot 3
• Database: MongoDB

Getting Started

To get started, follow the steps below:

1. Clone this repository.
2. Configure environment files in both the frontend and backend.
3. Install required dependencies.
4. Run the frontend and backend applications.

Usage

The application serves as a platform for job seekers to connect with consultants. Users can filter job listings based on country, job category, consultant name, and job role. Follow these steps to make an appointment:

1. Choose a country (e.g., American Samoa).
2. Select a job category (e.g., Art & Design Related).
3. Choose a consultant (e.g., Kavi Castelo).
4. Select a job role under the chosen category.

Login Credentials

Reception Panel:

• Username: [email protected]
• Password: Admin@12345

You can use consultants credentials too

Consultant Login (Sign In):

• Username: [email protected]

• Password: 123456

• Username: [email protected]

• Password: 123456

Consultant Apply:

nav bar > become a consultant or top bar > become a consultant > apply now

Functionality

• CRUD operations for job listings.
• Reception and consultant login with shared credentials.
• Filter function on the homepage for searching job listings.
• Authenticated access for secure operations.

Described only main function. Many more functions to have consultant and reception panels.

Deployment

• Frontend: Hosted on Netlify (https://seeker-by-kavi.netlify.app/)
• Backend: Hosted on Render (https://jobseeker-ftq4.onrender.com/)

Note: Backend loading time might be up to 30 seconds due to the free hosting plan.

Security

• Authentication and authorization mechanisms are integrated.
• CORS is configured to allow frontend access to backend APIs.
• Reception and consultant login credentials are shared for educational purposes.
• Passwords are not encrypted for simplicity and educational purposes.

Local Setup

To run the project locally:

1. Clone the repository.
2. Checkout the frontend branch and configure the environment files as instructed.
3. Checkout the backend branch and configure the CORS settings and application.properties.
4. Run the frontend and backend applications.

Remember to wait for a minute after loading the website for optimal data transfer.

---

Feel free to explore and contribute to this educational project! For any questions or issues, contact Kavindu Kokila.

job_seeker's Issues

Nested calling methods

When I'm trying to accept consultant request, both accepted email and ban email are sent to the consultant. It happening because springboot not providing update method. It only update works if matched requested ID and exsisting ID. I sent email address for idendifier and then springboot creates a new entity in database.

Avoide this issue, I tried to create a delete method using email identifier and it called after completed the updated method. However in my function works like this.

[email protected] is the identifier.

checkMethodIfAvailable([email protected]).subscribe((resp)=>{
  if(resp !== null){
    updateConsultantAsVerified([email protected]).subscribe((resp)=>{
      // in this method, creates new data set for [email protected](update not working)
      // send account approved email
      deleteCurrentOldConsultant([email protected]).subscribe((resp)=>{
        // send ban account email
      },
      err = > {
        //error handle
      })
    }, err = > {
      //error handle
    })
  }
}, err = > {
//error handle
})

Further more, I use deleteCurrentOldConsultant([email protected]) this method to ban consultant accounts in reception panel too.

Sudgest any method to fix this bug without creating another deleteAccount method(without sending email)