added documentation. some cleanup

Dockerfile.md

@@ -0,0 +1,19 @@
+## Aerospike Server Dockerfile
+
+This repository contains the Dockerfile for building a Docker image for running [Aerospike](http://aerospike.com). 
+
+## Dependencies
+
+- [ubuntu:14.04](https://registry.hub.docker.com/_/ubuntu/)
+
+## Installation
+
+1. Install [Docker](https://www.docker.io/).
+
+2. Download from public [Docker Registry](https://index.docker.io/):
+
+		docker pull aerospike/aerospike-server
+
+	_Alternatively, you can build an image from Dockerfile:_
+
+		docker build -t="aerospike/aerospike-server" github.com/aerospike/aerospike-server.docker

LICENSE

@@ -0,0 +1,13 @@
+Copyright 2014-2015 Aerospike, Inc.
+
+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.

README-short.txt

@@ -0,0 +1,3 @@
+Aerospike is an open source distributed database. Aerospike is built on a 
+"shared nothing" architecture designed to reliably stores terabytes of data 
+with automatic fail-over, replication and cross data-center synchronization.

README.md

@@ -1,92 +1,5 @@
-## Aerospike Server Dockerfile
-
-This repository contains the Dockerfile for [Aerospike](http://aerospike.com). 
-
-### Dependencies
-
-- [ubuntu:14.04](https://registry.hub.docker.com/_/ubuntu/)
-
-### Installation
-
-1. Install [Docker](https://www.docker.io/).
-
-2. Download from public [Docker Registry](https://index.docker.io/):
-
-		docker pull aerospike/aerospike-server
-
-	_Alternatively, you can build an image from Dockerfile:_
-
-		docker build -t="aerospike/aerospike-server" github.com/aerospike/aerospike-server.docker
-
-### Usage
-
-The following will run `asd` with all the exposed ports forward to the host machine.
-
-	docker run -tid --name aerospike -p 3000:3000 -p 3001:3001 -p 3002:3002 -p 3003:3003 aerospike/aerospike-server
-
-**NOTE** Although this is the simplest method to getting Aerospike up and running, but it is not the prefered method. To properly run the container, please specify an **custom configuration** with the **access-address** defined.
-
-### Advanced Usage 
-
-
-#### Custom Configuration
-
-By default, `asd` will use the configuration file in `/etc/aerospike/aerospike.conf`, which is added to the directory by the Dockerfile. To provide a custom configuration, you should first mount a directory containing the file using the `-v` option for `docker`:
-
-	-v <DIRECTORY>:/opt/aerospike/etc
-
-Where `<DIRECTORY>` is the path to a directory containing your custom configuration file. Next, you will want to tell `asd` to use a configuration file from `/opt/aerospike/etc`, by using the `--config-file` option for `aerospike/aerospike-server`:
-
-	--config-file /opt/aerospike/etc/aerospike.conf
-
-This will use tell `asd` to use the file in `/opt/aerospike/etc/aerospike.conf`, which is mapped to `<DIRECTORY>/aerospike.conf`.
-
-A full example:
-
-	docker run -tid -v <DIRECTORY>:/opt/aerospike/etc --name aerospike -p 3000:3000 -p 3001:3001 -p 3002:3002 -p 3003:3003 aerospike/aerospike-server --config-file /opt/aerospike/etc/aerospike.conf
-
-#### access-address Configuration
-
-In order for Aerospike to properly broadcast its address to the cluster or applications, the **access-address** needs to be set in the configuration file. If it is not set, then the IP address within the container will be used, which is not accessible to other nodes.
-
-To specify **access-address** in aerospike.conf:
-
-	network {
-	  service {
-	    address any                  # Listening IP Address
-	    port 3000                    # Listening Port
-	    access-address 192.168.1.100 # IP Address to be used by applications
-	                                 # and other nodes in the cluster.
-	  }
-	  ...
-
-
-#### Persistent Data Directory
-
-With Docker, the files within the container are not persisted. To persist the data, you will want to mount a directory from the host to the guest's `/opt/aerospike/data` using the `-v` option:
-
-	-v <DIRECTORY>:/opt/aerospike/data
-
-Where `<DIRECTORY>` is the path to a directory containing your data files.
-
-A full example:
-
-	docker run -tid -v <DIRECTORY>:/opt/aerospike/data --name aerospike -p 3000:3000 -p 3001:3001 -p 3002:3002 -p 3003:3003 aerospike/aerospike-server
-
-
-#### Clustering
-
-Aerospike recommends using multicast clustering whenever possible, however, we are currently working to figure out how to best support multicast via Docker. For the time being, it will be best to setup Mesh Clustering. We are open to pull-requests with proposals on how to implement multicast for our Dockerfile.
-
-##### Mesh Clustering
-
-Mesh networking requires setting up links between each node in the cluster. This can be achieved in two ways:
-
-1. Define a configuration for each node in the cluster, as defined in [Network Heartbeat Configuration](http://www.aerospike.com/docs/operations/configure/network/heartbeat/#mesh-unicast-heartbeat).
-
-2. Use `asinfo` to send the `tip` command, to make the node aware of another node, as defined in [tip command in asinfo](http://www.aerospike.com/docs/tools/asinfo/#tip).
-
-
-
+# About this Repo
 
+This is the Git repo of the official Docker image for [Aerospike](http://aerospike.com). See the Hub page for the full readme on how to use the Docker image and for information regarding contributing and issues.
 
+Documentation for Aerospike is available at http://aerospike.com/docs

USAGE.md

@@ -0,0 +1,72 @@
+# Using this Image
+
+The following will run `asd` with all the exposed ports forward to the host machine.
+
+  docker run -tid --name aerospike -p 3000:3000 -p 3001:3001 -p 3002:3002 -p 3003:3003 aerospike/aerospike-server
+
+**NOTE** Although this is the simplest method to getting Aerospike up and running, but it is not the prefered method. To properly run the container, please specify an **custom configuration** with the **access-address** defined.
+
+# Advanced Usage 
+
+
+## Custom Configuration
+
+By default, `asd` will use the configuration file in `/etc/aerospike/aerospike.conf`, which is added to the directory by the Dockerfile. To provide a custom configuration, you should first mount a directory containing the file using the `-v` option for `docker`:
+
+  -v <DIRECTORY>:/opt/aerospike/etc
+
+Where `<DIRECTORY>` is the path to a directory containing your custom configuration file. Next, you will want to tell `asd` to use a configuration file from `/opt/aerospike/etc`, by using the `--config-file` option for `aerospike/aerospike-server`:
+
+  --config-file /opt/aerospike/etc/aerospike.conf
+
+This will use tell `asd` to use the file in `/opt/aerospike/etc/aerospike.conf`, which is mapped to `<DIRECTORY>/aerospike.conf`.
+
+A full example:
+
+  docker run -tid -v <DIRECTORY>:/opt/aerospike/etc --name aerospike -p 3000:3000 -p 3001:3001 -p 3002:3002 -p 3003:3003 aerospike/aerospike-server --config-file /opt/aerospike/etc/aerospike.conf
+
+## access-address Configuration
+
+In order for Aerospike to properly broadcast its address to the cluster or applications, the **access-address** needs to be set in the configuration file. If it is not set, then the IP address within the container will be used, which is not accessible to other nodes.
+
+To specify **access-address** in aerospike.conf:
+
+  network {
+    service {
+      address any                  # Listening IP Address
+      port 3000                    # Listening Port
+      access-address 192.168.1.100 # IP Address to be used by applications
+                                   # and other nodes in the cluster.
+    }
+    ...
+
+
+## Persistent Data Directory
+
+With Docker, the files within the container are not persisted. To persist the data, you will want to mount a directory from the host to the guest's `/opt/aerospike/data` using the `-v` option:
+
+  -v <DIRECTORY>:/opt/aerospike/data
+
+Where `<DIRECTORY>` is the path to a directory containing your data files.
+
+A full example:
+
+  docker run -tid -v <DIRECTORY>:/opt/aerospike/data --name aerospike -p 3000:3000 -p 3001:3001 -p 3002:3002 -p 3003:3003 aerospike/aerospike-server
+
+
+## Clustering
+
+Aerospike recommends using multicast clustering whenever possible, however, we are currently working to figure out how to best support multicast via Docker. For the time being, it will be best to setup Mesh Clustering. We are open to pull-requests with proposals on how to implement multicast for our Dockerfile.
+
+### Mesh Clustering
+
+Mesh networking requires setting up links between each node in the cluster. This can be achieved in two ways:
+
+1. Define a configuration for each node in the cluster, as defined in [Network Heartbeat Configuration](http://www.aerospike.com/docs/operations/configure/network/heartbeat/#mesh-unicast-heartbeat).
+
+2. Use `asinfo` to send the `tip` command, to make the node aware of another node, as defined in [tip command in asinfo](http://www.aerospike.com/docs/tools/asinfo/#tip).
+
+
+
+
+