[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.

[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.

[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

[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.

[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?