holochain-proto | Holographic storage for distributed applications | Blockchain library

Developers Only: At this stage, holochain is only for use by developers (either developers of applications to run on holochains, or developers of the holochain software itself). App developers should bundle their app in an installer as either approach below is not for non-technical folks.
as a standard Go language application for direct execution on your machine
using docker for execution in a container.
Download the most recent release (https://github.com/holochain/holochain-proto/releases/) for your OS.
Unzip it to your directory of choice (or compile it from source).
Add that directory to your PATH if you want to call holochain-proto commands outside of that directory (this step differs by OS).
The commands listed in the 'Usage' section should now be available.
(Unix includes macOS and Linux.). First you'll need to install some necessary programs if you don't already have them.
Download Go. Download the "Archive" or "Installer" for version 1.8 or later for your CPU and OS. The "Source" download does not contain an executable and step 3 will fail.
Install Go on your system. See platform specific instructions and hints below for making this work.
Setup your path (Almost all installation problems that have been reported stem from skipping this step.) Export the $GOPATH variable in your shell profile. Add $GOPATH/bin to your $PATH in your shell profile. For example, add the following to the end of your shell profile (usually ~/.bashrc or ~/.bash_profile):
Install the command line tool suite with:
Test that it works (should look something like this):
Download Go. Download the "Archive" or "Installer" for version 1.8 or later for Windows and your CPU. The "Source" download does not contain an executable.
Install Windows git. Be sure to select the appropriate options so that git is accessible from the Windows command line.
Optional: Install GnuWin32 make.
Add a new entry with the name GOPATH and the value %USERPROFILE%\go (Or your Go workspace folder).
Double-click Path, and in the window that pops up add the following entries: %GOPATH%\bin C:\Go\bin (Or wherever you installed Go to+\bin). C:\Program Files (x86)\GnuWin32\bin (Or wherever you installed GnuWin32 make to+\bin).
Using docker, you don't have to install Go first. Our docker scripts manage installation of Go, holochain dependencies and holochain. The docker installation can run alongside Local ("Go") installation of holochain, sharing config directories. See docker usage on our wiki for more on how this works.
Install the latest version of Docker on your machine Docker Installation. The Community edition; stable is sufficient. See Docker Getting Started for help. It is recommended to add your user to the docker group as in: Post Installation Steps, rather than use sudo before all script commands. Holochain Apps cannot exploit the kinds of security concerns mentioned in the Post Installation Steps document.  
Confirm that docker installation and permissions are working by running: $ docker info
Pull our holochain image from docker hub: $ docker pull holochain/holochain-proto:develop
To run holochain in your new environment, suitable to continue the walkthrough below in usage $ docker run --rm -it --name clutter -p 3141:3141 holochain/holochain-proto:develop
This will put you into an new command shell that may behave differently than what you're used to. To exit this holochain (Alpine) shell, press Ctrl-D or type exit
The instructions below walk you through the basic steps necessary to run a holochain application. This command creates a ~/.holochain directory for storing all chain data, along with initial public/private key pairs based on the identity string provided as the second argument. You can use the hcadmin tool to join a pre-existing Holochain application by running the following command (replacing SOURCE_PATH with a path to an application's DNA and CHAIN_NAME with the name you'd like it to be stored as). For example: hcadmin join ./examples/chat chat. Note: this command will be replaced by a package management command still in development.
Once you have followed the basic "getting started" guide above you will have the CLI tools installed locally.