Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PostgresQl database setup #5

Open
iqquee opened this issue Mar 22, 2022 · 0 comments
Open

PostgresQl database setup #5

iqquee opened this issue Mar 22, 2022 · 0 comments
Labels
enhancement New feature or request

Comments

@iqquee
Copy link
Owner

iqquee commented Mar 22, 2022

If we must call this an auth package, I don't see a reason why only one type of database should be used(which currently is mongodb). A developer should be able to choose a database which matches with the database he/she wishes to use throughout the development circle of their project and not compelling them to use only a specific kind of database. They should be able to choose to use either Mongodb, Postgres, Mariadb, Redis and so on for as many databases we have on the package.

A PostgresQl database server should be set up and integrated to the sign-up and sign-in functions along side the jwt-token function.

@iqquee iqquee added the enhancement New feature or request label Mar 22, 2022
@iqquee iqquee self-assigned this Mar 22, 2022
@iqquee iqquee changed the title PosgresQl database setup PostgresQl database setup Mar 22, 2022
@iqquee iqquee removed their assignment Mar 26, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant