GitHub user soralee opened a pull request:

    https://github.com/apache/zeppelin/pull/2073

    ZEPPELIN-2130_do_not_use_webDebPort

    ### What is this PR for?
    If user uses web application development port such like 9000 which is 
default value, Zeppelin is not working because of this 
[line](https://github.com/apache/zeppelin/blob/master/zeppelin-web/src/components/baseUrl/baseUrl.service.js#L27).
 So, Zeppelin site need to guide this content until fixing this line (I'll 
improve to flexible web application development port later).
    
    
    ### What type of PR is it?
    [ Documentation ]
    
    ### What is the Jira issue?
    * [ZEPPELIN-2130](https://issues.apache.org/jira/browse/ZEPPELIN-2130)
    
    ### How should this be tested?
    1. Run document development mode.
    2. Connect 
`http://localhost:4000/install/configuration.html#zeppelin-properties` on 
browser.
    3. Check the description of `ZEPPELIN_PORT`
    
    ### Screenshots (if appropriate)
    
![z_not_use_port](https://cloud.githubusercontent.com/assets/8110458/23350768/32cf941a-fd00-11e6-8a3c-3390ddf2d7df.png)
    
    
    ### Questions:
    * Does the licenses files need update? No
    * Is there breaking changes for older versions? No
    * Does this needs documentation? Yes


You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/soralee/zeppelin ZEPPELIN-2130_webDevPort_Doc

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/zeppelin/pull/2073.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 #2073
    
----
commit c634713787414d1014d7b6de5df24f6189228d4e
Author: soralee <sora0...@zepl.com>
Date:   2017-02-27T05:57:12Z

    ZEPPELIN-2130_do_not_use_webDebPort

----


---
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.
---

Reply via email to