[Feature Request]: Handle different TLDs better

[Gelbotron]

Feature Description

As a developer using multiple devices for development, I encountered an issue after installing Herd. It took me considerable time to identify the source of the problem - a TLD conflict. Herd displayed the .test domain in the Sites tab, which confused me, as my setup on the personal computer used the .localhost TLD.

While I understand that supporting random TLDs might not be feasible, I suggest implementing a warning system within Herd to alert users if their TLD setup, specifically .test, is not configured correctly.

Is this feature valuable for other users as well and why?

This improvement would help avoid confusion and streamline the development process for Herd users.

[sujithtomy]

a ".test" tld will not accept in Google Auth Client. so it is a deadlock situation to develop laravel google auth projects with Herd as far as I know. (any other solutions?)

Not sure why this ticket is closed with out a fix or suggestion to workaround!

[matthewhutchings]

having this issue - google auth requires a tld or localhost.

I cant seem to access my project via localhost (when set in env) but can access it through .test

The only way round this was to use php artisan share but its a lot slower.

[maximepvrt]

Feel free to upvote and leave a comment on Issue https://issuetracker.google.com/issues/313466544?pli=1 to push Google to allow .test domains in OAuth callback URLs 🚀

[sschlein]

We've implemented a way to solve that for Google auth but still keep .test domains in Herd: https://herd.laravel.com/docs/windows/advanced-usage/social-auth

[milhouse1337]

I used the herd tld command to set a custom domain that resolves to 127.0.0.1. But it doesn't seems to be "officially" supported. 🤷‍♂️

➜  ~ herd tld example.com
Using a custom TLD is no longer officially supported and may lead to unexpected behavior. Do you wish to proceed? [y/N]

Maybe there is a better way, but so far it worked like a charm for me.

[maximepvrt]

@mechelon do you plan to add this feature soon? same problem as @sujithtomy, ".test" tld will not accept in Google Auth Client

[199ocero]

Is there any update for this? I want also to use Herd but it's preventing me to try since I have a Google auth and .test domain is not working.

[maximepvrt]

Feel free to upvote and leave a comment on Issue https://issuetracker.google.com/issues/313466544?pli=1 to push Google to allow .test domains in OAuth callback URLs 🚀

[JonPurvis]

I'd also like to see this feature implemented. Having to run some projects locally outside of Herd and it is not fun 😭

[michaloravec]

This is a necessary feature.

[joshlewis]

Agreed, this needs to be easier.

[maximepvrt]

@mechelon @sschlein @mpociot This was announced in May, but still not available 😢https://x.com/marcelpociot/status/1790412281307701466

[maximepvrt]

@mechelon @sschlein @mpociot Why is there still no news about this feature?

[HichemTab-tech]

any progress here ? I'm blocked in the same situation, can't use .test domain in google auth api. i can just "not use" Herd to resolve my problem, but i really do want to use it for other feature, please don't ruin this just because of this issue.

[maximepvrt]

Feel free to upvote and leave a comment on Issue https://issuetracker.google.com/issues/313466544?pli=1 to push Google to allow .test domains in OAuth callback URLs 🚀

[jonappcinking]

What steps can we take to address these issues? As a developer, I find working with the Google Console to be a bottleneck.

[sschlein]

We're currently testing this feature internally but it's pretty complex as a change of the tld needs regeneration of all config files and certificates. Should arrive soon

[rifrocket]

I wan to contribute to solving this issue, can I ?, because I need the functionality to update TLD, it is very important feature.

[sschlein]

You can use Expose to create a shared url until this feature is ready and even get a .com that points to your local app

[ejunker]

I used the herd tld to set a custom TLD and so far it seems to be working well. I hope that in the future the custom TLD will be able to be configured in the herd.yml file.

[sschlein]

The problem with custom tlds (right now) is that they also effect TLS certificate generations and all existing nginx configurations, so it's not the easiest feature and just running herd tld could break your setup at the moment.

The feature is planned on a global basis and we hope to release it with Herd 1.12 – but this also means that individual tld configuration per site like it's done in the herd.yml wouldn't work.

[maximepvrt]

any news about this?

[nshontz]

Bumping this issue.

As mentioned before, a ".test" tld is not accepted in Google Auth Client, making apps that use Google for Auth incompatible with Herd.

Thanks for all of the work. Herd is amazing.

[maximepvrt]

Feel free to upvote and leave a comment on Issue https://issuetracker.google.com/issues/313466544?pli=1 to push Google to allow .test domains in OAuth callback URLs 🚀

[badrshs]

Has anyone come across a solution for this? The herd tld dev didn't work for me.

and yeh same issue as the guys mentioned Google auth doesn't allow .test domain , I'm trying to use .dev or anything else

[maximepvrt]

Feel free to upvote and leave a comment on Issue https://issuetracker.google.com/issues/313466544?pli=1 to push Google to allow .test domains in OAuth callback URLs 🚀

[jakebathman]

Please don't spam the same comment on every reply, people subscribed to this issue get an email for every single one.

[sergyu91ma]

What about not using a TLD at all? This should be optional.
I have apps with "local<sitename>" for local development and i really want to leave them like that when i switch to herd.
Why should be a .smth mandatory ?
Maybe i don't use ssl locally, if that is a problem.
Anyway this should be at least configurable if not optional.
In other tools like xampp, laragon, flydev this is not a problem. You can customize it however you want.

[HichemTab-tech]

guys, the solution proposed by @milhouse1337 works pretty well; you shouldn't be blocked by this error :) I waited too long for a solution either from both the Laravel team and Google, but when I tried this solution I stopped worrying about whether they fix it or not haha.

[sschlein]

No TLD is not on the roadmap as this breaks the whole idea behind Herd running on actual domains, so I don't think we will reconsider this in the future. If this is a requirement for you, Herd might not be a good fit for you.

You are actually the first one requesting this.

[HichemTab-tech]

@sergyu91ma I just tried what you told me yesterday about the php versions, and it worked, I didn't face a problem :) i mean i set php 8.3 for my site, and the global version is 8.4, but the site IS actually running on 8.3 as expected i mean Herd worked perfectly, look :

• my route to show php info :

• the output :D

so the site followed the right version even if global version is different :D

[sergyu91ma]

Looks like your TLD is .com in herd, different from default, and weirdly is working.
Then smth is different on my side.

I did use link in herd for the sites. Maybe because of that?!
I didn't used parked path. From pictures you use that.

Can you also try to use xdebug on the 8.3 version? to see if it works?

[HichemTab-tech]

I did use link in herd for the sites. Maybe because of that?! I didn't used parked path. From pictures you use that.
what do you mean by link ?
And i just tried xdebug and it worked :")

[sergyu91ma]

You can link a site (which makes a symlink behind) if you want another domain name for your site rather than the folder name.
Read here in docs in the second part.
https://herd.laravel.com/docs/windows/getting-started/sites

I did it like that and it didnt't got the right php version when isolated.

[RonDarby]

I'm looking for a solution that will allow me to have multiple tlds concurrently in herd, where I can select which one I want for each project. Not here to bump the discussion, but reading the issues everyone here is mentioning about google auth, I managed to solve that by simply doing the following:

• cd ~/Library/Application\ Support/Herd/config you will find the various services, nginx, dnsmasq, valet and phpfpm files etc
• vim ./valet/config.json and edit the tld value to localtest.me
• cd into your project folder and herd link what-have-you or herd init and follow the prompts
• https://what-have-you.localtest.me works
• DO NOT go herd tld xxxx unless you are happy to break any custom setups you may have, I had a few custom nginx files serving as a proxy to nodejs servers running in docker projects that needed fixing up again (I like the self signed Valet CA certificates for local testing)

Sorted, no edit of hosts files or anything as xxxx.localtest.me points to 127.0.0.1 and google recognises it.

I tried editing dnsmasq with no joy, I'll still crack that one, but the certs will still be a problem with other domains that weren't added via the herd link command, there are limitations though.

[mikebronner]

Additionally, VSCode no longer follows links with .test domains in the terminal, as they are not valid URLs. VSCode now validates the URLs apparently.

This is definitely an annoyance, and manually setting the TLD via the command outlined in previous commends herd tld doesn't seem to work anymore, as the sites show as your custom TLD, but still resolve to .test.

[sschlein]

We've built a small service to make implementing Google auth (and other) easy:
https://herd.laravel.com/docs/windows/advanced-usage/social-auth

I am pretty sure that VSCode will fix that soon because using a valid public TLD would introduce a serious security issue and while we have a prototype that supports other TLDs like .wip, .herd and .local, that doesn't solve the valid URL problem.

[mikebronner]

Thanks for the explanation @sschlein, just wanted to add that .local domains do work with VSCode, we use those with our non-Herd projects. (This probably was because the domain was trusted.)

[mikebronner]

One more quick note in case others are experiencing the same issue I have: microsoft/vscode#249353 (comment)

Adding your .test domain to VSCode's Trusted Domains seems to solve the problem and make them clickable in the terminal. Or adding "*", to the top of the list seems to work as well.