Skip to content

Latest commit

 

History

History
72 lines (41 loc) · 3.31 KB

README_EN.md

File metadata and controls

72 lines (41 loc) · 3.31 KB
Raw


Poem-Admin
中文 | english

Introduction

An Admin panel build with axum/poem,sea-orm,vue3 etc.

open-api-version: branch-openapi

front-end:

https://github.com/lingdu1234/IUI314

Preview：

iui314.vercel.app preview iui314preview

Completed

  • User management：The user is the operator of the system panel. This module is used to configure system users。

  • Department management：Configure the organization (company, department, and group), display data permissions in a tree structure。

  • Post management：Set the position of a system user。

  • Menu management：Configure system menus, operation permissions, button permissions, and log etc。

  • Role management：assignment of role's Permissions。

  • Dictionary management：Maintenance of some relatively fixed data frequently used in the system。

  • Login-log：the log of user login behavior。

  • User online ：Monitor the users is online。

  • Scheduled task：Add modify delete tasks,also provide the log of the tasks。

  • Role-change: change the Permissions by change user's role。

  • Data-Permissions：all-permissions，only-department-permissions，department-permissions-and-the-department-is-undert-your-department，Custom-permissions，permissions of yourself (five modes)

  • department-change：an user can set a lot of department ,but one is enabled,can be changed,and the permissions is changed by change department；

  • System monitoring: a simple monitor of system information；

  • Data cache: according to api cache data, divided into public cache (everyone's cache data is consistent, used for public data cache) and personal cache (api cache of different data of different users of the same api), api is associated together through database name. When there is data update, the associated api cache data is cleared, cache time expires, cache data is cleared.

  • Operation log: set the logging level of each api in the menu, which is divided into file recording, database recording, and recording at the same time, not recording several modes, and configuring separately according to different api

  • front-end permissions management: routes are dynamically generated by the back-end return route; the front-end button-level permissions are uniformly controlled by the back-end return permission flag

Note

  1. The combination of department switching, role switching and data permissions can achieve a weird combination of permissions.

DataBase migration

  1. install tools 'sea-orm cli' : cargo install sea-orm-cli
  2. set the database url at .env file
  3. run：sea-orm-cli migrate up