Skip to content

Commit

Permalink
add more info to docs
Browse files Browse the repository at this point in the history
  • Loading branch information
peterskim12 committed Aug 10, 2016
1 parent 450d4b6 commit e0a6bfc
Showing 1 changed file with 20 additions and 0 deletions.
20 changes: 20 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -32,3 +32,23 @@ this in the Vagrant file.
* Run `vagrant up`

For more information on Vagrant, check out their [documentation](https://www.vagrantup.com/docs/).

## How to use

This is not a Vagrant tutorial; see their [docs](https://www.vagrantup.com/docs/) for more info.

Vagrant provides an elegant way to encapsulate dev environments. Once
you provision your Vagrant Elastic Stack environment, Elasticsearch and
Kibana are running and accessible at 192.168.56.5 on ports 9200 and 5601
respectively.

The /vagrant dir gets mounted automatically and is mapped to the directory
on your host containing the Vagrantfile. This makes it convenient to
place files such as Logstash configs, Elasticsearch index templates, raw
data files, etc. in the same dir as your Vagrantfile and execute Logstash
against those files by referencing them on the /vagrant mount.

Over time, as you work on different projects, just clone the elastic-base
project to another directory, place the project-specific files in that dir,
and you have an Elastic Stack environment specific for that project that
isn't muddled with configs and indexes from other projects.

0 comments on commit e0a6bfc

Please sign in to comment.