[2.1.0] Middleware changes (#30)

* middleware changes

* Update tenant-routes.blade.md (#32)

* Update tenant-routes.blade.md

* Update docs/source/v2/tenant-routes.blade.md

Co-Authored-By: Samuel Štancl <samuel.stancl@gmail.com>

docs/source/v2/tenant-routes.blade.md

@@ -7,31 +7,43 @@ section: content
 
 # Tenant Routes {#tenant-routes}
 
-Routes within `routes/tenant.php` will have the `web` middleware group and the `IntializeTenancy` middleware automatically applied on them. 
+Routes within `routes/tenant.php` will have the `web` and `tenancy` middleware groups automatically applied on them. 
-
-The `IntializeTenancy` middleware attempts to identify the tenant based on the current hostname. Once the tenant is identified, the database connection, cache, filesystem root paths and, optionally, Redis connection, will be switched.
 
 Just like `routes/web.php`, these routes use the `App\Http\Controllers` namespace (you can [configure this]({{ $page->link('configuration#tenant-route-namespace') }}))
 
 > If a tenant cannot be identified, an exception will be thrown. If you want to change this behavior (to a redirect, for example) read the [Middleware Configuration]({{ $page->link('middleware-configuration') }}) page.
 
-## Exempt routes {#exempt-routes}
+## Middleware {#middleware}
 
-Routes outside the `routes/tenant.php` file will not have the tenancy middleware automatically applied on them. You can apply this middleware manually, though.
+The package automatically adds the `InitializeTenancy` middleware to the global middleware stack. This middleware checks if the current domain is not part of `tenancy.exempt_domains`. If not, it attempts to identify the tenant based on the current hostname. Once the tenant is identified, the database connection, cache, filesystem root paths and, optionally, Redis connection, will be switched.
 
-If you want certain routes (perhaps API routes) to be multi-tenant, wrap them in a Route group with this middleware:
+After the *global* middleware is executed, the controllers are constructed. 
+
+After that, the *route* middleware is executed.
+
+All route groups in your application should have the `\Stancl\Tenancy\Middleware\PreventAccessFromTenantDomains` middleware applied on them, to prevent access from tenant domains to central routes and vice versa. See below for more detail about the `PreventAccessFromTenantDomains` middleware.
+
+All tenant routes in your application should have the `tenancy` middleware group applied on them.
+
+The `tenancy` middleware group marks the route as a tenant route. That middleware functions as a "flag" for the `PreventAccessFromTenantDomains`, telling it that the route is a tenant route, since the middleware has no other way of distingushing central from tenant routes.
+
+In previous versions, the `InitializeTenancy` middleware was applied only on tenant routes. However, that lead to tenancy not being initialized in controller constructors, which could cause bugs. So from 2.1.0 on, tenancy is initialized on all routes on non-exempt domains, and if the route is not tenant, the request gets aborted by the `PreventAccessFromTenantDomains` once Laravel reaches the route middleware step.
+
+## Central routes {#central-routes}
+
+Routes in files other than `routes/tenant.php` will not have the `tenancy` middleware automatically applied on them, so they will be central routes. If you want these routes to be tenant routes, you can apply the `tenancy` middleware manually, as described in custom route groups below.
 
 ## API routes / custom route groups {#custom-groups}
 
-```php
+If you want certain routes (perhaps API routes) to be multi-tenant, wrap them in a Route group with this middleware:
-use Stancl\Tenancy\Middleware\InitializeTenancy;
 
-Route::middleware(InitializeTenancy::class)->group(function () {
+```php
+Route::middleware('tenancy')->group(function () {
     // Route::get('/', 'HelloWorld');
 });
 ```
 
-and apply the `Stancl\Tenancy\Middleware\PreventAccessFromTenantDomains` middleware on the *entire* group:
+and make sure the `Stancl\Tenancy\Middleware\PreventAccessFromTenantDomains` middleware is applied on the *entire* group:
 
 ```php
 // app/Http/Kernel.php
@@ -52,4 +64,4 @@ Suggestion: Since you probably want cleaner URLs on your non-tenant part of the
 
 The `Stancl\Tenancy\Middleware\PreventAccessFromTenantDomains` middleware prevents access to non-tenant routes from tenant domains by returning a redirect to the tenant app's home page ([`tenancy.home_url`]({{ $page->link('configuration#home-url') }})). Conversely, it returns a 404 when a user attempts to visit a tenant route on a web (exempt) domain.
 
-The `tenancy:install` command applies this middleware to the `web` group. If you want apply it for another route group, add this middleware manually to that group. You can do this in `app/Http/Kernel.php`.
+The `tenancy:install` command applies this middleware to the `web` and `api` groups. To apply it for another route group, add this middleware manually to that group. You can do this in `app/Http/Kernel.php`.