Elgato_dark/zeppelin
1
0
Fork 0
mirror of https://github.com/apache/zeppelin synced 2026-05-24 09:38:26 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 1

fix: URLs in setup

Browse source
This commit is contained in:
1ambda 2017-05-27 10:03:52 +09:00
parent 0b1d635136
commit 4c56de5c4d
18 changed files with 120 additions and 60 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

15
docs/_includes/themes/zeppelin/_navigation.html
View file

@ -78,13 +78,14 @@
<li><a href="{{BASE_PATH}}/setup/basics/how_to_build.html">How to Build Zeppelin</a></li>
<li><a href="{{BASE_PATH}}/setup/basics/multi_user_support.html">Multi-user Support</a></li>
<li role="separator" class="divider"></li>
<li class="title"><span>Setup Zeppelin on Cluster</span></li>
<li><a href="{{BASE_PATH}}/setup/cluster/spark_cluster_mode.html#spark-standalone-mode">Spark Cluster Mode: Standalone</a></li>
<li><a href="{{BASE_PATH}}/setup/cluster/spark_cluster_mode.html#spark-on-yarn-mode">Spark Cluster Mode: YARN</a></li>
<li><a href="{{BASE_PATH}}/setup/cluster/spark_cluster_mode.html#spark-on-mesos-mode">Spark Cluster Mode: Mesos</a></li>
<li><a href="{{BASE_PATH}}/setup/cluster/zeppelin_with_flink_and_spark_cluster.html">Zeppelin with Flink, Spark Cluster</a></li>
<li><a href="{{BASE_PATH}}/setup/cluster/cdh.html">Zeppelin on CDH</a></li>
<li><a href="{{BASE_PATH}}/setup/cluster/virtual_machine.html">Zeppelin on VM: Vagrant</a></li>
<li class="title"><span>Deployment</span></li>
<li><a href="{{BASE_PATH}}/setup/deployment/docker.html">Docker Image for Zeppelin</a></li>
<li><a href="{{BASE_PATH}}/setup/deployment/spark_cluster_mode.html#spark-standalone-mode">Spark Cluster Mode: Standalone</a></li>
<li><a href="{{BASE_PATH}}/setup/deployment/spark_cluster_mode.html#spark-on-yarn-mode">Spark Cluster Mode: YARN</a></li>
<li><a href="{{BASE_PATH}}/setup/deployment/spark_cluster_mode.html#spark-on-mesos-mode">Spark Cluster Mode: Mesos</a></li>
<li><a href="{{BASE_PATH}}/setup/deployment/flink_and_spark_cluster.html">Zeppelin with Flink, Spark Cluster</a></li>
<li><a href="{{BASE_PATH}}/setup/deployment/cdh.html">Zeppelin on CDH</a></li>
<li><a href="{{BASE_PATH}}/setup/deployment/virtual_machine.html">Zeppelin on VM: Vagrant</a></li>
<li role="separator" class="divider"></li>
<li class="title"><span>Security</span></li>
<li><a href="{{BASE_PATH}}/setup/security/authentication_nginx.html">HTTP Basic Auth using NGINX</a></li>

17
docs/index.md
View file

@ -83,13 +83,14 @@ limitations under the License.
* Basics
* [How to Build Zeppelin](./setup/basics/how_to_build.html)
* [Multi-user Support](./setup/basics/multi_user_support.html)
* Setup Zeppelin on Cluster
* [Spark Cluster Mode: Standalone](./setup/cluster/spark_cluster_mode.html#spark-standalone-mode)
* [Spark Cluster Mode: YARN](./setup/cluster/spark_cluster_mode.html#spark-on-yarn-mode)
* [Spark Cluster Mode: Mesos](./setup/cluster/spark_cluster_mode.html#spark-on-mesos-mode)
* [Zeppelin with Flink and Spark Cluster](./setup/cluster/zeppelin_with_flink_and_spark_cluster.html)
* [Zeppelin on CDH](./setup/cluster/cdh.html)
* [Zeppelin on VM: Vagrant](./setup/cluster/virtual_machine.html)
* Deployment
* [Docker Image for Zeppelin](./setup/deployment/docker.html)
* [Spark Cluster Mode: Standalone](./setup/deployment/spark_cluster_mode.html#spark-standalone-mode)
* [Spark Cluster Mode: YARN](./setup/deployment/spark_cluster_mode.html#spark-on-yarn-mode)
* [Spark Cluster Mode: Mesos](./setup/deployment/spark_cluster_mode.html#spark-on-mesos-mode)
* [Zeppelin with Flink and Spark Cluster](./setup/deployment/flink_and_spark_cluster.html)
* [Zeppelin on CDH](./setup/deployment/cdh.html)
* [Zeppelin on VM: Vagrant](./setup/deployment/virtual_machine.html)
* Security: available security support in Apache Zeppelin
* [HTTP Basic Auth using NGINX](./setup/security/authentication_nginx.html)
* [Shiro Authentication](./setup/security/shiro_authentication.html)
@ -100,7 +101,7 @@ limitations under the License.
* [Git Storage](./setup/storage/storage.html#notebook-storage-in-local-git-repository)
* [S3 Storage](./setup/storage/storage.html#notebook-storage-in-s3)
* [Azure Storage](./setup/storage/storage.html#notebook-storage-in-azure)
* [ZeppelinHub Storage](./setup/storage/storage.html#notebook-torage-in-zeppelinhub)
* [ZeppelinHub Storage](./setup/storage/storage.html#notebook-storage-in-zeppelinhub)
* [MongoDB Storage](./setup/storage/storage.html#notebook-storage-in-mongodb)
* Operation
* [Configuration](./setup/operation/configuration.html): lists for Apache Zeppelin

8
docs/install/build.md → docs/setup/basics/how_to_build.md
View file

@ -1,8 +1,8 @@
---
layout: page
title: "Build from Source"
title: "How to Build Zeppelin from source"
description: "How to build Zeppelin from source"
group: install
group: setup/basics
---
<!--
Licensed under the Apache License, Version 2.0 (the "License");
@ -19,7 +19,7 @@ limitations under the License.
-->
{% include JB/setup %}
## Building from Source
## How to Build Zeppelin from Source
<div id="toc"></div>
@ -82,7 +82,7 @@ You can directly start Zeppelin by running after successful build:
Check [build-profiles](#build-profiles) section for further build options.
If you are behind proxy, follow instructions in [Proxy setting](#proxy-setting-optional) section.
If you're interested in contribution, please check [Contributing to Apache Zeppelin (Code)](../development/howtocontribute.html) and [Contributing to Apache Zeppelin (Website)](../../development/contributewebsite.html).
If you're interested in contribution, please check [Contributing to Apache Zeppelin (Code)](../../development/contribution/how_to_contribute_code.html) and [Contributing to Apache Zeppelin (Website)](../../development/contribution/how_to_contribute_website.html).
### Build profiles

29
docs/setup/basics/multi_user_support.md Normal file
View file

@ -0,0 +1,29 @@
---
layout: page
title: "Multi-user Support"
description: ""
group: setup/basics
---
<!--
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
-->
{% include JB/setup %}
# Multi-user Support
<div id="toc"></div>
Welcome to Apache Zeppelin! On this page are instructions to help you get started.
## Requirements

8
docs/install/cdh.md → docs/setup/deployment/cdh.md
View file

@ -2,7 +2,7 @@
layout: page
title: "Apache Zeppelin on CDH"
description: "This document will guide you how you can build and configure the environment on CDH with Apache Zeppelin using docker scripts."
group: install
group: setup/deployment
---
<!--
Licensed under the Apache License, Version 2.0 (the "License");
@ -85,16 +85,16 @@ export SPARK_HOME=[your_spark_home_path]
Don't forget to set Spark `master` as `yarn-client` in Zeppelin **Interpreters** setting page like below.
<img src="../assets/themes/zeppelin/img/docs-img/zeppelin_yarn_conf.png" />
<img src="/assets/themes/zeppelin/img/docs-img/zeppelin_yarn_conf.png" />
### 5. Run Zeppelin with Spark interpreter
After running a single paragraph with Spark interpreter in Zeppelin,
<img src="../assets/themes/zeppelin/img/docs-img/zeppelin_with_cdh.png" />
<img src="/assets/themes/zeppelin/img/docs-img/zeppelin_with_cdh.png" />
<br/>
browse `http://<hostname>:8088/cluster/apps` to check Zeppelin application is running well or not.
<img src="../assets/themes/zeppelin/img/docs-img/cdh_yarn_applications.png" />
<img src="/assets/themes/zeppelin/img/docs-img/cdh_yarn_applications.png" />

2
docs/install/docker.md → docs/setup/deployment/docker.md
View file

@ -2,7 +2,7 @@
layout: page
title: "Apache Zeppelin Releases Docker Images"
description: "This document contains instructions about making docker containers for Zeppelin. It mainly provides guidance into how to create, publish and run docker images for zeppelin releases."
group: install
group: setup/deployment
---
<!--
Licensed under the Apache License, Version 2.0 (the "License");

12
docs/setup/cluster/zeppelin_with_flink_and_spark_cluster.md → docs/setup/deployment/flink_and_spark_cluster.md
View file

@ -2,7 +2,7 @@
layout: page
title: "Install Zeppelin with Flink and Spark in cluster mode"
description: ""
group: setup/cluster
group: setup/deployment
---
<!--
Licensed under the Apache License, Version 2.0 (the "License");
@ -100,7 +100,7 @@ sudo ln -s /usr/local/apache-maven-3.3.9/bin/mvn /usr/bin/mvn
```
### Installing Zeppelin
This provides a quick overview of Zeppelin installation from source, however the reader is encouraged to review the [Zeppelin Installation Guide](../install/install.html)
This provides a quick overview of Zeppelin installation from source, however the reader is encouraged to review the [Zeppelin Installation Guide](../../quickstart/install.html)
From the command prompt:
Clone Zeppelin.
@ -153,7 +153,7 @@ Use `ifconfig` to determine the host machine's IP address. If you are not famili
Open a web-browser on a machine connected to the same network as the host (or in the host operating system if using a virtual machine). Navigate to http://`yourip`:8080, where yourip is the IP address you found in `ifconfig`.
See the [Zeppelin tutorial](../tutorial/tutorial.html) for basic Zeppelin usage. It is also advised that you take a moment to check out the tutorial notebook that is included with each Zeppelin install, and to familiarize yourself with basic notebook functionality.
See the [Zeppelin tutorial](../../quickstart/tutorial.html) for basic Zeppelin usage. It is also advised that you take a moment to check out the tutorial notebook that is included with each Zeppelin install, and to familiarize yourself with basic notebook functionality.
##### Flink Test
Create a new notebook named "Flink Test" and copy and paste the following code.
@ -291,7 +291,7 @@ build-target/bin/start-cluster.sh
In a browser, navigate to http://`yourip`:8082 to see the Flink Web-UI. Click on 'Task Managers' in the left navigation bar. Ensure there is at least one Task Manager present.
<center>![alt text](../assets/themes/zeppelin/img/screenshots/flink-webui.png "The Flink Web-UI")</center>
<center>![alt text](/assets/themes/zeppelin/img/screenshots/flink-webui.png "The Flink Web-UI")</center>
If no task managers are present, restart the Flink cluster with the following commands:
@ -369,7 +369,7 @@ spark/sbin/start-master.sh --webui-port 8082
Open a browser and navigate to http://`yourip`:8082 to ensure the Spark master is running.
<center>![alt text](../assets/themes/zeppelin/img/screenshots/spark-master-webui1.png "It should look like this...")</center>
<center>![alt text](/assets/themes/zeppelin/img/screenshots/spark-master-webui1.png "It should look like this...")</center>
Toward the top of the page there will be a *URL*: spark://`yourhost`:7077. Note this URL, the Spark Master URI, it will be needed in subsequent steps.
@ -416,6 +416,6 @@ You should be able check the Flink and Spark webuis (at something like http://`y
### Next Steps
Check out the [tutorial](./tutorial.html) for more cool things you can do with your new toy!
Check out the [tutorial](../../quickstart/tutorial.html) for more cool things you can do with your new toy!
[Join the community](http://zeppelin.apache.org/community.html), ask questions and contribute! Every little bit helps.

14
docs/install/spark_cluster_mode.md → docs/setup/deployment/spark_cluster_mode.md
View file

@ -2,7 +2,7 @@
layout: page
title: "Apache Zeppelin on Spark cluster mode"
description: "This document will guide you how you can build and configure the environment on 3 types of Spark cluster manager(Standalone, Hadoop Yarn, Apache Mesos) with Apache Zeppelin using docker scripts."
group: install
group: setup/deployment
---
<!--
Licensed under the Apache License, Version 2.0 (the "License");
@ -61,12 +61,12 @@ Note that `sparkmaster` hostname used here to run docker container should be def
### 3. Configure Spark interpreter in Zeppelin
Set Spark master as `spark://<hostname>:7077` in Zeppelin **Interpreters** setting page.
<img src="../assets/themes/zeppelin/img/docs-img/standalone_conf.png" />
<img src="/assets/themes/zeppelin/img/docs-img/standalone_conf.png" />
### 4. Run Zeppelin with Spark interpreter
After running single paragraph with Spark interpreter in Zeppelin, browse `https://<hostname>:8080` and check whether Spark cluster is running well or not.
<img src="../assets/themes/zeppelin/img/docs-img/spark_ui.png" />
<img src="/assets/themes/zeppelin/img/docs-img/spark_ui.png" />
You can also simply verify that Spark is running well in Docker with below command.
@ -139,12 +139,12 @@ export SPARK_HOME=[your_spark_home_path]
Don't forget to set Spark `master` as `yarn-client` in Zeppelin **Interpreters** setting page like below.
<img src="../assets/themes/zeppelin/img/docs-img/zeppelin_yarn_conf.png" />
<img src="/assets/themes/zeppelin/img/docs-img/zeppelin_yarn_conf.png" />
### 5. Run Zeppelin with Spark interpreter
After running a single paragraph with Spark interpreter in Zeppelin, browse `http://<hostname>:8088/cluster/apps` and check Zeppelin application is running well or not.
<img src="../assets/themes/zeppelin/img/docs-img/yarn_applications.png" />
<img src="/assets/themes/zeppelin/img/docs-img/yarn_applications.png" />
@ -201,13 +201,13 @@ export SPARK_HOME=[PATH OF SPARK HOME]
Don't forget to set Spark `master` as `mesos://127.0.1.1:5050` in Zeppelin **Interpreters** setting page like below.
<img src="../assets/themes/zeppelin/img/docs-img/zeppelin_mesos_conf.png" />
<img src="/assets/themes/zeppelin/img/docs-img/zeppelin_mesos_conf.png" />
### 5. Run Zeppelin with Spark interpreter
After running a single paragraph with Spark interpreter in Zeppelin, browse `http://<hostname>:5050/#/frameworks` and check Zeppelin application is running well or not.
<img src="../assets/themes/zeppelin/img/docs-img/mesos_frameworks.png" />
<img src="/assets/themes/zeppelin/img/docs-img/mesos_frameworks.png" />
### Troubleshooting for Spark on Mesos

2
docs/install/virtual_machine.md → docs/setup/deployment/virtual_machine.md
View file

@ -2,7 +2,7 @@
layout: page
title: "Apache Zeppelin on Vagrant Virtual Machine"
description: "Apache Zeppelin provides a script for running a virtual machine for development through Vagrant. The script will create a virtual machine with core dependencies pre-installed, required for developing Apache Zeppelin."
group: install
group: setup/deployment
---
<!--
Licensed under the Apache License, Version 2.0 (the "License");

2
docs/install/yarn_install.md → docs/setup/deployment/yarn_install.md
View file

@ -2,7 +2,7 @@
layout: page
title: "Install Zeppelin to connect with existing YARN cluster"
description: "This page describes how to pre-configure a bare metal node, configure Apache Zeppelin and connect it to existing YARN cluster running Hortonworks flavour of Hadoop."
group: install
group: setup/deployment
---
<!--
Licensed under the Apache License, Version 2.0 (the "License");

2
docs/install/configuration.md → docs/setup/operation/configuration.md
View file

@ -2,7 +2,7 @@
layout: page
title: "Apache Zeppelin Configuration"
description: "This page will guide you to configure Apache Zeppelin using either environment variables or Java properties. Also, you can configure SSL for Zeppelin."
group: install
group: setup/operation
---
<!--
Licensed under the Apache License, Version 2.0 (the "License");

29
docs/setup/operation/trouble_shooting.md Normal file
View file

@ -0,0 +1,29 @@
---
layout: page
title: "Trouble Shooting"
description: ""
group: setup/operation
---
<!--
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
-->
{% include JB/setup %}
# Trouble Shooting
<div id="toc"></div>
Welcome to Apache Zeppelin! On this page are instructions to help you get started.
## Requirements

4
docs/install/upgrade.md → docs/setup/operation/upgrading.md
View file

@ -2,7 +2,7 @@
layout: page
title: "Manual Zeppelin version upgrade procedure"
description: "This document will guide you through a procedure of manual upgrade your Apache Zeppelin instance to a newer version. Apache Zeppelin keeps backward compatibility for the notebook file format."
group: install
group: setup/operation
---
<!--
Licensed under the Apache License, Version 2.0 (the "License");
@ -35,7 +35,7 @@ So, copying `notebook` and `conf` directory should be enough.
1. Copy your `notebook` and `conf` directory into a backup directory
1. Download newer version of Zeppelin and Install. See [Install page](./install.html#installation).
1. Download newer version of Zeppelin and Install. See [Install Guide](../../quickstart/install.html#install).
1. Copy backup `notebook` and `conf` directory into newer version of Zeppelin `notebook` and `conf` directory

8
docs/security/authentication.md → docs/setup/security/authentication_nginx.md
View file

@ -1,8 +1,8 @@
---
layout: page
title: "Authentication for NGINX"
title: "HTTP Basic Auth using NGINX"
description: "There are multiple ways to enable authentication in Apache Zeppelin. This page describes HTTP basic auth using NGINX."
group: security
group: setup/security
---
<!--
Licensed under the Apache License, Version 2.0 (the "License");
@ -23,7 +23,7 @@ limitations under the License.
<div id="toc"></div>
[Build in authentication mechanism](./shiroauthentication.html) is recommended way for authentication. In case of you want authenticate using NGINX and [HTTP basic auth](https://en.wikipedia.org/wiki/Basic_access_authentication), please read this document.
[Build in authentication mechanism](./shiro_authentication.html) is recommended way for authentication. In case of you want authenticate using NGINX and [HTTP basic auth](https://en.wikipedia.org/wiki/Basic_access_authentication), please read this document.
## HTTP Basic Authentication using NGINX
@ -121,7 +121,7 @@ This instruction based on Ubuntu 14.04 LTS but may work with other OS with few c
1. More security consideration
* Using HTTPS connection with Basic Authentication is highly recommended since basic auth without encryption may expose your important credential information over the network.
* Using [Shiro Security feature built-into Zeppelin](./shiroauthentication.html) is recommended if you prefer all-in-one solution for authentication but NGINX may provides ad-hoc solution for re-use authentication served by your system's NGINX server or in case of you need to separate authentication from zeppelin server.
* Using [Shiro Security feature built-into Zeppelin](./shiro_authentication.html) is recommended if you prefer all-in-one solution for authentication but NGINX may provides ad-hoc solution for re-use authentication served by your system's NGINX server or in case of you need to separate authentication from zeppelin server.
* It is recommended to isolate direct connection to Zeppelin server from public internet or external services to secure your zeppelin instance from unexpected attack or problems caused by public zone.
## Another option

12
docs/security/datasource_authorization.md → docs/setup/security/datasource_authorization.md
View file

@ -2,7 +2,7 @@
layout: page
title: "Data Source Authorization in Apache Zeppelin"
description: "Apache Zeppelin supports protected data sources. In case of a MySql database, every users can set up their own credentials to access it."
group: security
group: setup/security
---
<!--
Licensed under the Apache License, Version 2.0 (the "License");
@ -35,17 +35,17 @@ In this case, you can add your credential information to Apache Zeppelin and use
## How to save the credential information?
You can add new credentials in the dropdown menu for your data source which can be passed to interpreters.
<img class="img-responsive" src="../assets/themes/zeppelin/img/docs-img/credential_tab.png" width="180px"/>
<img class="img-responsive" src="/assets/themes/zeppelin/img/docs-img/credential_tab.png" width="180px"/>
**Entity** can be the key that distinguishes each credential sets.(We suggest that the convention of the **Entity** is `[Interpreter Group].[Interpreter Name]`.)
Please see [what is interpreter group](../manual/interpreters.html#what-is-interpreter-group) for the detailed information.
Please see [what is interpreter group](../../usage/interpreter/overview.html#what-is-interpreter-group) for the detailed information.
Type **Username & Password** for your own credentials. ex) Mysql user & password of the JDBC Interpreter.
<img class="img-responsive" src="../assets/themes/zeppelin/img/docs-img/add_credential.png" />
<img class="img-responsive" src="/assets/themes/zeppelin/img/docs-img/add_credential.png" />
The credentials saved as per users defined in `conf/shiro.ini`.
If you didn't activate [shiro authentication in Apache Zeppelin](./shiroauthentication.html), your credential information will be saved as `anonymous`.
If you didn't activate [shiro authentication in Apache Zeppelin](./shiro_authentication.html), your credential information will be saved as `anonymous`.
All credential information also can be found in `conf/credentials.json`.
#### JDBC interpreter
@ -60,5 +60,5 @@ You have to store the password information for users.
## Please note
As a first step of data source authentication feature, [ZEPPELIN-828](https://issues.apache.org/jira/browse/ZEPPELIN-828) was proposed and implemented in Pull Request [#860](https://github.com/apache/zeppelin/pull/860).
Currently, only customized 3rd party interpreters can use this feature. We are planning to apply this mechanism to [the community managed interpreters](../manual/interpreterinstallation.html#available-community-managed-interpreters) in the near future.
Currently, only customized 3rd party interpreters can use this feature. We are planning to apply this mechanism to [the community managed interpreters](../../usage/interpreter/installation.html#available-community-managed-interpreters) in the near future.
Please keep track [ZEPPELIN-1070](https://issues.apache.org/jira/browse/ZEPPELIN-1070).

8
docs/security/notebook_authorization.md → docs/setup/security/notebook_authorization.md
View file

@ -2,7 +2,7 @@
layout: page
title: "Notebook Authorization in Apache Zeppelin"
description: "This page will guide you how you can set the permission for Zeppelin notebooks. This document assumes that Apache Shiro authentication was set up."
group: security
group: setup/security
---
<!--
Licensed under the Apache License, Version 2.0 (the "License");
@ -25,7 +25,7 @@ limitations under the License.
## Overview
We assume that there is an **Shiro Authentication** component that associates a user string and a set of group strings with every NotebookSocket.
If you don't set the authentication components yet, please check [Shiro authentication for Apache Zeppelin](./shiroauthentication.html) first.
If you don't set the authentication components yet, please check [Shiro authentication for Apache Zeppelin](./shiro_authentication.html) first.
## Authorization Setting
You can set Zeppelin notebook permissions in each notebooks. Of course only **notebook owners** can change this configuration.
@ -37,14 +37,14 @@ As you can see, each Zeppelin notebooks has 3 entities :
* Readers ( users or groups )
* Writers ( users or groups )
<center><img src="../assets/themes/zeppelin/img/docs-img/permission_setting.png"></center>
<center><img src="/assets/themes/zeppelin/img/docs-img/permission_setting.png"></center>
Fill out the each forms with comma seperated **users** and **groups** configured in `conf/shiro.ini` file.
If the form is empty (*), it means that any users can perform that operation.
If someone who doesn't have **read** permission is trying to access the notebook or someone who doesn't have **write** permission is trying to edit the notebook, Zeppelin will ask to login or block the user.
<center><img src="../assets/themes/zeppelin/img/docs-img/insufficient_privileges.png"></center>
<center><img src="/assets/themes/zeppelin/img/docs-img/insufficient_privileges.png"></center>
## Separate notebook workspaces (public vs. private)
By default, the authorization rights allow other users to see the newly created note, meaning the workspace is `public`. This behavior is controllable and can be set through either `ZEPPELIN_NOTEBOOK_PUBLIC` variable in `conf/zeppelin-env.sh`, or through `zeppelin.notebook.public` property in `conf/zeppelin-site.xml`. Thus, in order to make newly created note appear only in your `private` workspace by default, you can set either `ZEPPELIN_NOTEBOOK_PUBLIC` to `false` in your `conf/zeppelin-env.sh` as follows:

6
docs/security/shiroauthentication.md → docs/setup/security/shiro_authentication.md
View file

@ -2,7 +2,7 @@
layout: page
title: "Apache Shiro Authentication for Apache Zeppelin"
description: "Apache Shiro is a powerful and easy-to-use Java security framework that performs authentication, authorization, cryptography, and session management. This document explains step by step how Shiro can be used for Zeppelin notebook authentication."
group: security
group: setup/security
---
<!--
Licensed under the Apache License, Version 2.0 (the "License");
@ -55,7 +55,7 @@ Then you can browse Zeppelin at [http://localhost:8080](http://localhost:8080).
### 4. Login
Finally, you can login using one of the below **username/password** combinations.
<center><img src="../assets/themes/zeppelin/img/docs-img/zeppelin-login.png"></center>
<center><img src="/assets/themes/zeppelin/img/docs-img/zeppelin-login.png"></center>
```
[users]
@ -231,5 +231,5 @@ If you want to grant this permission to other users, you can change **roles[ ]**
## Other authentication methods
- [HTTP Basic Authentication using NGINX](./authentication.html)
- [HTTP Basic Authentication using NGINX](./authentication_nginx.html)

2
docs/storage/storage.md → docs/setup/storage/storage.md
View file

@ -2,7 +2,7 @@
layout: page
title: "Notebook Storage for Apache Zeppelin"
description: Apache Zeppelin has a pluggable notebook storage mechanism controlled by zeppelin.notebook.storage configuration option with multiple implementations."
group: storage
group: setup/storage
---
<!--
Licensed under the Apache License, Version 2.0 (the "License");