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

Tutorial to use this app structure #2

Open
narayanpai opened this issue Apr 16, 2015 · 3 comments
Open

Tutorial to use this app structure #2

narayanpai opened this issue Apr 16, 2015 · 3 comments

Comments

@narayanpai
Copy link

Hi,

Do you have any tutorial to use the app structure or a tutorial app that I can take a look into

Thanks,

@comoser
Copy link
Owner

comoser commented Apr 17, 2015

Hi there!

I'm sorry I still haven't had the time to make a tutorial on how to work with this app structure. And I know it can be confusing in the beginning. I think I will be adding an option pretty soon that comes working already. With the github API for instance. Then the work is on adapting the code more than learn how to work with it.

If that would suffice, Saturday at the end of the day I may have that ready. I don't know your urgency, but that's the best I can do.

Thank for trying out my generator.

Best regards,
David Alecrim

No dia 16/04/2015, às 22:17, Narayan notifications@github.com escreveu:

Hi,

Do you have any tutorial to use the app structure or a tutorial app that I can take a look into

Thanks,


Reply to this email directly or view it on GitHub.

@narayanpai
Copy link
Author

Hi,

Its urgent and I kind of liked the folder structure. Any help would be great. Any suggestion, how could we restructure the app which is beased on various user roles

@comoser
Copy link
Owner

comoser commented Apr 17, 2015

The best advice I can give for now is to make an "auth" module, a "main" module which you can name what you like and then the rest of the modules from your app logic. The auth module is responsible for making the login, register and similar operations. The main module is the module called after the successful login and presents the base of your app. Then, according to actions in this module, call operations on other modules.

In order to support various user roles, on the response of the login call, the response should bring the user type, which you can store locally. Then, on your "main" module, you have conditions in your controller in order to choose what you want to show to that specific user type.

Without giving you examples, this is the best I can do

Repository owner locked and limited conversation to collaborators Apr 24, 2015
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants