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

add --port parameter to "dbt docs serve" (#955) #987

Merged
merged 1 commit into from
Sep 11, 2018

Conversation

beckjake
Copy link
Contributor

@beckjake beckjake commented Sep 7, 2018

Adds a --port parameter to "dbt docs serve" that defaults to 8080.

FIxes #955.

@@ -29,7 +31,7 @@ def run(self):
)

try:
webbrowser.open_new_tab('http://127.0.0.1:8080')
webbrowser.open_new_tab('http://127.0.0.1:{}'.format(port))
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this is not relevant to this change, but it looks like we serve on 0.0.0.0 but we open 127.0.0.1 in the browser. Is there an appreciable difference between these two addresses? I think that 0.0.0.0 is accessible to others on the network, right?

Copy link
Contributor Author

@beckjake beckjake Sep 7, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You shouldn't access 0.0.0.0 - it's intended as a valid address for listening, and means that all source addresses can access it. 127.0.0.0/8 is reserved for loopback adapters and by default 127.0.0.1 is generally bound to a default loopback adapter on every OS, with a hosts file entry of 'localhost' pointing to it.

Copy link
Contributor

@drewbanin drewbanin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

One comment strictly for my edification, but this LGTM

@beckjake beckjake merged commit 669a29b into dev/lucretia-mott Sep 11, 2018
@beckjake beckjake deleted the feature/dbt-docs-serve-port branch September 11, 2018 13:34
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