Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Feature: Wildcard subdomains? #122

Closed
clytras opened this issue Feb 23, 2021 · 2 comments · Fixed by #138
Closed

Feature: Wildcard subdomains? #122

clytras opened this issue Feb 23, 2021 · 2 comments · Fixed by #138
Labels
feature good first issue

Comments

@clytras
Copy link

clytras commented Feb 23, 2021

I can see there is a feature supporting subdomains with #11 and I'd like to ask if it would be possible to add wildcard subdomain support, something like the following format:

*.mydomain http://localhost:8080

will resolve to every subdomain automatically, like:

test.mydomain.dev
user10.mydomain.dev
admin.mydomain.dev

There are applications that have such features to generate subdomains and of course this is configurable in a DNS level and there are even wildcard SSL certificates and having such a feature for developement environment using Ergo would be awesome!
cristianoliveira added a commit that referenced this issue May 23, 2023
@cristianoliveira
feat: allows using wildcard for services
6cc9c1e 
Usage:
  *.frontend http://localhost:3000

  All requests like
   - http://foo.frontend.dev
   - http://bar.frontend.dev
   - http://doesnmatter.frontend.dev

  Are now redirected to http://localhost:3000

Closes #122
cristianoliveira added a commit that referenced this issue May 23, 2023
@cristianoliveira
feat: allows using wildcard for services
94f739a 
Usage:
  *.frontend http://localhost:3000

  All requests like
   - http://foo.frontend.dev
   - http://bar.frontend.dev
   - http://doesnmatter.frontend.dev

  Are now redirected to http://localhost:3000

Closes #122
@cristianoliveira cristianoliveira mentioned this issue May 23, 2023
Merged
cristianoliveira added a commit that referenced this issue May 23, 2023
@cristianoliveira
feat: allows using wildcard for services
3fb9b9b 
Usage:
  *.frontend http://localhost:3000

  All requests like
   - http://foo.frontend.dev
   - http://bar.frontend.dev
   - http://doesnmatter.frontend.dev

  Are now redirected to http://localhost:3000

Closes #122
@cristianoliveira
Copy link
Owner

I know it's been a while but this feature is now implemented on ergo and soon will be merged :D

cristianoliveira added a commit that referenced this issue May 23, 2023
@cristianoliveira
feat: allows using wildcards for services (#138)
b6c0955 
* feat: allows using wildcard for services

Usage:
  *.frontend http://localhost:3000

  All requests like
   - http://foo.frontend.dev
   - http://bar.frontend.dev
   - http://doesnmatter.frontend.dev

  Are now redirected to http://localhost:3000

Closes #122

* chore: run linter
@clytras
Copy link
Author

clytras commented May 25, 2023

Thank you @cristianoliveira,

I've switched some projects to use Caddy for local development, but the initiation and configuration process is a PITA compared to Ergo's simplicity.

I'll definately look at this feature.

cristianoliveira added a commit that referenced this issue Jun 3, 2023
@cristianoliveira
feat: allows using wildcards for services (#138)
b74eb69 
* feat: allows using wildcard for services

Usage:
  *.frontend http://localhost:3000

  All requests like
   - http://foo.frontend.dev
   - http://bar.frontend.dev
   - http://doesnmatter.frontend.dev

  Are now redirected to http://localhost:3000

Closes #122

* chore: run linter
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
feature good first issue
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

feat: allows using wildcards for services cristianoliveira/ergo
2 participants
@cristianoliveira @clytras