Creating, reading, updating, and deleting resources is used in pretty much every application. Laravel helps make the process easy using resource controllers. Resource Controllers can make life much easier and takes advantage of some cool Laravel routing techniques. Today, we'll go through the steps necessary to get a fully functioning CRUD application using resource controllers.

For this tutorial, we will go through the process of having an admin panel to create, read, update, and delete (CRUD) a resource. Let's use nerds as our example. We will also make use of Eloquent ORM.

This tutorial will walk us through: * Setting up the database and models * Creating the resource controller and its routes * Creating the necessary views * Explaining each method in a resource controller

To get started, we will need the controller, the routes, and the view files.

Getting our Database Ready

Nerd Migration

(This sounds like a bunch of nerds moving south for the winter). We need to set up a quick database so we can do all of our CRUD functionality. In the command line in the root directory of our Laravel application, let's create a migration.

php artisan migrate:make create_nerds_table --table=nerds --create This will create our nerd migration in app/database/migrations . Open up that file and let's add name, email, and nerd_level fields.

// app/database/migrations/####_##_##_######_create_nerds_table.php <?php use IlluminateDatabaseSchemaBlueprint; use IlluminateDatabaseMigrationsMigration; class CreateNerdsTable extends Migration { /** * Run the migrations. * * @return void */ public function up() { Schema::create('nerds', function(Blueprint $table) { $table->increments('id'); $table->string('name', 255); $table->string('email', 255); $table->integer('nerd_level'); $table->timestamps(); }); } /** * Reverse the migrations. * * @return void */ public function down() { Schema::drop('nerds'); } }

Now from the command line again, let's run this migration. Make sure your database settings are good in app/config/database.php and then run:

php artisan migrate Our database now has a nerds table to house all of the nerds we CRUD (create, read, update, and delete). Read more about migrations at the Laravel docs.

Eloquent Model for the Nerds

Now that we have our database, let's create a simple Eloquent model so that we can access the nerds in our database easily. You can read about Eloquent ORM and see how you can use it in your own applications.

Upgrade Your JS Go from vanilla JavaScript 👉 React

Watch for FREE

In the app/models folder, let's create a Nerd.php model.

// app/models/Nerd.php <?php class Nerd extends Eloquent { }

That's it! Eloquent can handle the rest. By default, this model will link to our nerds table and and we can access it later in our controllers.

Creating the Controller

From the official Laravel docs, on resource controllers, you can generate a resource controller using the artisan tool.

Let's go ahead and do that. This is the easy part. From the command line in the root directory of your Laravel project, type:

php artisan controller:make NerdController This will create our resource controller with all the methods we need.

// app/controllers/NerdController.php <?php class NerdController extends BaseController { /** * Display a listing of the resource. * * @return Response */ public function index() { // } /** * Show the form for creating a new resource. * * @return Response */ public function create() { // } /** * Store a newly created resource in storage. * * @return Response */ public function store() { // } /** * Display the specified resource. * * @param int $id * @return Response */ public function show($id) { // } /** * Show the form for editing the specified resource. * * @param int $id * @return Response */ public function edit($id) { // } /** * Update the specified resource in storage. * * @param int $id * @return Response */ public function update($id) { // } /** * Remove the specified resource from storage. * * @param int $id * @return Response */ public function destroy($id) { // } }

Setting Up the Routes

Now that we have generated our controller, let's make sure our application has the routes necessary to use it. This is the other easy part (they actually might all be easy parts). In your routes.php file, add this line:

// app/routes.php <?php Route::resource('nerds', 'NerdController');

This will automatically assign many actions to that resource controller. Now if you, go to your browser and view your application at example.com/nerds , it will correspond to the proper method in your NerdController.

Actions Handled By the Controller

HTTP Verb Path (URL) Action (Method) Route Name GET /nerds index nerds.index GET /nerds/create create nerds.create POST /nerds store nerds.store GET /nerds/{id} show nerds.show GET /nerds/{id}/edit edit nerds.edit PUT/PATCH /nerds/{id} update nerds.update DELETE /nerds/{id} destroy nerds.destroy

Tip: From the command line, you can run php artisan routes to see all the routes associated with your application.

The Views

Since only four of our routes are GET routes, we only need four views. In our app/views folder, let's make those views now.

app views nerds index.blade.php create.blade.php show.blade.php edit.blade.php



Making It All Work Together

Now we have our migrations, database, and models, our controller and routes, and our views. Let's make all these things work together to build our application. We are going to go through the methods created in the resource controller one by one and make it all work.

Showing All Resources nerds.index

Description URL Controller Function View File Default page for showing all the nerds. GET example.com/nerds index() app/views/nerds/index.blade.php

Controller Function index()

In this function, we will get all the nerds and pass them to the view.

// app/controllers/NerdController.php <?php ... /** * Display a listing of the resource. * * @return Response */ public function index() { // get all the nerds $nerds = Nerd::all(); // load the view and pass the nerds return View::make('nerds.index') ->with('nerds', $nerds); } ...

The View app/views/nerds/index.blade.php

Now let's create our view to loop over the nerds and display them in a table. We like using Twitter Bootstrap for our sites, so the table will use those classes.

<!-- app/views/nerds/index.blade.php --> <!DOCTYPE html> <html> <head> <title>Look! I'm CRUDding</title> <link rel="stylesheet" href="//netdna.bootstrapcdn.com/bootstrap/3.0.0/css/bootstrap.min.css"> </head> <body> <div class="container"> <nav class="navbar navbar-inverse"> <div class="navbar-header"> <a class="navbar-brand" href="{{ URL::to('nerds') }}">Nerd Alert</a> </div> <ul class="nav navbar-nav"> <li><a href="{{ URL::to('nerds') }}">View All Nerds</a></li> <li><a href="{{ URL::to('nerds/create') }}">Create a Nerd</a> </ul> </nav> <h1>All the Nerds</h1> <!-- will be used to show any messages --> @if (Session::has('message')) <div class="alert alert-info">{{ Session::get('message') }}</div> @endif <table class="table table-striped table-bordered"> <thead> <tr> <td>ID</td> <td>Name</td> <td>Email</td> <td>Nerd Level</td> <td>Actions</td> </tr> </thead> <tbody> @foreach($nerds as $key => $value) <tr> <td>{{ $value->id }}</td> <td>{{ $value->name }}</td> <td>{{ $value->email }}</td> <td>{{ $value->nerd_level }}</td> <!-- we will also add show, edit, and delete buttons --> <td> <!-- delete the nerd (uses the destroy method DESTROY /nerds/{id} --> <!-- we will add this later since its a little more complicated than the other two buttons --> <!-- show the nerd (uses the show method found at GET /nerds/{id} --> <a class="btn btn-small btn-success" href="{{ URL::to('nerds/' . $value->id) }}">Show this Nerd</a> <!-- edit this nerd (uses the edit method found at GET /nerds/{id}/edit --> <a class="btn btn-small btn-info" href="{{ URL::to('nerds/' . $value->id . '/edit') }}">Edit this Nerd</a> </td> </tr> @endforeach </tbody> </table> </div> </body> </html>

We can now show all of our nerds on a page. There won't be any that show up currently since we haven't created any or seeded our database with nerds. Let's move on to the form to create a nerd.

Creating a New Resource nerds.create

Description URL Controller Function View File Show the form to create a new nerd. GET example.com/nerds/create create() app/views/nerds/create.blade.php

Controller Function create()

In this function, we will show the form for creating a new nerd. This form will be processed by the store() method.

// app/controllers/NerdController.php <?php ... /** * Show the form for creating a new resource. * * @return Response */ public function create() { // load the create form (app/views/nerds/create.blade.php) return View::make('nerds.create'); } ...

The View app/views/nerds/create.blade.php

<!-- app/views/nerds/create.blade.php --> <!DOCTYPE html> <html> <head> <title>Look! I'm CRUDding</title> <link rel="stylesheet" href="//netdna.bootstrapcdn.com/bootstrap/3.0.0/css/bootstrap.min.css"> </head> <body> <div class="container"> <nav class="navbar navbar-inverse"> <div class="navbar-header"> <a class="navbar-brand" href="{{ URL::to('nerds') }}">Nerd Alert</a> </div> <ul class="nav navbar-nav"> <li><a href="{{ URL::to('nerds') }}">View All Nerds</a></li> <li><a href="{{ URL::to('nerds/create') }}">Create a Nerd</a> </ul> </nav> <h1>Create a Nerd</h1> <!-- if there are creation errors, they will show here --> {{ HTML::ul($errors->all()) }} {{ Form::open(array('url' => 'nerds')) }} <div class="form-group"> {{ Form::label('name', 'Name') }} {{ Form::text('name', Input::old('name'), array('class' => 'form-control')) }} </div> <div class="form-group"> {{ Form::label('email', 'Email') }} {{ Form::email('email', Input::old('email'), array('class' => 'form-control')) }} </div> <div class="form-group"> {{ Form::label('nerd_level', 'Nerd Level') }} {{ Form::select('nerd_level', array('0' => 'Select a Level', '1' => 'Sees Sunlight', '2' => 'Foosball Fanatic', '3' => 'Basement Dweller'), Input::old('nerd_level'), array('class' => 'form-control')) }} </div> {{ Form::submit('Create the Nerd!', array('class' => 'btn btn-primary')) }} {{ Form::close() }} </div> </body> </html>

We will add the errors section above to show validation errors when we try to store() the resource.

Tip: When using {{ Form::open() }} , Laravel will automatically create a hidden input field with a token to protect from cross-site request forgeries. Read more at the When using, Laravel will automatically create a hidden input field with a token to protect from cross-site request forgeries. Read more at the Laravel docs

We now have the form, but we need to have it do something when it the submit button gets pressed. We set this form's action to be a POST to example.com/nerds. The resource controller will handle this and automatically route the request to the store() method. Let's handle that now.

Storing a Resource store()

Description URL Controller Function View File Process the create form submit and save the nerd to the database. POST example.com/nerds store() NONE

As you can see from the form action and the URL, you don't have to pass anything extra into the URL to store a nerd. Since this form is sent using the POST method, the form inputs will be the data used to store the resource.

To process the form, we'll want to validate the inputs, send back error messages if they exist, authenticate against the database, and store the resource if all is good. Let's dive in.

Controller Function store()

// app/controllers/NerdController.php <?php ... /** * Store a newly created resource in storage. * * @return Response */ public function store() { // validate // read more on validation at http://laravel.com/docs/validation $rules = array( 'name' => 'required', 'email' => 'required|email', 'nerd_level' => 'required|numeric' ); $validator = Validator::make(Input::all(), $rules); // process the login if ($validator->fails()) { return Redirect::to('nerds/create') ->withErrors($validator) ->withInput(Input::except('password')); } else { // store $nerd = new Nerd; $nerd->name = Input::get('name'); $nerd->email = Input::get('email'); $nerd->nerd_level = Input::get('nerd_level'); $nerd->save(); // redirect Session::flash('message', 'Successfully created nerd!'); return Redirect::to('nerds'); } } ...

If there are errors processing the form, we will redirect them back to the create form with those errors. We will add them in so the user can understand what went wrong. They will show up in the errors section we setup earlier.

Now you should be able to create a nerd and have them show up on the main page! Navigate to example.com/nerds and there they are. All that's left is showing a single nerd, updating, and deleting.

Showing a Resource show()

Description URL Controller Function View File Show one of the nerds. GET example.com/nerds/{id} show() app/views/nerds/show.blade.php

Controller Function show()

// app/controllers/NerdController.php <?php ... /** * Display the specified resource. * * @param int $id * @return Response */ public function show($id) { // get the nerd $nerd = Nerd::find($id); // show the view and pass the nerd to it return View::make('nerds.show') ->with('nerd', $nerd); } ...

The View app/views/nerds/show.blade.php

<!-- app/views/nerds/show.blade.php --> <!DOCTYPE html> <html> <head> <title>Look! I'm CRUDding</title> <link rel="stylesheet" href="//netdna.bootstrapcdn.com/bootstrap/3.0.0/css/bootstrap.min.css"> </head> <body> <div class="container"> <nav class="navbar navbar-inverse"> <div class="navbar-header"> <a class="navbar-brand" href="{{ URL::to('nerds') }}">Nerd Alert</a> </div> <ul class="nav navbar-nav"> <li><a href="{{ URL::to('nerds') }}">View All Nerds</a></li> <li><a href="{{ URL::to('nerds/create') }}">Create a Nerd</a> </ul> </nav> <h1>Showing {{ $nerd->name }}</h1> <div class="jumbotron text-center"> <h2>{{ $nerd->name }}</h2> <p> <strong>Email:</strong> {{ $nerd->email }}<br> <strong>Level:</strong> {{ $nerd->nerd_level }} </p> </div> </div> </body> </html>

Editing a Resource edit()

Description URL Controller Function View File Pull a nerd from the database and allow editing. GET example.com/nerds/{id}/edit edit() app/views/nerds/edit.blade.php

To edit a nerd, we need to pull them from the database, show the creation form, but populate it with the selected nerd's info. To make life easier, we will use form model binding. This allows us to pull info from a model and bind it to the input fields in a form. Just makes it easier to populate our edit form and you can imagine that when these forms start getting rather large this will make life much easier.

Controller Function edit()

// app/controllers/NerdController.php <?php ... /** * Show the form for editing the specified resource. * * @param int $id * @return Response */ public function edit($id) { // get the nerd $nerd = Nerd::find($id); // show the edit form and pass the nerd return View::make('nerds.edit') ->with('nerd', $nerd); } ...

The View app/views/nerds/edit.blade.php

<!-- app/views/nerds/edit.blade.php --> <!DOCTYPE html> <html> <head> <title>Look! I'm CRUDding</title> <link rel="stylesheet" href="//netdna.bootstrapcdn.com/bootstrap/3.0.0/css/bootstrap.min.css"> </head> <body> <div class="container"> <nav class="navbar navbar-inverse"> <div class="navbar-header"> <a class="navbar-brand" href="{{ URL::to('nerds') }}">Nerd Alert</a> </div> <ul class="nav navbar-nav"> <li><a href="{{ URL::to('nerds') }}">View All Nerds</a></li> <li><a href="{{ URL::to('nerds/create') }}">Create a Nerd</a> </ul> </nav> <h1>Edit {{ $nerd->name }}</h1> <!-- if there are creation errors, they will show here --> {{ HTML::ul($errors->all()) }} {{ Form::model($nerd, array('route' => array('nerds.update', $nerd->id), 'method' => 'PUT')) }} <div class="form-group"> {{ Form::label('name', 'Name') }} {{ Form::text('name', null, array('class' => 'form-control')) }} </div> <div class="form-group"> {{ Form::label('email', 'Email') }} {{ Form::email('email', null, array('class' => 'form-control')) }} </div> <div class="form-group"> {{ Form::label('nerd_level', 'Nerd Level') }} {{ Form::select('nerd_level', array('0' => 'Select a Level', '1' => 'Sees Sunlight', '2' => 'Foosball Fanatic', '3' => 'Basement Dweller'), null, array('class' => 'form-control')) }} </div> {{ Form::submit('Edit the Nerd!', array('class' => 'btn btn-primary')) }} {{ Form::close() }} </div> </body> </html>

Note that we have to pass a method of PUT so that Laravel knows how to route to the controller correctly.

Updating a Resource update()

Description URL Controller Function View File Process the create form submit and save the nerd to the database. PUT example.com/nerds update() NONE

This controller method will process the edit form. It is very similar to store() . We will validate, update, and redirect.

Controller Function update()

// app/controllers/NerdController.php <?php ... /** * Update the specified resource in storage. * * @param int $id * @return Response */ public function update($id) { // validate // read more on validation at http://laravel.com/docs/validation $rules = array( 'name' => 'required', 'email' => 'required|email', 'nerd_level' => 'required|numeric' ); $validator = Validator::make(Input::all(), $rules); // process the login if ($validator->fails()) { return Redirect::to('nerds/' . $id . '/edit') ->withErrors($validator) ->withInput(Input::except('password')); } else { // store $nerd = Nerd::find($id); $nerd->name = Input::get('name'); $nerd->email = Input::get('email'); $nerd->nerd_level = Input::get('nerd_level'); $nerd->save(); // redirect Session::flash('message', 'Successfully updated nerd!'); return Redirect::to('nerds'); } } ...

Deleting a Resource destroy()

Description URL Controller Function View File Process the create form submit and save the nerd to the database. DELETE example.com/nerds/{id} destroy() NONE

The workflow for this is that a user would go to view all the nerds, see a delete button, click it to delete. Since we never created a delete button in our app/views/nerds/index.blade.php , we will create that now. We will also add a notification section to show a success message.

We have to send the request to our application using the DELETE HTTP verb, so we will create a form to do that since a button won't do.

Alert: The DELETE HTTP verb is used when accessing the nerds.destroy route. Since you can't just create a button or form with the method DELETE, we will have to spoof it by creating a hidden input field in our delete form.

The View app/views/nerds/index.blade.php

<!-- app/views/nerds/index.blade.php --> ... @foreach($nerds as $key => $value) <tr> <td>{{ $value->id }}</td> <td>{{ $value->name }}</td> <td>{{ $value->email }}</td> <td>{{ $value->nerd_level }}</td> <!-- we will also add show, edit, and delete buttons --> <td> <!-- delete the nerd (uses the destroy method DESTROY /nerds/{id} --> <!-- we will add this later since its a little more complicated than the other two buttons --> {{ Form::open(array('url' => 'nerds/' . $value->id, 'class' => 'pull-right')) }} {{ Form::hidden('_method', 'DELETE') }} {{ Form::submit('Delete this Nerd', array('class' => 'btn btn-warning')) }} {{ Form::close() }} <!-- show the nerd (uses the show method found at GET /nerds/{id} --> <a class="btn btn-small btn-success" href="{{ URL::to('nerds/' . $value->id) }}">Show this Nerd</a> <!-- edit this nerd (uses the edit method found at GET /nerds/{id}/edit --> <a class="btn btn-small btn-info" href="{{ URL::to('nerds/' . $value->id . '/edit') }}">Edit this Nerd</a> </td> </tr> @endforeach ...

Now when we click that form submit button, Laravel will use the nerds.destroy route and we can process that in our controller.

Controller Function destroy()

// app/controllers/NerdController.php <?php ... /** * Remove the specified resource from storage. * * @param int $id * @return Response */ public function destroy($id) { // delete $nerd = Nerd::find($id); $nerd->delete(); // redirect Session::flash('message', 'Successfully deleted the nerd!'); return Redirect::to('nerds'); } ...

Conclusion

That's everything! Hopefully we covered enough so that you can understand how resource controllers can be used in all sorts of scenarios. Just create the controller, create the single line in the routes file, and you have the foundation for doing CRUD.

As always, let us know if you have any questions or comments. We'll be expanding more on Laravel in the coming articles so if there's anything specific, throw it in the comments or email us.

Further Reading: For more Laravel, check out our Simple Laravel Series.

Like this article? Follow @chrisoncode on Twitter