I have my routes set up as follows:
<?php
Route::group([
'domain' => '{username}.u.'.env('APP_DOMAIN'),
], function () {
Route::get('/', 'FrontendController@site');
});
Route::group([
'domain' => env('APP_DOMAIN'),
], function () {
// Regular site routes
});
Route::group([
'domain' => '{domain}',
], function () {
Route::get('/', 'FrontendController@domain');
});
What I'm trying to achieve is allowing users to have their own sites, e.g. hello.u.domain.com, and for those sites to also be served through a custom domain that is CNAME'd to their subdomain. Using the routing above, the wildcard subdomain works perfectly fine. However the custom domain routing is never hit; whenever a custom domain that is CNAME'd to the subdomain is visited, the regular site routes are used.
APP_DOMAIN
is not the same as the custom domain, and I have $router->pattern('domain', '[a-z0-9.]+');
in my RouteServiceProvider.php
to allow {domain}
as a full domain name.
This has been answered, at least partially, by myself here: Creating a route in Laravel using subdomain and domain wildcards
In short, you cannot make the whole domain a parameter in the routes file. Instead, you assign a middleware that will check the current domain, match it against your pre-defined list of allowed user domains and based on that - take some decision (eg. what method to hit in your controller).
Consider:
And then in your FrontendController:
You can't have a wildcard on the whole domain, at least not with one wildcard. What you can do is the following:
Just make sure that this group is the last one in your routes file, it will act as a fallback group on domains and will serve the requests that don't match any of the previous domains.
Also I'd recommend using this package, it might be helpful for what you are trying to do.
Unfortunately I did not get an answer to my comment. This answer assumes the problem is that normal default routes are used instead of routes with subdomain.
Example:
A user is visiting sub.website.com but route() returns website.com/blabla instead of sub.website.com/blabla
You can solve this by dynamically create the pattern for domain inside routes.php
By using this method you will create a problem with your route() and controller parameters.
route() problem
When calling the route() function while using this method you will get a missing argument error. The route() function expects you to give the {subdomain}.{domain}.{tld} parameters.
You can solve this by creating your own route function. I named it mdroute() (multi domain route).
Controller problem
The parameters {sub}.{domain}.{tld} are always send to your controller. You can't access other parameters the way you are used to be.
Example:
You can solve this by accessing your parameter through the Request object.