Provide a way of customizing/disabling the default routes

[MarkIvanowich]

A mirror of Jetstream's laravel/jetstream#67

Enables a user to call Fortify::ignoreRoutes() in a provider's register method to disable the default routes and provide their own.
Also enables publishing of default routes into userland.

Relevant are #9, #10

[MarkIvanowich]

The Jetstream's version was merged while this one was closed? I figured since these two packages went hand-in-hand that they should be consistent in functionality.

I want to move my application login pages away from common endpoints that are typically brute forced. (/login, /wp-login, etc) Adding a prefix to the login route adds just enough additional security through obscurity.

[rodrigopedra]

Thanks @taylorotwell

Much appreciated! =)

[anhofmann]

Why was the PR only partially merged?
Publishing the routes did not make it into the master branch, or do I see it wrong?
If I want to adjust my routes, do I copy them manually from fortify into my routes, or what is the right way? I am relatively new to laravel and am trying to build customized login/register routes for different user roles in my app. A single prefix is (sadly) not enough for my App.

[driesvints]

@anhofmann you can just copy/paste them into your own routes.

[nicolailebek]

I copied "vendor/laravel/fortify/routes/routes.php" to "routes/fortify.php".

Then in "App/Providers/FortifyServiceProvider.php":

public function boot() {
        $this->configureRoutes();
        ...
}

/**
 * Configure the routes offered by the application.
 *
 * @return void
 */
protected function configureRoutes()
{
    if (Fortify::$registersRoutes) {
        Route::group([
            'namespace' => 'Laravel\Fortify\Http\Controllers',
            'domain' => config('fortify.domain', null),
            'prefix' => config('fortify.path'),
        ], function () {
            $this->loadRoutesFrom(base_path('routes/fortify.php'));
        });
    }
}

Did the same with jetstream's routes