Arvados

h1. Arvbox

We recommend using "Arvbox":http://doc.arvados.org/install/arvbox.html to set up self-contained Arvados development environment.

h2. Running Arvados in development mode

<pre>

$ arvbox reboot dev

</pre>

This performs the following operations:

# Rebuild the arvbox-dev docker image (typically the layers are cached so this is a no-op unless you are working on arvbox itself)

# Create @~/.arvbox/arvbox@ to store arvbox state

# Clone the arvados git repository to @~/.arvbox/arvbox/arvados@

# Place stateful container data in @~/.arvbox/arvbox/postgres@ and @~/.arvbox/arvbox/var@

# Start the container

The container will then:

# Download and cache various packages (Ruby gems, Passenger)

# Compile and install Arvados server binaries

# Build and install Arvados SDK packages (such as arvados-python-client)

# Start the Arvados services

The directories inside @~/.arvbox/arvbox@ are all bind-mounted inside the container.  This means that you may edit files on the host file system and the changes will be seen inside the container immediately.  For example, if you edit a page template in @~/.arvbox/arvbox/arvados/apps/workbench/app/views@ you only need to reload the page in your browser to see the change.

You can restart individual services without restarting the whole container.  For compiled server programs, the startup script always recompiles the server before starting it.  For example, if you are working on @keepproxy@

<pre>

$ arvbox sv restart keepproxy

</pre>

If any service fails to come up, you can see the debug log using @arvbox log@.  This log will include compilation or install errors:

<pre>

$ arvbox log keepproxy

</pre>

Finally, you can get a root shell inside the container using @arvbox sh@

<pre>

$ arvbox sh

</pre>

h2. Running the test suite

Arvbox can also be used to run the Arvados test suite in an isolated manner.

<pre>

$ arvbox restart test

</pre>