GitHub user anthonycorbacho reopened a pull request:

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

    [DOC] Update shiro after merging #1568

    ### What is this PR for?
    A simple update of the documentation to let user know how that they need to 
copy `shiro.ini.template` to `shiro.ini`
    
    
    ### What type of PR is it?
    [Documentation]
    
    ### Screenshots (if appropriate)
    ![screen shot 2016-10-31 at 7 08 09 
pm](https://cloud.githubusercontent.com/assets/3139557/19850732/6466763a-9f9d-11e6-9949-d58740d6c229.png)
    
    ### Questions:
    * Does the licenses files need update? NO
    * Is there breaking changes for older versions? NO 
    * Does this needs documentation? NO
    


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

    $ git pull https://github.com/anthonycorbacho/incubator-zeppelin 
doc/ShiroTemplate

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

    https://github.com/apache/zeppelin/pull/1571.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 #1571
    
----
commit 3f11260cf6883154bec3ce036f669bc009dab9ca
Author: Anthony Corbacho <corbacho.anth...@gmail.com>
Date:   2016-10-31T10:05:28Z

    Update shiro part about coping shiro.ini.template to shiro.ini in conf

commit f933a6a0f6704e87084b7e12a784e89b7d38eb37
Author: Anthony Corbacho <corbacho.anth...@gmail.com>
Date:   2016-10-31T10:09:06Z

    Fix typo

commit bcba1dbdb4add485c34bd7cef29afa4673c9b70b
Author: Anthony Corbacho <corbacho.anth...@gmail.com>
Date:   2016-10-31T10:48:39Z

    Fix typo number 2 Yo

commit 2f73f56624da52304076c88ce8c0d282166fe118
Author: Anthony Corbacho <corbacho.anth...@gmail.com>
Date:   2016-10-31T13:43:29Z

    Fix typo :: copy -> cp ^^

----


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