Repository: incubator-zeppelin Updated Branches: refs/heads/master 1bdf1ff97 -> 0d4c3acc1
ZEPPELIN-657: Change the official location of Zeppelin in the documentation ### What is this PR for? Lately, an official location of Zeppelin was changed from **https://github.com/apache/incubator-zeppelin.git** to **http://git.apache.org/incubator-zeppelin.git**. So I changed the old location in several documentations to the latest one. ### What type of PR is it? Documentation ### Todos ### Is there a relevant Jira issue? [ZEPPELIN-657](https://issues.apache.org/jira/browse/ZEPPELIN-657) ### How should this be tested? ### Screenshots (if appropriate) ### Questions: * Does the licenses files need update? No * Is there breaking changes for older versions? No * Does this needs documentation? No Author: Ryu Ah young <[email protected]> Closes #700 from AhyoungRyu/ZEPPELIN-657 and squashes the following commits: 2144bcc [Ryu Ah young] ZEPPELIN-657: Change 'release' -> 'branch' in howtocontribute.md 813b438 [Ryu Ah young] ZEPPELIN-657: Change 'release' -> 'branch' 23646e5 [Ryu Ah young] ZEPPELIN-657: Fix the wrong locations c4bef6c [Ryu Ah young] ZEPPELIN-657: fix a typo in howtocontribute.md a5fb130 [Ryu Ah young] ZEPPELIN-657: Change the official location of Zeppelin Project: http://git-wip-us.apache.org/repos/asf/incubator-zeppelin/repo Commit: http://git-wip-us.apache.org/repos/asf/incubator-zeppelin/commit/0d4c3acc Tree: http://git-wip-us.apache.org/repos/asf/incubator-zeppelin/tree/0d4c3acc Diff: http://git-wip-us.apache.org/repos/asf/incubator-zeppelin/diff/0d4c3acc Branch: refs/heads/master Commit: 0d4c3acc1ad46ffeb65eae587c226ab00dff069c Parents: 1bdf1ff Author: Ryu Ah young <[email protected]> Authored: Mon Feb 8 14:34:46 2016 +0900 Committer: Lee moon soo <[email protected]> Committed: Thu Feb 11 12:01:39 2016 +0900 ---------------------------------------------------------------------- CONTRIBUTING.md | 6 +- docs/development/howtocontribute.md | 58 +++++++++----------- docs/development/howtocontributewebsite.md | 37 +++++-------- docs/install/virtual_machine.md | 46 ++++++++-------- docs/install/yarn_install.md | 6 +- scripts/vagrant/zeppelin-dev/README.md | 14 ++--- .../vagrant/zeppelin-dev/show-instructions.sh | 2 +- 7 files changed, 78 insertions(+), 91 deletions(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/incubator-zeppelin/blob/0d4c3acc/CONTRIBUTING.md ---------------------------------------------------------------------- diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index f40e808..947cb3f 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -144,13 +144,13 @@ First of all, you need the Zeppelin source code. The official location for Zeppe Get the source code on your development machine using git. ``` -git clone http://git.apache.org/incubator-zeppelin.git zeppelin +git clone git://git.apache.org/incubator-zeppelin.git zeppelin ``` -You may also want to develop against a specific release. For example, for branch-0.1 +You may also want to develop against a specific branch. For example, for branch-0.5.6 ``` -git clone -b branch-0.1 http://git.apache.org/incubator-zeppelin.git zeppelin +git clone -b branch-0.5.6 git://git.apache.org/incubator-zeppelin.git zeppelin ``` or with write access http://git-wip-us.apache.org/repos/asf/incubator-zeppelin/blob/0d4c3acc/docs/development/howtocontribute.md ---------------------------------------------------------------------- diff --git a/docs/development/howtocontribute.md b/docs/development/howtocontribute.md index 0de1e78..c2bd5cb 100644 --- a/docs/development/howtocontribute.md +++ b/docs/development/howtocontribute.md @@ -5,52 +5,49 @@ description: "How to contribute" group: development --- -## IMPORTANT +# Contributing to Apache Zeppelin ( Code ) +## IMPORTANT Apache Zeppelin (incubating) is an [Apache2 License](http://www.apache.org/licenses/LICENSE-2.0.html) Software. -Any contribution to Zeppelin (Source code, Documents, Image, Website) means you agree license all your contributions as Apache2 License. - +Any contributions to Zeppelin (Source code, Documents, Image, Website) means you agree with license all your contributions as Apache2 License. +## Setting up +Here are some tools you will need to build and test Zeppelin. -### Setting up -Here are some things you will need to do to build and test Zeppelin. +#### Software Configuration Management ( SCM ) -#### Software Configuration Management(SCM) +Since Zeppelin uses Git for it's SCM system, you need git client installed in your development machine. -Zeppelin uses Git for it's SCM system. Hosted by github.com. `https://github.com/apache/incubator-zeppelin` You'll need git client installed in your development machine. - -#### Integrated Development Environment(IDE) +#### Integrated Development Environment ( IDE ) You are free to use whatever IDE you prefer, or your favorite command line editor. -#### Build Tools +### Build Tools To build the code, install -Oracle Java 7 -Apache Maven + + * Oracle Java 7 + * Apache Maven -### Getting the source code -First of all, you need the Zeppelin source code. The official location for Zeppelin is [https://github.com/apache/incubator-zeppelin](https://github.com/apache/incubator-zeppelin) +## Getting the source code +First of all, you need Zeppelin source code. The official location of Zeppelin is [http://git.apache.org/incubator-zeppelin.git](http://git.apache.org/incubator-zeppelin.git). -#### git access +### git access Get the source code on your development machine using git. ``` -git clone https://github.com/apache/incubator-zeppelin.git zeppelin +git clone git://git.apache.org/incubator-zeppelin.git zeppelin ``` -You may also want to develop against a specific release. For example, for branch-0.1 +You may also want to develop against a specific branch. For example, for branch-0.5.6 ``` -git clone -b branch-0.1 https://github.com/apache/incubator-zeppelin.git zeppelin +git clone -b branch-0.5.6 git://git.apache.org/incubator-zeppelin.git zeppelin ``` - #### Fork repository - -If you want not only build Zeppelin but also make changes, then you need to fork Zeppelin repository and make pull request. - +If you want not only build Zeppelin but also make any changes, then you need fork [Zeppelin github mirror repository](https://github.com/apache/incubator-zeppelin) and make a pull request. ###Build @@ -67,7 +64,7 @@ mvn install -DskipTests To build with specific spark / hadoop version ``` -mvn install -Dspark.version=1.0.1 -Dhadoop.version=2.2.0 +mvn install -Dspark.version=x.x.x -Dhadoop.version=x.x.x ``` ### Run Zeppelin server in development mode @@ -76,7 +73,8 @@ mvn install -Dspark.version=1.0.1 -Dhadoop.version=2.2.0 cd zeppelin-server HADOOP_HOME=YOUR_HADOOP_HOME JAVA_HOME=YOUR_JAVA_HOME mvn exec:java -Dexec.mainClass="org.apache.zeppelin.server.ZeppelinServer" -Dexec.args="" ``` -NOTE: make sure you first run ```mvn clean install -DskipTests``` on your zeppelin root directory otherwise your server build will fail to find the required dependencies in the local repro + +> **Note:** Make sure you first run ```mvn clean install -DskipTests``` on your zeppelin root directory, otherwise your server build will fail to find the required dependencies in the local repro. or use daemon script @@ -84,15 +82,13 @@ or use daemon script bin/zeppelin-daemon start ``` - -Server will be run on http://localhost:8080 - +Server will be run on [http://localhost:8080](http://localhost:8080). ### Generating Thrift Code -Some portions of the Zeppelin code are generated by [Thrift](http://thrift.apache.org). For most Zeppelin changes, you don't need to worry about this, but if you modify any of the Thrift IDL files (e.g. zeppelin-interpreter/src/main/thrift/*.thrift), then you also need to regenerate these files and submit their updated version as part of your patch. +Some portions of the Zeppelin code are generated by [Thrift](http://thrift.apache.org). For most Zeppelin changes, you don't need to worry about this. But if you modify any of the Thrift IDL files (e.g. zeppelin-interpreter/src/main/thrift/*.thrift), then you also need to regenerate these files and submit their updated version as part of your patch. -To regenerate the code, install thrift-0.9.0 and change directory into Zeppelin source directory. and then run following command +To regenerate the code, install **thrift-0.9.0** and change directory into Zeppelin source directory. and then run following command ``` @@ -100,10 +96,10 @@ thrift -out zeppelin-interpreter/src/main/java/ --gen java zeppelin-interpreter/ ``` -### JIRA +## JIRA Zeppelin manages its issues in Jira. [https://issues.apache.org/jira/browse/ZEPPELIN](https://issues.apache.org/jira/browse/ZEPPELIN) -### Stay involved +## Stay involved Contributors should join the Zeppelin mailing lists. * [[email protected]](http://mail-archives.apache.org/mod_mbox/incubator-zeppelin-dev/) is for people who want to contribute code to Zeppelin. [subscribe](mailto:[email protected]?subject=send this email to subscribe), [unsubscribe](mailto:[email protected]?subject=send this email to unsubscribe), [archives](http://mail-archives.apache.org/mod_mbox/incubator-zeppelin-dev/) http://git-wip-us.apache.org/repos/asf/incubator-zeppelin/blob/0d4c3acc/docs/development/howtocontributewebsite.md ---------------------------------------------------------------------- diff --git a/docs/development/howtocontributewebsite.md b/docs/development/howtocontributewebsite.md index 90a7367..2cefab8 100644 --- a/docs/development/howtocontributewebsite.md +++ b/docs/development/howtocontributewebsite.md @@ -5,62 +5,51 @@ description: "How to contribute (website)" group: development --- -## IMPORTANT +# Contributing to Apache Zeppelin ( Website ) +## IMPORTANT Apache Zeppelin (incubating) is an [Apache2 License](http://www.apache.org/licenses/LICENSE-2.0.html) Software. Any contribution to Zeppelin (Source code, Documents, Image, Website) means you agree license all your contributions as Apache2 License. +## Modifying the website -### Modifying the website - - -<br /> #### Getting the source code Website is hosted in 'master' branch under `/docs/` dir. -First of all, you need the website source code. The official location of mirror for Zeppelin is [https://github.com/apache/incubator-zeppelin](https://github.com/apache/incubator-zeppelin). +First of all, you need the website source code. The official location of mirror for Zeppelin is [http://git.apache.org/incubator-zeppelin.git](http://git.apache.org/incubator-zeppelin.git). Get the source code on your development machine using git. ``` -git clone https://github.com/apache/incubator-zeppelin.git +git clone git://git.apache.org/incubator-zeppelin.git cd docs ``` -<br /> #### Build -To build, you'll need to install some prerequisites. - -Please check 'Build' section on [docs/README.md](https://github.com/apache/incubator-zeppelin/blob/master/docs/README.md#build) +To build, you'll need to install some prerequisites. Please check 'Build documentation' section in [docs/README.md](https://github.com/apache/incubator-zeppelin/blob/master/docs/README.md#build-documentation). -<br /> #### Run website in development mode -While you're modifying website, you'll want to see preview of it. - -Please check 'Run' section on [docs/README.md](https://github.com/apache/incubator-zeppelin/blob/master/docs/README.md#run) +While you're modifying website, you'll want to see preview of it. Please check 'Run website' section in [docs/README.md](https://github.com/apache/incubator-zeppelin/blob/master/docs/README.md#run-website). -You'll be able to access it on localhost:4000 with your webbrowser. +You'll be able to access it on [http://localhost:4000](http://localhost:4000) with your web browser. -<br /> -#### Pull request +#### Making a Pull Request -When you're ready, just make a pull-request. +When you are ready, just make a pull-request. -<br /> -### Alternative way +## Alternative way You can directly edit .md files in `/docs/` dir at github's web interface and make pull-request immediatly. -<br /> -### JIRA +## JIRA Zeppelin manages its issues in Jira. [https://issues.apache.org/jira/browse/ZEPPELIN](https://issues.apache.org/jira/browse/ZEPPELIN) -### Stay involved +## Stay involved Contributors should join the Zeppelin mailing lists. * [[email protected]](http://mail-archives.apache.org/mod_mbox/incubator-zeppelin-dev/) is for people who want to contribute code to Zeppelin. [subscribe](mailto:[email protected]?subject=send this email to subscribe), [unsubscribe](mailto:[email protected]?subject=send this email to unsubscribe), [archives](http://mail-archives.apache.org/mod_mbox/incubator-zeppelin-dev/) http://git-wip-us.apache.org/repos/asf/incubator-zeppelin/blob/0d4c3acc/docs/install/virtual_machine.md ---------------------------------------------------------------------- diff --git a/docs/install/virtual_machine.md b/docs/install/virtual_machine.md index f210740..f72ae1e 100644 --- a/docs/install/virtual_machine.md +++ b/docs/install/virtual_machine.md @@ -22,11 +22,11 @@ limitations under the License. ## Vagrant Virtual Machine for Apache Zeppelin -The Apache Zeppelin distribution includes a scripts directory +Apache Zeppelin distribution includes a scripts directory `scripts/vagrant/zeppelin-dev` -This script creates a virtual machine that launches a repeatable, known set of core dependencies required for developing Zeppelin. It can also be used to run an existing Zeppelin build if you don't plan to build from source. For pyspark users, this script also includes several helpful [Python Libraries](#pythonextras) +This script creates a virtual machine that launches a repeatable, known set of core dependencies required for developing Zeppelin. It can also be used to run an existing Zeppelin build if you don't plan to build from source. For pyspark users, this script also includes several helpful [Python Libraries](#pythonextras). ####Installing the required components to launch a virtual machine. @@ -34,19 +34,22 @@ This script requires three applications, [Ansible](http://docs.ansible.com/ansib ### Create a Zeppelin Ready VM in 4 Steps (5 on Windows) -*If you are running Windows and don't yet have python installed, install Python 2.7.x* [Python Windows Installer](https://www.python.org/downloads/release/python-2710/) +If you are running Windows and don't yet have python installed, [install Python 2.7.x](https://www.python.org/downloads/release/python-2710/) first. 1. Download and Install Vagrant: [Vagrant Downloads](http://www.vagrantup.com/downloads) -2. Install Ansible: [Ansible Python pip install](http://docs.ansible.com/ansible/intro_installation.html#latest-releases-via-pip) -`sudo easy_install pip` then -`sudo pip install ansible` -`ansible --version` should now report version 1.9.2 or higher +2. Install Ansible: [Ansible Python pip install](http://docs.ansible.com/ansible/intro_installation.html#latest-releases-via-pip) + + ``` + sudo easy_install pip + sudo pip install ansible + ansible --version + ``` + After then, please check whether it reports **ansible version 1.9.2 or higher**. + 3. Install Virtual Box: [Virtual Box Downloads](https://www.virtualbox.org/ "Virtual Box") 4. Type `vagrant up` from within the `/scripts/vagrant/zeppelin-dev` directory -Thats it! - -You can now run `vagrant ssh` and this will place you into the guest machines terminal prompt. +Thats it ! You can now run `vagrant ssh` and this will place you into the guest machines terminal prompt. If you don't wish to build Zeppelin from scratch, run the z-manager installer script while running in the guest VM: @@ -55,18 +58,17 @@ curl -fsSL https://raw.githubusercontent.com/NFLabs/z-manager/master/zeppelin-in ``` - ### Building Zeppelin -You can now `git clone https://github.com/apache/incubator-zeppelin.git` into a directory on your host machine, or directly in your virtual machine. +You can now `git clone git://git.apache.org/incubator-zeppelin.git` into a directory on your host machine, or directly in your virtual machine. -Cloning zeppelin into the `/scripts/vagrant/zeppelin-dev` directory from the host, will allow the directory to be shared between your host and the guest machine. +Cloning Zeppelin into the `/scripts/vagrant/zeppelin-dev` directory from the host, will allow the directory to be shared between your host and the guest machine. -Cloning the project again may seem counter intuitive, since this script likley originated from the project repository. Consider copying just the vagrant/zeppelin-dev script from the zeppelin project as a stand alone directory, then once again clone the specific branch you wish to build. +Cloning the project again may seem counter intuitive, since this script likley originated from the project repository. Consider copying just the vagrant/zeppelin-dev script from the Zeppelin project as a stand alone directory, then once again clone the specific branch you wish to build. Synced folders enable Vagrant to sync a folder on the host machine to the guest machine, allowing you to continue working on your project's files on your host machine, but use the resources in the guest machine to compile or run your project. _[(1) Synced Folder Description from Vagrant Up](https://docs.vagrantup.com/v2/synced-folders/index.html)_ -By default, Vagrant will share your project directory (the directory with the Vagrantfile) to `/vagrant`. Which means you should be able to build within the guest machine after you +By default, Vagrant will share your project directory (the directory with the Vagrantfile) to `/vagrant`. Which means you should be able to build within the guest machine after you `cd /vagrant/incubator-zeppelin` @@ -74,7 +76,7 @@ By default, Vagrant will share your project directory (the directory with the Va Running the following commands in the guest machine should display these expected versions: -`node --version` should report *v0.12.7* +`node --version` should report *v0.12.7* `mvn --version` should report *Apache Maven 3.3.3* and *Java version: 1.7.0_85* @@ -117,15 +119,15 @@ Comment out the `forward_port` line, and uncomment the `private_network` line in config.vm.network "private_network", ip: "192.168.51.52" ``` -`vagrant halt` followed by `vagrant up` will restart the guest machine bound to the IP address of `192.168.51.52`. -This approach usually is typically required if running other virtual machines that discover each other directly by IP address, such as Spark Masters and Slaves as well as Cassandra Nodes, Elasticsearch Nodes, and other Spark data sources. You may wish to launch nodes in virtual machines with IP Addresses in a subnet that works for your local network, such as: 192.168.51.53, 192.168.51.54, 192.168.51.53, etc.. +`vagrant halt` followed by `vagrant up` will restart the guest machine bound to the IP address of `192.168.51.52`. +This approach usually is typically required if running other virtual machines that discover each other directly by IP address, such as Spark Masters and Slaves as well as Cassandra Nodes, Elasticsearch Nodes, and other Spark data sources. You may wish to launch nodes in virtual machines with IP addresses in a subnet that works for your local network, such as: 192.168.51.53, 192.168.51.54, 192.168.51.53, etc.. ### [Python Extras](id:pythonextras) -With zeppelin running, Numpy, SciPy, Pandas and Matplotlib will be available. Create a pyspark notebook, and try +With Zeppelin running, **Numpy**, **SciPy**, **Pandas** and **Matplotlib** will be available. Create a pyspark notebook, and try the below code. -``` +```python %pyspark import numpy @@ -139,9 +141,9 @@ print "pandas " + pandas.__version__ print "matplotlib " + matplotlib.__version__ ``` -To Test plotting using matplotlib into a rendered %html SVG image, try +To Test plotting using Matplotlib into a rendered `%html` SVG image, try -``` +```python %pyspark import matplotlib http://git-wip-us.apache.org/repos/asf/incubator-zeppelin/blob/0d4c3acc/docs/install/yarn_install.md ---------------------------------------------------------------------- diff --git a/docs/install/yarn_install.md b/docs/install/yarn_install.md index 2b38068..723291f 100644 --- a/docs/install/yarn_install.md +++ b/docs/install/yarn_install.md @@ -138,13 +138,13 @@ Zeppelin can work with multiple versions Spark. A complete list [is available he ## Build -Checkout source code from [https://github.com/apache/incubator-zeppelin](https://github.com/apache/incubator-zeppelin) +Checkout source code from [git://git.apache.org/incubator-zeppelin.git](git://git.apache.org/incubator-zeppelin.git). ```bash cd /home/zeppelin/ -git clone https://github.com/apache/incubator-zeppelin.git +git clone git://git.apache.org/incubator-zeppelin.git ``` -Zeppelin package is available at /home/zeppelin/incubator-zeppelin after the checkout completes. +Zeppelin package is available at `/home/zeppelin/incubator-zeppelin` after the checkout completes. ### Cluster mode http://git-wip-us.apache.org/repos/asf/incubator-zeppelin/blob/0d4c3acc/scripts/vagrant/zeppelin-dev/README.md ---------------------------------------------------------------------- diff --git a/scripts/vagrant/zeppelin-dev/README.md b/scripts/vagrant/zeppelin-dev/README.md index ffb7f23..6510f5f 100644 --- a/scripts/vagrant/zeppelin-dev/README.md +++ b/scripts/vagrant/zeppelin-dev/README.md @@ -24,9 +24,9 @@ This script requires three applications, [Ansible](http://docs.ansible.com/ansib *If you are running Windows and don't yet have python installed, install Python 2.7.x* [Python Windows Installer](https://www.python.org/downloads/release/python-2710/) 1. Download and Install Vagrant: [Vagrant Downloads](http://www.vagrantup.com/downloads) -2. Install Ansible: [Ansible Python pip install](http://docs.ansible.com/ansible/intro_installation.html#latest-releases-via-pip) -`sudo easy_install pip` then -`sudo pip install ansible` +2. Install Ansible: [Ansible Python pip install](http://docs.ansible.com/ansible/intro_installation.html#latest-releases-via-pip) +`sudo easy_install pip` then +`sudo pip install ansible` `ansible --version` should now report version 1.9.2 or higher 3. Install Virtual Box: [Virtual Box Downloads](https://www.virtualbox.org/ "Virtual Box") 4. Type `vagrant up` from within the `/scripts/vagrant/zeppelin-dev` directory @@ -45,7 +45,7 @@ curl -fsSL https://raw.githubusercontent.com/NFLabs/z-manager/master/zeppelin-in ### Building Zeppelin -You can now `git clone https://github.com/apache/incubator-zeppelin.git` into a directory on your host machine, or directly in your virtual machine. +You can now `git clone git://git.apache.org/incubator-zeppelin.git` into a directory on your host machine, or directly in your virtual machine. Cloning zeppelin into the `/scripts/vagrant/zeppelin-dev` directory from the host, will allow the directory to be shared between your host and the guest machine. @@ -53,7 +53,7 @@ Cloning the project again may seem counter intuitive, since this script likley o Synced folders enable Vagrant to sync a folder on the host machine to the guest machine, allowing you to continue working on your project's files on your host machine, but use the resources in the guest machine to compile or run your project. _[(1) Synced Folder Description from Vagrant Up](https://docs.vagrantup.com/v2/synced-folders/index.html)_ -By default, Vagrant will share your project directory (the directory with the Vagrantfile) to `/vagrant`. Which means you should be able to build within the guest machine after you +By default, Vagrant will share your project directory (the directory with the Vagrantfile) to `/vagrant`. Which means you should be able to build within the guest machine after you `cd /vagrant/incubator-zeppelin` @@ -61,7 +61,7 @@ By default, Vagrant will share your project directory (the directory with the Va Running the following commands in the guest machine should display these expected versions: -`node --version` should report *v0.12.7* +`node --version` should report *v0.12.7* `mvn --version` should report *Apache Maven 3.3.3* and *Java version: 1.7.0_85* @@ -104,7 +104,7 @@ Comment out the `forward_port` line, and uncomment the `private_network` line in config.vm.network "private_network", ip: "192.168.51.52" ``` -`vagrant halt` followed by `vagrant up` will restart the guest machine bound to the IP address of `192.168.51.52`. +`vagrant halt` followed by `vagrant up` will restart the guest machine bound to the IP address of `192.168.51.52`. This approach usually is typically required if running other virtual machines that discover each other directly by IP address, such as Spark Masters and Slaves as well as Cassandra Nodes, Elasticsearch Nodes, and other Spark data sources. You may wish to launch nodes in virtual machines with IP Addresses in a subnet that works for your local network, such as: 192.168.51.53, 192.168.51.54, 192.168.51.53, etc.. http://git-wip-us.apache.org/repos/asf/incubator-zeppelin/blob/0d4c3acc/scripts/vagrant/zeppelin-dev/show-instructions.sh ---------------------------------------------------------------------- diff --git a/scripts/vagrant/zeppelin-dev/show-instructions.sh b/scripts/vagrant/zeppelin-dev/show-instructions.sh index 6cfefbb..43bba76 100644 --- a/scripts/vagrant/zeppelin-dev/show-instructions.sh +++ b/scripts/vagrant/zeppelin-dev/show-instructions.sh @@ -18,7 +18,7 @@ echo '# Post vagrant up instructions.' echo '# From your host machine,' echo '# git clone the incubator-zeppelin branch into this directory' echo -echo 'git clone https://github.com/apache/incubator-zeppelin.git' +echo 'git clone git://git.apache.org/incubator-zeppelin.git' echo echo '# Cloning the project again may seem counter intuitive, since this script' echo '# originated from the project repository. Consider copying just the vagrant/zeppelin-dev'
