Admin and Guest index same information in database

Best Answer

Level 58

It's a common scenario to have different types of users interact with the same data in different ways. In your case, you have an admin who needs to perform CRUD operations on events, and guests who only need to view the list of events. Here's a solution that follows best practices and leverages Laravel's features to handle this elegantly.

You can indeed use the same Event model for both the admin and the guests. However, it's a good idea to separate the controllers to handle the different permissions and actions that each type of user can perform.

Here's how you can structure your controllers and routes:

Create an EventController for the guest actions, which will only include the index method (or show if you want to display individual events).

// app/Http/Controllers/EventController.php

namespace App\Http\Controllers;

use App\Models\Event;

class EventController extends Controller
{
    public function index()
    {
        $events = Event::all();
        return view('events.index', compact('events'));
    }
}

Create an AdminEventController for the admin actions, which will include methods for creating, storing, editing, updating, and deleting events.

// app/Http/Controllers/AdminEventController.php

namespace App\Http\Controllers\Admin;

use App\Http\Controllers\Controller;
use App\Models\Event;
use Illuminate\Http\Request;

class AdminEventController extends Controller
{
    public function index()
    {
        $events = Event::all();
        return view('admin.events.index', compact('events'));
    }

    public function create()
    {
        return view('admin.events.create');
    }

    public function store(Request $request)
    {
        // Validate and store the event
    }

    public function edit(Event $event)
    {
        return view('admin.events.edit', compact('event'));
    }

    public function update(Request $request, Event $event)
    {
        // Validate and update the event
    }

    public function destroy(Event $event)
    {
        $event->delete();
        return redirect()->route('admin.events.index');
    }
}

Define your routes in web.php, using route groups to organize them and middleware to protect the admin routes.

// routes/web.php

use App\Http\Controllers\EventController;
use App\Http\Controllers\Admin\AdminEventController;

// Guest routes
Route::get('/events', [EventController::class, 'index'])->name('events.index');

// Admin routes
Route::prefix('admin')->name('admin.')->middleware('auth')->group(function () {
    Route::resource('events', AdminEventController::class);
});

In this setup, you'll need to ensure that your auth middleware is set up to only allow the admin user to access the admin routes. You can do this by using gates or policies to define authorization logic.

For unit testing, you can create separate tests for the EventController and AdminEventController. Ensure that you test both the successful access and the unauthorized access scenarios.

This approach keeps your controllers focused and adheres to the Single Responsibility Principle. It also makes your code easier to maintain and understand.