| # |
Jul 17th 2009, 12:58 |
ProLoser|Work |
things that work WITH auth or are replacements to |
| # |
Jul 17th 2009, 12:58 |
ProLoser|Work |
everyone has done /different/ stuff |
| # |
Jul 17th 2009, 12:58 |
ProLoser|Work |
i looked around |
| # |
Jul 17th 2009, 12:58 |
ProLoser|Work |
cuz i don't think anyones done it |
| # |
Jul 17th 2009, 12:58 |
ProLoser|Work |
which i think is exactly what a shell is |
| # |
Jul 17th 2009, 12:58 |
techno-geek |
but why re-invent something someone else has done? |
| # |
Jul 17th 2009, 12:58 |
ProLoser|Work |
i'm simply generate a template of my controller/actions/model |
| # |
Jul 17th 2009, 12:58 |
ProLoser|Work |
it's not time-intensive |
| # |
Jul 17th 2009, 12:57 |
techno-geek |
seems like something someone already probably did |
| # |
Jul 17th 2009, 12:57 |
techno-geek |
I would do some intense googling for current solutions before I invested the time on that |
| # |
Jul 17th 2009, 12:56 |
ProLoser|Work |
i guess i could just make a shell script |
| # |
Jul 17th 2009, 12:56 |
ProLoser|Work |
otherwise it's a template controller/model/views |
| # |
Jul 17th 2009, 12:55 |
ProLoser|Work |
it just screams plugin to me |
| # |
Jul 17th 2009, 12:55 |
ProLoser|Work |
if i always have a forgotten pass action, a register action, a change pass, edit profile, stuff like that |
| # |
Jul 17th 2009, 12:55 |
ProLoser|Work |
i /do/ just copy paste the code but it seems like that's what a plugin IS |
| # |
Jul 17th 2009, 12:55 |
ProLoser|Work |
plus the matter of the custom user validation/actions |
| # |
Jul 17th 2009, 12:54 |
ProLoser|Work |
figure do both and make it worth the while |
| # |
Jul 17th 2009, 12:54 |
ProLoser|Work |
but acl? |
| # |
Jul 17th 2009, 12:54 |
techno-geek |
*minutes |
| # |
Jul 17th 2009, 12:54 |
techno-geek |
it takes less than 5 minuts |
| # |
Jul 17th 2009, 12:54 |
techno-geek |
Auth is trivial to setup though |
| # |
Jul 17th 2009, 12:53 |
ProLoser|Work |
but iunno it was just cuz i'm reusing it so much |
| # |
Jul 17th 2009, 12:53 |
ProLoser|Work |
the issue is the scenarios when you tweak it |
| # |
Jul 17th 2009, 12:53 |
ProLoser|Work |
it's just a small bundle of files already setup for you |
| # |
Jul 17th 2009, 12:53 |
ProLoser|Work |
and you can continue to manually specify allow/deny as you normally do |
| # |
Jul 17th 2009, 12:53 |
ProLoser|Work |
what if you just load the plugin and on initilization it loads auth site-wide |
| # |
Jul 17th 2009, 12:52 |
ProLoser|Work |
i just was thinking that auth is the one thing i setup almost identical on every single environment, except i've been assuming i have to build it into the app due to it's nature, authorization |
| # |
Jul 17th 2009, 12:52 |
ProLoser|Work |
meh, it's pretty much your users' mvc and acos/aros management |
| # |
Jul 17th 2009, 12:51 |
techno-geek |
how would that work? |
| # |
Jul 17th 2009, 12:51 |
ProLoser|Work |
i was just pondering the pros and cons of bundling the setupd of auth/acl in a plugin |
| # |
Jul 17th 2009, 12:50 |
ProLoser|Work |
that doesn't install acl, it only administrates |
| # |
Jul 17th 2009, 12:50 |
ProLoser|Work |
no no |
| # |
Jul 17th 2009, 12:50 |
techno-geek |
http://bakery.cakephp.org/articles/view/acl-management-plugin |
| # |
Jul 17th 2009, 12:50 |
ProLoser|Work |
since in conjunction with acl, i figure maintance at that point can be database administrated, and thus, can reside out of hardcode |
| # |
Jul 17th 2009, 12:50 |
techno-geek |
I think mariano_iglesias and AD7six both have done this before |
| # |
Jul 17th 2009, 12:49 |
ProLoser|Work |
it's mostly an idea i was thinking for internal development |
| # |
Jul 17th 2009, 12:49 |
ProLoser|Work |
so that you don't have to set it up on every following application |
| # |
Jul 17th 2009, 12:49 |
ProLoser|Work |
it isn't a custom component |
| # |
Jul 17th 2009, 12:49 |
ProLoser|Work |
all it does is setup auth/acl for you |
| # |
Jul 17th 2009, 12:49 |
techno-geek |
plugin |
| # |
Jul 17th 2009, 12:49 |
techno-geek |
yeah |