golocity 0.0.1

Building the images

Before your project can be deployed on the Network, we must first build the docker image as well as the Golem virtual machine image. Before issuing the command, make sure you have Docker installed and running on your computer.

To do so, use the build command:

golocity build /path/to/your/project

This will build the requisite images as well as create a .golocity directory in your projects directory. This directory holds configuration files needed by Golocity as well as logs.

The build command also pushes the Golem virtual machine image to the Network’s public repository. To preform a dry-run, append the --info flag to the command.

Under the hood, Golocity parses your Dockerfile for ENTRYPOINT and CMD commands. These commands currently are not supported in the Golem virtual machine format, so Golocity removes them and manually calls them from within the deploy command. Don’t worry, Golocity will not alter your project files, it only operates on temporary copies.

Deploying to the Network

Once you have successfully built and pushed the images, you are ready to deploy your project on the Network! First, make sure you have the yagna daemon running on your machine, for more information, refer to the Golem Handbook.

Now, deploying is one line away!

golocity deploy [budget]

Replace budget with the limit of what to spend while running the project. From here Golocity will handle the rest. It will find the best provider and handle the output.

Poetry

We use poetry to manage dependencies, to get started follow these steps:

git clone https://github.com/davidstyers/golocity
cd golocity
poetry install
poetry run pytest

Pre-Commit

We have a configuration for pre-commit to add the hook run the following command:

pre-commit install