多个子域访问的单个 Laravel 实例

Question

I am completely no-wise to Laravel. But unfortunately, just a week ago, I got a project build upon Laravel. I set that up and running on my hosting machine. It's working good. But now I need to setup subdomains and access the same instance of Laravel project.

I struggled and somehow made it. Now my subdomains can access main domain laravel instance.

Here are complete details:

Suppose my main domain with Laravel installation of project is eg example.com . Then created another subdomain as sub.example.com and point it's DocumentRoot directory to my main domain "example.com"

Then I created a new .env file with name of my subdomain as .env.sub.example.com in my main Laravel installation and updated following file bootstrape/app.php with following code so it can read .env file depending on the request coming from which domain and serve accordingly.

/*
|-----------------------------------------------
| Load domain-specific .env file if it exists
|-----------------------------------------------
*/

if(isset($_SERVER['HTTP_HOST']) && !empty($_SERVER['HTTP_HOST'])){

    $domain = $_SERVER['HTTP_HOST'];

    if (isset($domain)) {
        $dotenv = Dotenv\Dotenv::createImmutable(base_path(), '.env.'.$domain);

        try {
            $dotenv->load();
        } catch (\Dotenv\Exception\InvalidPathException $e) {
        // No custom .env file found for this domain
        }
    }
}
// ...

Everything works good but it has problems with sessions and some of my modules installed are conflicting. If someone could point my mistake or tell me what am I missing.

How can I use my single instance of Laravel with Subdomains?

My routes/web.php file contains Routes like this

Route::group(['prefix' => 'settings'], function () {
   Route::post('categories/import', 'Settings\Categories@import')->name('categories.import');
   Route::get('categories/export', 'Settings\Categories@export')->name('categories.export');
   Route::resource('categories', 'Settings\Categories');
});

Answer 1

@Airy, ideally you would want to look into multi-tenancy for your application. It's easier to maintain and you wouldn't have to update the Laravel internals to get it to work and that is my suggestion.

Take a look at some of the Laravel packages that may help you with this:

1. https://tenancyforlaravel.com/
2. https://spatie.be/docs/laravel-multitenancy/v2/introduction
3. https://tenancy.dev/

Hopefully the above helps.