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

added hostname configuration #737

Merged
merged 1 commit into from Dec 18, 2013
Merged

added hostname configuration #737

merged 1 commit into from Dec 18, 2013

Conversation

radiodario
Copy link
Contributor

  • Added hostname configuration key
  • altered tests

This is in reponse to #642

# Log
address = opts.serverHttp.address()
serverHostname = if address.address is '0.0.0.0' then 'localhost' else address.address
serverHostname = address.address #if address.address is '0.0.0.0' then 'localhost' else address.address
Copy link
Member

Choose a reason for hiding this comment

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

Does this output 0.0.0.0 now when null/localhost is set?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Actually on my tests, it still outputs localhost, which is strange. Also on the current version, even if it's listening on 0.0.0.0 it's saying localhost, which made me think it wouldn't listen on all interfaces, i.e only on loopback. I think it'd be better if it outputs exactly what it is listening on?

@balupton
Copy link
Member

Yeah maybe. It could be an aliasing thing in more recent versions of the server stuff. My concern is if we list 0.0.0.0 that could seem strange for people who are expecting localhosg.

Will merge tomorrow :-)

@radiodario
Copy link
Contributor Author

While I understand your concern, I think calling it localhost when it's
actually listening on 0.0.0.0 would actually be considered misleading. For
me, localhost -> 127.0.0.1, which is very different from actually listening
on all interfaces. :)

On Mon, Dec 16, 2013 at 1:47 PM, Benjamin Arthur Lupton <
notifications@github.com> wrote:

Yeah maybe. It could be an aliasing thing in more recent versions of the
server stuff. My concern is if we list 0.0.0.0 that could seem strange for
people who are expecting localhosg.

Will merge tomorrow :-)


Reply to this email directly or view it on GitHubhttps://github.com//pull/737#issuecomment-30661245
.

balupton added a commit that referenced this pull request Dec 18, 2013
added hostname configuration
@balupton balupton merged commit b3a6f83 into docpad:master Dec 18, 2013
@balupton
Copy link
Member

Released to v6.58.2. Changed the localhost display line to check for 127.0.0.1 as re your suggestion.

balupton added a commit that referenced this pull request Dec 18, 2013
- v6.58.2 December 18, 2013
	- Can now change the hostname that we listen to via the `hostname`
configuration option
		- Thanks to [Dario](https://github.com/radiodario) for [pull request
#737](#737)
	- Updated dependencies
@radiodario
Copy link
Contributor Author

Woohoo! Thanks!
On Dec 18, 2013 1:36 AM, "Benjamin Arthur Lupton" notifications@github.com
wrote:

Released to v6.58.2. Changed the localhost display line to check for
127.0.0.1 as re your suggestion.


Reply to this email directly or view it on GitHubhttps://github.com//pull/737#issuecomment-30809093
.

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.

None yet

2 participants