Skip to content

ivanrivaldi191/keda_interview

Repository files navigation

Laravel Back End Keda Interview Manual

## Guidelines to do the project's There are several prerequisite apps/packages before making this project, such as:
1. PHP : version that is used on this project is PHP 7.4.14
2. Composer (Laravel) : version that is used on this project is Laravel Framework 8.35.1
3. PostgreSQL : version that is used on this project is postgres (PostgreSQL) 13.1

Next steps are:

  1. From terminal run the command to clone repo : "https://github.com/ivanrivaldi191/keda_interview.git"
  2. Move to the cloned repo
  3. Composer install or update
  4. Open the project with a text editor Identify .env.example on the root directory Copy .env.example and copy it to .env Change the following fields in the .env file: DB_DATABASE=dbname DB_USERNAME=dbuser DB_PASSWORD=dbpassword
  5. php artisan key:generate

Tasks to be done are:

  1. Identify and fix the problems that exist in the project (Hint: Started from migration until seeder)
    Note: You are not allowed to make a new migration/seeder file for the user / user type
    ,the password in seeder is bcrypted goes by "dummydummy"
    You must only use api.php for the "routing"

  2. Create Model for Customer and Controllers that support following features:

    • Login
    • Logout
    • Message to other Customer(s)
    • View own chat history
    • Can report other Customer(s) or own feedback/bug to Staff
  3. Create Model for Staff and Controllers that support following features:

    • Login
    • Logout
    • View all chat history
    • View all Customer + deleted Customer
    • Message to other Staff(s)
    • Message to other Customer(s)
    • Delete Customer(s)
  4. Auth on each page or feature

  5. You can create own Model and controllers to support point no 2 & 3, for example Model "Messages" to support Customer and Staff.
    You must not use any other packages / vendors, only from the composer or auth related are allowed which means only Laravel Passport or JWT only.

  6. You are only tasked to work on the back-end side, so view is not important. Use postman for the documentation.

  7. As for the testing you are allowed to use phpunittest or any php/Laravel testing.

About

No description, website, or topics provided.

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published