Right now I have two separate directories:

system/admin
system/application

And in ‘public_html’ two files to call them:

public_html/admin/index.php
public_html/index.php

How do you separate your front-end from back-end? Or do you prefer to keep them together?

What I do is create a controller named admin and put my functions like login, logout, addPost, editPost, etc, and use the session class to verify permissions before loading a view.

the way CodeExtinguisher works is by putting everything it uses in a folder outside of system/...it never made sense to me to have the application inside the system folder.

Well there are two options really.

If you will need to use lots of similar data/files between both the admin and frontend, it makes sense to just have the admin in a sub directory and use all the same stuff. I normally do it this way as my sites are often basic “user registration/forum/blog” type sites with a few extras. No need to seperate it.

I keep mine separate by use of admin directly and an Admin and Public Controller. The only different is the Admin controller asks for authentication.

@jTaby: Now that you mentioned it, it makes logical sense to put an application outside system folder, but does it give you any other benefits besides having things “neat”?

It means that you can run several applications with only one system folder, which cuts down on the clutter and makes it really easy to update.

You could also use two applications (as the pyromaniac) suggest, together with Matchbox, and have a module directory in your system folder with resources that are to be shared between the two, and then additional module directories in each application folder with resources exclusive to front/back-end.

Zacharias Knudsen - 05 March 2008 12:37 PM

You could also use two applications (as the pyromaniac) suggest, together with Matchbox, and have a module directory in your system folder with resources that are to be shared between the two, and then additional module directories in each application folder with resources exclusive to front/back-end.

In the case of Matchbox, could you not modify MY_Router to conditionally load a module from application/admin/modules/ when ‘admin’ was included as the first segment in the url? You could probably enable this as a feature via a config setting. The advantage would be sharing common libraries, helpers, and plugins within a single application rather than creating two applications. The disadvantage, especially when a module installer is considered, is dividing module specific code among two module directory system.

In our earlier projects at work, we use the pyromaniac approach but rename a second copy of index.php to admin.php in order to load the two applications.

When I work on my localhost I have this folders:
D:\proyects\proyect1\
-frontend
-backend
-system
-www
—index.php
—admin
—-index.php

D:\proyects\proyect2\
-frontend
-backend
-system
-www
—index.php
—admin
—-index.php
Then in the first index.php I have:
  $system_folder = ”../system”;
  $application_folder = ”../frontend”;

..And in admin/index.php I have:
  $system_folder = ”../../system”;
  $application_folder = ”../../backend”;

This way when I upload my files to the server I put frontend,backend and system outside the public_html and the contents of www goes into public_html

dejitaru, is there a way to share some libraries or models between font end and back end using your method?

Sharing a library is not a problem, just drop it under the system/libraries nut sharing a model could me a problem. The way I do is copying the model in both models folders

this is what i’ve done and worked for me.
just make 2 controllers, admin and public. then make 2 subdirectories in your /views folder (/views/admin and /views/public)

yes of course Psyco, it just about preferences ^_^ I prefer my client go:
http://www.example/admin instead of http://www.example/admin.php

It may sound perhaps silly… but you should meet my clients! they call me twice a week because of the .php at the end