PerlDancer / PerlDancer/Dancer2-Plugin-Auth-Extensible
Dancer2::Plugin::Database
Nobody has claimed this yet.
- Dominant language
- Perl
- Stars
- 10
- Forks
- 21
- PR merge metrics
- No merged PRs in 30d
Description
The latest available versions are installed via cpanm. Postgresql database.
Changing the settings does not affect the operation of the module, the data is taken by default.
Authorization works, and the list of roles can not be obtained.
To store information on the user, another table has been created, where e-mail, fullname, address is stored. Id in both tables are the same.
disable_roles: 0
users_table: 'auth'
roles_table: 'roles'
user_roles_table: 'auth_roles'
users_id_column: 'id'
users_username_column: 'login'
users_password_column: 'password'
roles_id_column: 'id'
roles_role_column: 'role'
user_roles_user_id_column: 'auth_id'
user_roles_role_id_column: 'roles_id'
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the Dancer2::Plugin::Database behavior with the listed PostgreSQL tables and configuration values, then inspect how settings and role lookup are handled. Done means the configured tables and columns are used and the user's roles can be retrieved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- perl, postgresql
- Domain
- authentication, database
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100