NOTE: This repo has now been merged into holochain-rust
This repo provides a set of tools for building and running Holochain DNA from the command line. The tools are written in Rust, and delivered as binary executables.
Our recommended pattern for the installation of hc command line tools is to use the Developer Preview release that you can find here, along with its instructions: https://github.com/holochain/app-spec-rust/releases/tag/v0.0.1-dev-preview. Otherwise, you can proceed with the more complex instructions for building from source, below.
These dependencies need to be installed in order to compile, and use holochain-cmd:
- Rust
- needs to be the
nightlybuild, so use the following commands, once you have first installed Rust rustup toolchain install nightlyrustup default nightly- Also, if you are going to be developing Zomes in Rust, install the WASM build target for Rust, by running:
rustup target add wasm32-unknown-unknown --toolchain nightly
- needs to be the
- Node.js (needed for running tests)
- hcshell (also needed for running tests, hcshell is currently installed as part of holosqape)
To install the Holochain command line, run the following commands in a terminal
$ git clone https://github.com/holochain/holochain-cmd.git
$ cd holochain-cmd
$ git submodule init
$ git submodule update
$ cargo install -f --path .The command line tools are now available in your command line using the hc command.
Run hc -V to confirm.
Run hc help for help.
(u) means the command is not yet implemented.
| Command | Use |
|---|---|
| init | Initializes a new Holochain app at the given directory |
| generate | Generates a new Zome |
| package | Builds the current Holochain app into a .dna.json file |
| unpack | Unpacks a Holochain bundle into its original file system structure |
| test | Runs tests written in the test folder |
| web (u) | Starts a web server for the current Holochain app |
| agent (u) | Starts a Holochain node as an agent |
In your terminal, change directories to one where you wish to initialize a new Holochain app.
Run the following, replacing your_app_name with your actual app name:
$ hc init your_app_name
$ cd your_app_nameWe now have the empty shell of a Holochain app. From here, we will want to generate at least one Zome.
To do this, run the following, replacing your_zome_name with a name related to the functionality you wish to develop. For example: users.
$ hc generate zomes/your_zome_nameCurrently, only Zomes written in Rust can be generated. In the future, you may be able to generate Zomes in another language. hc generate scaffolds the files and config you need to get started.
What this did is generate a new folder under zomes called users. Here is the folder structure of it.
- users
- code
- src
- lib.rs
- .build
- Cargo.toml
- src
- code
So in every Zome there must be a code folder, which can be compiled into a single WASM binary with the code for this Zome.
Now that you have your Rust Zome, check out the two sources of documentation about writing Holochain DNA source code:
In order for Holochain to run your app, you have to build your code into a single packaged file. Those instructions follow.
Holochain DNA can be fully contained in a file known as a .dna.json file.
It is a JSON file, with a particular structure that Holochain can understand, and execute.
This is an unusual JSON file; it is part configuration, and part executable.
The configuration part comes from the json file at the top level of your source code.
The executable part comes from having embedded Base64 encoded WebAssembly code in the file. What does that mean? WebAssembly is a fast and secure low-level language. Rather than storing the code in its ugly raw WASM bytecode format, Holochain expects the code to be encoded using Base64 , for legibility and simplicity reasons.
If you haven't heard of WebAssembly (WASM for short), that's ok. Important to know is that WASM is intended as a "compilation target" for other languages, not a language to write code in. So instead of writing code in WASM, write code in a language that's familiar to you, and supports WASM. When it's time to run your code in Holochain, compile it.
In order to avoid having to handcraft this complex JSON structure, with lots of room for error, the hc package command streamlines the process of taking your "raw" application folder, and packaging it up into the final .dna.json file.
More information about this follows.
The hc package tool will automate the process of compiling your Zome code, encoding it, and inserting into the .dna.json file. In order to get these benefits, you just need to make sure that you have the right compilation tools installed on the machine you are using the command line tools from, and that you have the proper configuration files in your Zome folders.
hc package works with two special files called .hcignore files and .build files.
In the process of building a .dna.json file, here is what Holochain does.
- It iterates Zome by Zome adding them to the JSON
- For each Zome, it looks for any folders containing a
.buildfile - For any folder with a
.buildfile, it executes one or more commands from the.buildfile to create a WASM file - It takes that built WASM file and Base64 encodes it, then stores a key/value pair for the Zome with the key as the folder name and the encoded WASM as the value
When using hc generate to scaffold a Zome, you will have a .build file automatically. If you create your Zome manually however, you will need to create the file yourself. Here's the structure of a .build file, using a Rust Zome which builds using Cargo as an example:
{
"steps": {
"cargo": [
"build",
"--release",
"--target=wasm32-unknown-unknown"
]
},
"artifact": "target/wasm32-unknown-unknown/release/code.wasm"
}The two top level properties are steps and artifact. steps is a list of commands which will be sequentially executed to build a WASM file. artifact is the expected path to the built WASM file. Under steps, each key refers to the bin of the command that will be executed, such as cargo. The value of cargo, the command, is an array of arguments: build, and the two -- flags. In order to determine what should go here, just try running the commands yourself from a terminal, while in the directory of the Zome code.
Sometimes, you'll want to exclude files and folders in your project directory to get a straight .dna.json file that can be understood by Holochain. In order to do that, just create a .hcignore file. It has a similar structure to .gitignore files:
README.md
dist
.DS_Store
The package command includes patterns inside .gitignore files automatically, so you don't have to write everything twice. Also hidden files are ignored by default as well.
If we take Zome code in Rust as an example, you will need Rust and Cargo set up appropriately to build WASM from Rust code. WASM compilation is available on the nightly Rust toolchain. To enable it, run the following:
$ rustup toolchain install nightly
$ rustup target add wasm32-unknown-unknown --toolchain nightly # adds WASM as a compilation target
$ rustup default nightly # switch to the nightly rust toolchain as your defaultOnce that's done, you should be able to run commands like cargo build --target=wasm32-unknown-unknown and have it work.
Once all of this is set up, you can build and run your .dna.json file with Holochain!
By default, when you use hc init to create a new project folder, it creates a sub-directory called test. The files in that folder are equipped for testing your project.
Checkout the README of our default testing configuration to understand how to write your tests in Javascript: https://github.com/holochain/js-tests-scaffold.
Once you have a project folder initiated, you can run hc test to execute your tests. This combines the following steps:
- Packaging your files into a DNA file, located at
dist/bundle.json. This step will fail if your packaging step fails. - Installing build and testing dependencies, if they're not installed (
npm install) - Building a single JS file used for testing, placed at
test/dist/bundle.js(npm run build) - Executing (with hcshell) the test file found at
test/dist/bundle.js
hc test also has some configurable options.
If you want to run it without repackaging the DNA, run it with
hc test --no-packageIf you want to run it without running the npm commands, run it with
hc test --skip-npmIf your tests are in a different folder than test, run it with
hc test --dir testswhere tests is the name of the folder.
If the file you wish to actually execute is somewhere besides test/dist/bundle.js then run it with
hc test --testfile test/test.jswhere test/test.js is the path of the file.
You have the flexibility to write tests in quite a variety of ways, open to you to explore.
Note about default configuration with TAPE testing: If you use the default configuration with Tape for testing, to get an improved CLI visual output (with colors! and accurate script exit codes), we recommend adjusting the command you use to run tests as follows:
hc test | test/node_modules/faucet/bin/cmd.js
Holochain is an open source project. We welcome all sorts of participation and are actively working on increasing surface area to accept it. Please see our contributing guidelines for our general practices and protocols on participating in the community.
Copyright (C) 2018, Holochain Trust
This program is free software: you can redistribute it and/or modify it under the terms of the license p rovided in the LICENSE file (GPLv3). This program is distributed in the hope that it will be useful, bu t WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Note: We are considering other 'looser' licensing options (like MIT license) but at this stage are using GPL while we're getting the matter sorted out. See this article for some of our thinking on licensing for distributed application frameworks.