Support the ongoing development of Laravel.io →
Configuration Authentication Security
Last updated 8 months ago.
0

Jakobud said:

The subdomain approach requires a separate Laravel installation.

you could actually use subdomain routing to use a single laravel project for both frontend and backend. http://laravel.com/docs/routing#sub-domain-routing

i think it's just a matter of preferences, i use both of them for different scenario.

Last updated 8 months ago.
0

i have the same challenge...this is what i am doing...not sure if this is best practice :(

Route::group(array('domain' => 'admin.mydomain.com'), function()
{
    Route::get('/', function() {
        return 'Hello admin!';
    });
});

Route::group(array('domain' => 'customer.mydomain.com'), function()
{
    Route::get('/', function() {
        return 'Hello Customer!';
    });
});
Last updated 8 months ago.
0

Sign in to participate in this thread!

LoadForge

Your banner here too?

Jakobud jakobud Joined 31 Jan 2014

Moderators

We'd like to thank these amazing companies for supporting us

Your logo here?

Laravel.io

The Laravel portal for problem solving, knowledge sharing and community building.

© 2023 Laravel.io - All rights reserved.