How do I make a custom local domain for Laravel Herd projects?

is it that important, or just a temporary annoyance?

@snapey It's important.

@snapey Thanks.

@bobclewell and @saidguerrero If your using Herd, when you try to change your tld for your local projects or use the command herd tld [ your custom local tld ] you will get a message as such Using a custom TLD is no longer officially supported and may lead to unexpected behavior Do you wish to proceed? [y/N] . Herd recommends that you use the *.test domain or tld for this reason.

Since herd is built on top of Valet, and doesn't modify the existing installation on your system you can do pretty much the same thing above to get a custom tld with Valet. You will need to stop Herd services, restart Valet valet restart and then use the Valet command valet tld [the tld you would like to use ] . Hop in your browser and see the results of your local custom tld *.your-tld

However, right now it seems redundant to have both since they pretty much do the same thing and the tld *.test is a minor inconvenience if you are used to having a custom tld , since you don't have to deal with homebrew and all it's dependencies and setting up composer , node and the laravel/installer.

Additionally, the only thing you may need is a built-in database server. In this case, you can check out DBngin and perhaps this tutorial. I hope this helps and provides more clarification. Take care.

@snapey Thanks for the education on the .test top level domain. The project that I maintain used .local as it's top level development environment domain, but I can see in the Wikipedia reference that is a bad practice, since .local has its own special use case.

en.wikipedia.org/wiki/.local

Or course, .dev would also make more sense to me here than .test, but again that's taken. So, considering the foundation established by the IETF, .test is the best choice here.

Bumping this. It would be great to be able to control the domain for testing purposes, particularly for Laravel/Socialite

Laravel Herd may have its own design. Try to prevent users from modifying the site's domain name, nginx configuration file, etc. To ensure maximum stability. You can try PhpWebStudy. Another PHP environment tool. Supports any domain name. Everything, all under your control.

Hello, I am also experiencing an issue with Google Auth redirect due to the .test TLD which is rejected.

I use this as the callback url : h t t p : / / localhost/JUMP/my-project.test/auth/google/callback

(* the weird h t t p : / /. is intentional here in the forum as it would not let me add a link in my first post)

I just realized the url rewrite from the .htaccess won’t work because .htaccess is used by Apache. So I need to find a way to do the redirect url rewrite directive in a nginx conf file for my local app.

Any guidance on how/where to add a rewrite directive would be greatly appreciated. Thanks!

/=====/

Here's what I finally did to make it work:

Note : the weird spacing in the url is because Laracasts prevents me from including links as I am new to the forum.

#1) Added my Google API callback and my local development domains to the /etc/hosts file:

127.0.0.1	local . fakedomainxyz . com    // sorry for the weird spacing...
127.0.0.1	my-project . test    // sorry for the weird spacing...

#2) Defined the redirect url in Google API Console: h t t p s : // local . fakedomainxyz . com/auth/google/callback // sorry for the weird spacing...

#3) Made sure the Google API callback url is the same in my project .env file

#4) Ensured my project directory is in the parked Herd directory

#5) Set herd secure in my local project directory (or you can also set it via the GUI)

#6) Inside the nginx config file .../Herd/config/valet/my-project.test, under the first server block (for http / non-ssl), I added a ssl server block as:

server {
    listen 127.0.0.1:443 ssl;
    server_name local . fakedomainxyz . com;    // sorry for the weird spacing...
    rewrite ^/(.*)$ h t t p s : // my-project . test/ permanent;    // sorry for the weird spacing...
    ssl_certificate "/Users/[your name]/Library/Application Support/Herd/config/valet/Certificates/[your local app domain].crt";
    ssl_certificate_key "/Users/[your name]/Library/Application Support/Herd/config/valet/Certificates/[your local app domain].key";
}

You can replace the 2 ssl_certificate lines with the one you can find in the default ssl server block below in the file.

Note: I decided to create the ssl server block above the existing one because nginx seem to go through the whole file following each block conditions so I thought it would be better to isolate my ssl block with the server_name that is only used during the Google callback so it should be skipped for any call that is not using this fake redirect domain.

#7) I ensured to restart the services from Herd and flushed all browser cache and cookies.

#8) In my app, after I log in, I get a warning that the certificate is not secured but this doesn't matter as I only access it from my local development on my machine.

For anyone still interested, I did finally get this working using Herd, Socialite, and Expose. Add the full Expose url with your callback to Authorized redirect URIs in your GCP Client ID for Web application. The GOOGLE_REDIRECT_URI in your .env should match exactly. Both settings should look something like https://ypk29e4a83.sharedwithexpose.com/auth/google/callback.

There are, of course, still issues with the whole keep-alive thing because it looks like you get a 1 hour timer when you start Expose. But still, good enough for testing.

Easy peasy. Lamb and sneezy. Hope this helps.

The lack of ability to use a custom domain is a huge drawback to our team using Herd.

First off, we have fonts that are whitelisted to work only on certain domains, and *.test isn't one of them.

Second, there are CORS restrictions that have similar whitelisted domains restrictions. Expose can probably solve some of these issues, but that's another configuration and another license.

Herd seemed like a slam dunk for teams development needs (we are a Laravel shop), but I'm thinking Mamp Pro might be better suited (and $10 cheaper/year).

Made a tool for this https://github.com/bergstar/herdomain