Separate Dnsmasq configuration for each site/proxy

[nforst]

Would it be possible to create a separate configuration for each page instead of a single dnsmasq configuration? This would have the advantage of allowing you to specify a specific TLD, e.g., “.dev,” and your own domain, e.g., “test.dev,” which would then be forwarded to valet, but it would not overwrite other domains that also end with “.dev.”

I currently have the problem that I want to integrate Google's OAuth and test it locally, but I need a valid TLD to do so. This means I cannot use “.test”.

[adrum]

@nforst Random comment, I ran into this exact issue. Locally, I spun up a simple a simple OAuth Server with Laravel Passport, and then used socialite to connect it my app.

As long as you use socialite, it should more or less be the same, and you can just swap the Socialite provider. Here's a Socialite driver for Passport.

Here's an example Google callback controller I've used:

<?php

namespace App\Http\Controllers\Auth;

use Str;
use Auth;
use App\Models\User;
use Laravel\Socialite\Facades\Socialite;


class GoogleCallbackController
{
    public function __invoke()
    {
        // @phpstan-ignore-next-line
        $social = Socialite::driver('google')->stateless()->user();

        /** @var \App\Models\User $user */
        $user = User::where('email', $social->getEmail())->first() ?? new User([
            'name' => $social->getName(),
            'email' => $social->getEmail(),
            'password' => '',
            // 'avatar' => $social->getAvatar(),
            // 'nickname' => $user->getNickname(),
            // 'google_id' => $user->getId(),
        ]);

        $user->save();

        Auth::loginUsingId($user->id);

        return redirect()->intended();
    }
}

A more robust match would use the Google ID instead of email, but it's good enough for simple use cases.

https://laravel.com/docs/12.x/socialite#authentication-and-storage