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.

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

golang-1.17.2, update readme #285

Merged
merged 6 commits into from
Oct 31, 2021
Merged

golang-1.17.2, update readme #285

merged 6 commits into from
Oct 31, 2021

Conversation

nonrational
Copy link
Member

No description provided.

@nonrational nonrational merged commit 06bb09e into master Oct 31, 2021
@nonrational nonrational deleted the update-go-readme branch October 31, 2021 14:44
@cjlarose
Copy link
Member

cjlarose commented Nov 1, 2021

The functionality described by 3f601b0 and tested in 2aed6ee actually works pretty reliably for me and is important for my use case.

I work on a SaaS application where each customer has a custom subdomain and we rely on this behavior to ensure that we don't have to add a new symlink for every new customer we create locally.

FWIW, anecdotally, I've found that the behavior works as described in the README when using symlinks to point to directories, but does not work when using the "proxy" support by writing a file with a host/port.

@nonrational
Copy link
Member Author

nonrational commented Nov 1, 2021

Ah, thanks. I wasn't able to get it working in the last few releases and, in my haste, incorrectly assumed it'd been broken somewhere along the way.

I'll file this as a new issue to restore documentation to the README and add a test to verify the behavior.

@cjlarose
Copy link
Member

cjlarose commented Nov 1, 2021

Thanks so much!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants