Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


Textstyles
Colorrgb(236,0,140)

WORK IN PROGRESS | Services are in active development and are subject to change.

 

When computing on Charity Engine, you virtually have a million CPU cores available right on your own machine. Tap into the power of the distributed network by following these three steps.


Textstyles
Size20px

Step 1

Get an account – To receive demo access to the Charity Engine Compute platform, contact us with a request and we will get it set up for you.


Textstyles
Size20px

Step 2

Set up your app – You can use the Remote CLI to run any docker image on Docker Hub. Craft a command line to run on a public image, or create your own custom image to run what you need.


Textstyles
Size20px

Step 3

Launch the Remote CLI – Once you have your app ready and an authorization key from Charity Engine, you can try a demonstration to see how it works:

Code Block
languagebash
$ ce-cli --app “docker:node” --commandline “echo \”2+2\” > /local/output/out.txt” --auth [KEY] local-file.txt
This command will create a job on the Charity Engine network that launches a docker container from the public image called node at DockerHub. The job will then run echo 2+2 > /local/output/out.txt inside of that container and the result will be written to your local machine in local-file.txt. Try adding the --debug flag to see more information.

Then, to scale this to hundreds or thousands of devices, see how to run in Parallel.

To learn more, full documentation is available on Computing with Charity Engine.

Info

The useOwnDevices flag is helpful for initial testing on a local device. 
This requires at least one of your devices to be running a Charity Engine client, attached with the same authorization key used to access the Remote CLI. For instructions on setting up the Charity Engine client, see Installing Charity Engine on Administered Resources.