Skip to content
The iExec pools registry, more below on how to list your Worker Pool!
Branch: master
Clone or download
Type Name Latest commit message Commit time
Failed to load latest commit information.
CloudAndHeat/Cloud&Heat Cloud and Heat Pool Add Jun 20, 2018
IBMCloud/IBMCloud IBMCloud pool add. Nov 21, 2018
Nerdalize/Nerdalize New Domains Jun 8, 2018
Qarnot/Qarnot fix readmes May 25, 2018
Stimergy/Stimergy New Domains Jun 8, 2018
TFCloud/TFCloud TFCloud update Feb 19, 2019
iExecBlockchainComputing Update iexec.json Oct 30, 2018 typo (#18) May 16, 2019
github-fork.png update readme May 25, 2018
github-pr.png update readme May 25, 2018
registry.json fix date Nov 21, 2018

iExec Pools Registry

In order to list your Worker Pool on the iExec Pool Registry, you need to make it into the iExec Pools Registry. But relax, it's very easy:

Once you created and deployed your iExec WorkerPool using the iExec SDK, here are the 5 steps that remain to enter this registry:

1. Github Fork this repo

click on the github "Fork" button and git clone the forked repository on your local machine.

github fork

2. Create 2 new folders

  • One organization folder at the root [MUST match your github user or github org name]. Ex: /iExecBlockchainComputing.

  • One folder for your pool inside your org folder [MUST match your pool name]. Ex: /iExecBlockchainComputing/MainPool.

3. Validate

Enter your pool folder, and run the below command to check its config:

  • iexec registry validate workerpool

4. Commit

Once the validation is successful, you can commit & push your pool config.

  • git add iexec.json deployed.json logo.png
  • git commit -m 'adding my MainPool workerpool'
  • git push

5. Github Pull Request

clic on this button to create a Pull Request (from your forked master branch TO iexec-pools-registry master branch):

github pull request

We'll review you Pool and if it meets all the above criteria, it will be added to the iExec Pool Registry!

You can’t perform that action at this time.