If you like or are using this project to learn or start your solution, please give it a star. Thanks!
Yeti is a demand tracking application. Users open requests about applications. Admin users undertake these demands. The main element of the application is the demands. Side items are applications and users. The movements arising from these elements are presented graphically on the dashboard screen.It is not possible to become a member of the application. therefore, an admin user must add you to the application to be able to use the application.
- Only admin users have full authority over the application.
Non-admin users, other users, can only see their own demands and take action. Non-admin users cannot see their screens(Applications and users).
Written on the basis of the MVC (Model-Viewv-Controller) design pattern using modern PHP language. MSQL-MariaDB is used as database. In practice, no ready-made library or ORM tool is used for database operations. Migration processes are based on filing and raw SQL queries are executed. In the application, one-step sql queries such as where, update, insert into, select are defined as generic.However, a store procedure is used for queries that contain join. In the application, only the raw SQL query was written in the migration steps.
- By imitating Laravel Framework, we tried to prepare custom Laravel Framework.
| Developing | Tool |
|---|---|
| Graphics | HighCharts |
| Theme Components | Semantic UI |
| Javascript | Jquery |
| Datatables | Datatables.net |
| Database | MariaDB |
| Backend | Modern PHP |
- While developing the application, it tried to comply with the principles of SOLID KISSS and DRY.
- Static classes are derived for fixed objects. Used stored procedures and the constant data filling the dropdopwn list are kept in the Constant class.
- Making abstraction between classes that are related to each other. Each database model is derived from the DbModel class.Thus, each model has been able to call DbModel methods as they wish, and each model must have tableName, primaryKey .. methods.
User Stories
- When admin adds a new user, it gives him the initial password. The user can change his / her own password if he / she wishes.
- User passwords are saved as hashes. No user, including the admin user, can see the raw password.
- The admin user can add, delete, update and view the user information. However, if the logged in user is admin, he cannot delete himself.
- 403 and 404 error code requests are defined for http requests. The 403 error code is thrown when the user makes an unauthorized page request, or the 404 error code is thrown when the user tries to reach an invalid address. However, the generic page was written to show other error codes.
