To create a Laravel controller, use the php artisan make:controller command; the basic usage generates an empty controller for running php artisan make:controller ControllerName; add the --resource parameter to create a resource controller with a CRUD method; use subdirectories such as Admin/AdminController to organize large project structures; other common options include -f overriding the controller of the same name and -m binding model. For example: php artisan make:controller PostController generates a normal controller, while php artisan make:controller CommentController --resource generates a resource controller with index, create, store and other methods, and can be registered in the route through Route::resource('comments', CommentController::class). If the controller needs to be placed in a subdirectory, the namespace must be correctly specified in the route; this command is flexible and efficient, and is suitable for various scenarios from simple pages to complete APIs.

Creating a new controller in Laravel is straightforward, and the php artisan make:controller command makes it even easier. Here's how to do it right.

Basic Usage of php artisan make:controller

To create a new controller, open your terminal and run:

 php artisan make:controller ControllerName

This will generate a new controller file in the app/Http/Controllers directory. By default, Laravel assumes you're creating a plain controller — one that doesn't include any predefined methods like index(), store(), etc.

For example:

 php artisan make:controller PostController

That creates PostController.php with just an empty class.

Creating a Resource Controller

If you want a controller with all the standard resource methods (like index, create, store, show, edit, update, destroy), add the --resource flag:

 php artisan make:controller CommentController --resource

This gives you a controller pre-filled with all the common CRUD-related methods. It's especially useful when working with RESTful routes.

You can also use this in your routes/web.php file like so:

 Route::resource('comments', CommentController::class);

Which automatically maps each method to the appropriate HTTP verb and URL.

Placing Controllers in Subdirectories

As your app grows, organizing controllers into subfolders helps keep things tidy. Let's say you want an admin section — you can do:

 php artisan make:controller Admin/AdminController

This will place the controller inside app/Http/Controllers/Admin/ . Just make sure to include the namespace when referencing it in routes.

In web.php , it would look like this:

 use App\Http\Controllers\Admin\AdminController;

Route::get('/admin', [AdminController::class, 'index']);

Other Useful Options

• -r or --resource
  As mentioned above, creates a controller with full CRUD methods.

• -f or --force
  If a controller already exists with the same name, this option overwrites it.

• -m or --model
  Ties the controller to a specific model. For example:

   php artisan make:controller ProductController --model=Product

  This won't change much in the controller itself unless used with other flags like --api , but it helps document intent.

  ---

  And that's about it. Using php artisan make:controller is fast and flexible once you know which options to use. Whether you're building a simple page or a full resource-based API, Laravel's got your back.

  The above is the detailed content of How do I create a new controller in Laravel? (php artisan make:controller). For more information, please follow other related articles on the PHP Chinese website!