Examples of how to use your own Golem image in a requestor script
Introduction
Golem images define a remote environment where you execute tasks. They are identified either by their tags
or by a hash
. You can read more about Golem images in Golem Images Explained guide.
Prerequisites
Yagna service is installed and running with try_golem
app-key configured.
This example has been designed to work with the following environments:
- OS X 10.14+, Ubuntu 20.04 or Windows
- Node.js 16.0.0 or above
How to run examples
Create a project folder, initialize a Node.js project, and install the @golem-sdk/golem-js
library.
mkdir golem-example
cd golem-example
npm init
npm install @golem-sdk/golem-js
Copy the code into the index.mjs
file in the project folder and run:
node index.mjs
Using Golem images
Below you will find an example requestor script used in the QuickStart.
import { TaskExecutor } from "@golem-sdk/golem-js";
(async () => {
const executor = await TaskExecutor.create({
package: "529f7fdaf1cf46ce3126eb6bbcd3b213c314fe8fe884914f5d1106d4",
yagnaOptions: { apiKey: 'try_golem' }});
const result = await executor.run(
async (ctx) => (await ctx.run("node -v")).stdout);
await executor.end();
console.log("Task result:", result);
})();
Note the 529f7fdaf1cf46ce3126eb6bbcd3b213c314fe8fe884914f5d1106d4
hash in the line where TaskExecutor is created:
const executor = await TaskExecutor.create({
package: "529f7fdaf1cf46ce3126eb6bbcd3b213c314fe8fe884914f5d1106d4",
yagnaOptions: { apiKey: 'try_golem' }});
If you had created your custom Golem image and published it to the repository, you can simply replace the hash (529 [...] 1106d4
) in the script with the hash generated for your image by gvmkit-build tool or with your own defined tag.
package: "529f7fdaf1cf46ce3126eb6bbcd3b213c314fe8fe884914f5d1106d4",
or
package: "golem/my_example:latest",