Templates
🌟 Status: Live on Mainnet:
Templates may be kept private or submitted to be considered for listing as a public template. In the Network's boostrapping phase, the template contributor earns 20% of value of workload. This allows early template contributors to enjoy a significant incentive should their template prove popular.
Template overview​
Templates are the custom method to leverage NodeOps Cloud Compute, while the products and services are the NodeOps-provided entry point.
This means there are few boundaries constraining what you may create and consume from the Cloud Marketplace.
Templates state their resource requirements, currently, apps and code may be called via a public Docker image.
NodeOps is developing alternative methods for you to set up templates.
To consume your own template that leverages a bespoke app you must:
- Create a public Docker image of the app
- Create a template that leverages that Docker and upload it to the Marketplace
Template constraints​
- Maximum of 5 services.
- Only one service per template can be exposed to the public.
- Only 1 persistent volume is allowed.
- The total resource usage is limited to 4 Compute Units (CUs)
calculated as: CU = max(total CPU, total Memory)
- Upon template interruption, all services will be restarted as part of a single pod with multiple containers.
Update your Docker image​
To push out an updated version of your NodeOps template, push a new tag to your Docker image with the command:
docker push {username}/{template)name}:tagname
Then, from the NodeOps Marketplace console, navigate to My Templates and select your template, update the YAML version number and submit for re-review.