-
Notifications
You must be signed in to change notification settings - Fork 63
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
Documentation: Elaborate on url and webRoot properties #348
Labels
Comments
DanKaplanSES
changed the title
Elaborate on url and webRoot properties
Documentation: Elaborate on url and webRoot properties
Jan 10, 2024
@hbenl I'm still learning the ropes of GitHub, so I hope this ping isn't out of line. Given your extensive contributions to the repository, I was wondering if you could share your insights on the issue I've raised. Thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This is a request for clarifying documentation. I don't understand what problem
url
and/orwebRoot
solve:I know when my app needs a running webserver, but I don't understand how these properties relate. I hoped they fired up a web server and served my local frontend files through it. That use case comes up for me all the time, and it's time consuming to have to figure out which web server is the easiest to set up just so I can troubleshoot some HTML/JS's behavior when it's opened locally vs through a server.
I can't tell if that's what this feature does or not. To me, that quote could be interpreted either way. Can the readme include more details about what these properties do and when you need them?
The text was updated successfully, but these errors were encountered: