-
Notifications
You must be signed in to change notification settings - Fork 141
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
Documentation would be greatly appreciated #4
Comments
I apologize; I've been using this for my personal projects, and have been lagging on writing comprehensive docs. I will finish the documentation this evening. |
Sounds great. I can also note that I made some surprising headway when I just copy pasted the routes from |
I lied 3 days ago when I said I'd finish the docs the next day. I will still try to do this as soon as possible |
I've recently published a lot of new documentation for sails-auth and sails-permissions. I hope you find it useful. |
This is not aswered by any documentation in here, is it ? |
Corrected npmjs.org link & removed incorrect travis-link
I've been trying to bring sails-auth into an existing project and I have to say this is more painful due to the lack of documentation. There's good promise in sails-auth but can the project in its current state to really be used? If so, what exact steps does one need to do, what exactly needs to be implemented by hand and what does sails-auth implement.
I'm fine with manually adding tokens to users. All I want is to validate that this thing is going to work and to do that I need to know what templates / callbacks etc. need to be implemented and where.
PS. A note about the need to add
"auth-api": "sails-auth"
to.sailsrc
would be good.The text was updated successfully, but these errors were encountered: