backend/frontend separation in laravel

Question

I come from a Codeigniter background. At the moment I am building a CMS in Laravel.

What I would like to know is how can I separate the backend and frontend in Laravel?

In Codeigniter i use to make two controller Admin_Controller and Front_Controller.

Article extends Admin_Controller
Article extends Front_Controller

and the file structure looked like this

controller
--admin
---user
---blog
---news
--user 
--blog
--news

for admin controller I make separate folder and front end controller remain in root of controller folder.

Should I use the same logic in Laravel or is there a better way to do it?

With Laravel the 'how do I architect'-type questions are very much up to you. I think the system you proposed, that you already know and use, is perfectly fine. — alexrussell
– alexrussell, Commented Feb 19, 2014 at 14:00
Your question isn't really about separating front and back ends, but about how to organize your files. Choose whatever file structure is easiest to work with. Laravel doesn't care which files are in which folders so long as they can be properly autoloaded. — Dave
– Dave, Commented Feb 19, 2014 at 14:58

Antonio Carlos Ribeiro · Accepted Answer · 2014-02-19 14:18:18Z

35

If you want to create thinks like Taylor Otwell and 'the core' is trying to teach people do things in Laravel, this is a good start:

Your files could be organized as

├── app
│   ├── ZIP
│   │   ├── Controllers
│   │   │   ├── Admin
│   │   │   │   ├── Base.php <--- your base controller
│   │   │   │   ├── User.php
│   │   │   │   ├── Blog.php
│   │   │   │   ├── News.php
│   │   │   ├── Front
│   │   │   │   ├── Base.php <--- your base controller
│   │   │   │   ├── User.php
│   │   │   │   ├── Blog.php
│   │   │   │   ├── News.php

Configure a PSR-0 or PSR-4 (better) to autoload your classes:

"psr-0": {
    "ZIP": "app/"
},

Create namespaces to all tour classes, according to your source tree:

<?php namespace ZIP\Controllers\Admin

class User extends Base {

}


<?php namespace ZIP\Controllers\Front

class Blog extends Base {

}

And create your base controllers

<?php namespace ZIP\Controllers\Admin

use Controller;

class Base extends Controller {

}

answered Feb 19, 2014 at 14:18

Antonio Carlos Ribeiro

87.9k22 gold badges220 silver badges205 bronze badges

Sign up to request clarification or add additional context in comments.

7 Comments

Andreyco Over a year ago

I don't understand why someone downvoted on this. This is perfectly valid answer to this question. App structure here is superb here!

Antonio Carlos Ribeiro Over a year ago

Looks like we have some haters around... :)

Dexture Over a year ago

yup i didnt expect that even this answer an get downvote ,one up from me

haakym Over a year ago

Does the name ZIP have any special meaning here?

Alliswell Over a year ago

@AntonioCarlosRibeiro What about separate users, users cookies and all that stuff?

|

GWed · Accepted Answer · 2014-02-19 14:24:47Z

2

You can certainly do it the two controllers way or if you like even more separation (and a more 'laravel' way), write your front end and backend as separate packages (previously called bundles in Laravel 3).

They basically behave like standalone applications within your main app. They can have their own routes, models, controllers etc. You can also write 'core code' at the main application level which can be shared across the packages.

If you are moving to Laravel as you want to learn a new framework, then you should definitely try and get a handle on packages - very powerful.

If you are being 'made' to move to Laravel, or have some time pressure, just do it as you have normally done. Laravel is flexible and will be fine either way you do it.

For more info, see the docs.

Laravel current version (4 at time of writing) - http://laravel.com/docs/packages

Laravel 3 - http://three.laravel.com/docs/bundles

edited Feb 19, 2014 at 14:24

answered Feb 19, 2014 at 14:10

GWed

15.8k7 gold badges66 silver badges105 bronze badges

1 Comment

kishor10d Over a year ago

@gaz-edge : Is there any separation like frontend and backend like Yii advanced template? I mean any link to already implemented repository on githhub or elsewhere?

Collectives™ on Stack Overflow

backend/frontend separation in laravel

2 Answers 2

7 Comments

1 Comment

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

7 Comments

1 Comment

Your Answer

Sign up or log in

Post as a guest

Related