[eluser]jleequeen[/eluser]
Hi Everyone,
I was wondering how anyone handles the administrative portions of their apps using CI. Especially if some of your models and libraries could be shared between the front-end (public) and back-end (admin) apps. Is it worth some redundancy to create two separate applications for each? Any ideas or suggestions would be great.
[eluser]Jamie Rumbelow[/eluser]
I generally don't bother with creating different apps - I find it easier to just create an "admin" folder in my controllers.
But that's just me...
[eluser]Dam1an[/eluser]
I also just put all the admins tuff in a seperate directory, just makes life easier.
Although in general (not sure if its an issue with frameworks though, as they use the index.php as a front controller, and don't allow direct access) its poor security to name the admin folder 'admin' as this is the first thing a potential hacker will look for
[eluser]jleequeen[/eluser]
@Jemgames
Do you use URI Routing to make URL's shorter?
@Dam1an
Do you have separate models for your admin/public functions?
@Anyone
My application basically has 3 types of user. I have a public user that can see the site and doesn't have a login. The other two types of users need a login. One is someone who registers for the site, and the other is a administrative user who manages the site. I'm basically trying to decide which way to go. Either create basically three separate apps, although I like the idea of organizing my controllers into sub-directories for each type of user...but then I also have some controllers/views that need to be shared between the registered user and administrative user. It seems that duplicating the controllers for each type of user would be redundant in that scenario.