Open blissman opened 8 years ago
I confirm no way to log into account whatever password reset attempt
Consider as must-have
Rip out bcryt & sorcery. Install devise.
Sub Task: Attention - might have to revise/re-do schema => update/changes per column.
I elect that we stick with sorcery for the MVP rather than move to devise
I think for the MVP, we can deploy the test users through the seed file, and then for the IoT the same. It means we have to modify the user to include an admin column
It's gonna be a big headache if we don't move to Devise now, IMO. Especially when/if OAUTH comes into play. The earlier we do it the easier it will be.
On Sep 1, 2016 7:12 PM, "Bliss Man" notifications@github.com wrote:
I think for the MVP, we can deploy the test users through the seed file, and then for the IoT the same. It means we have to modify the user to include an admin column
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/GortHealth/Kinly/issues/1#issuecomment-244239998, or mute the thread https://github.com/notifications/unsubscribe-auth/ADz-34b-7vTElER3nx7Btb84TztzTbkaks5ql1vdgaJpZM4JQ07n .
Just kind of looking through the Sorcery repo now, it's not actively being maintained and may not fully work with Rails 5. Another reason not to go down that road.
On Sep 2, 2016 7:21 AM, "Filip Stankovic" filips@gmail.com wrote:
It's gonna be a big headache if we don't move to Devise now, IMO. Especially when/if OAUTH comes into play. The earlier we do it the easier it will be.
On Sep 1, 2016 7:12 PM, "Bliss Man" notifications@github.com wrote:
I think for the MVP, we can deploy the test users through the seed file, and then for the IoT the same. It means we have to modify the user to include an admin column
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/GortHealth/Kinly/issues/1#issuecomment-244239998, or mute the thread https://github.com/notifications/unsubscribe-auth/ADz-34b-7vTElER3nx7Btb84TztzTbkaks5ql1vdgaJpZM4JQ07n .
So wise. Yeah, that's fair. Have a look at the Rails5 repo; it's already sort of going that direction.
Rip out current code (if there is any) for login, and replace with devise or something similar for password management.