GitHub user jonbuffington opened a pull request:
https://github.com/apache/incubator-zeppelin/pull/221
feat: use ZEPPELIN_HOSTNAME to specify hostname
ZEPPELIN_HOSTNAME supports running Zeppelin in environments where the
hostname of the server does not match the hostname delivered to the
browser. If ZEPPELIN_HOSTNAME is not set, java.net.InetAddress.
getLocalHost().getHostName() is still used to lookup the server's
current hostname.
NotebookServerTests was renamed to NotebookServerTest to permit the
test cases to run using Maven's test goal.
Fixes https://issues.apache.org/jira/browse/ZEPPELIN-231
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/fuseelements/incubator-zeppelin
WIP-hostname-env
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-zeppelin/pull/221.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #221
----
commit 336c49e4d2efe227c7e5425f378646a703d96962
Author: Jon Buffington <j...@fuseelements.com>
Date: 2015-08-17T21:13:16Z
feat: use ZEPPELIN_HOSTNAME to specify hostname
ZEPPELIN_HOSTNAME supports running Zeppelin in environments where the
hostname of the server does not match the hostname delivered to the
browser. If ZEPPELIN_HOSTNAME is not set, java.net.InetAddress.
getLocalHost().getHostName() is still used to lookup the server's
current hostname.
NotebookServerTests was renamed to NotebookServerTest to permit the
test cases to run using Maven's test goal.
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
