Skip to content
This repository has been archived by the owner on Jul 21, 2024. It is now read-only.

HOWTO: Setup provider: Your own render farm (local)

Jump to bottom
Rabit edited this page Oct 20, 2023 · 19 revisions

If you reached this point - it seems like you need to use your own resources. So be prepared - even using the easiest way you still will need to put some efforts to squeeze out the last drop of performance from your setup.

Video reference:

Task execution

First of all you need to understand the basics of how the tasks are executed on the BlendNet cluster:

Small execution process diagram

Ways to go

There is a number of ways to setup your own render farm, so we prepared a nice step-by-step documentation for you.

Windows cluster

If you're prefer to use Windows - we have a special verbose documentation for you:

Linux/MacOS cluster

If you're an automation engineer or just loves to use Linux or MacOS - this tough one will suit your needs:

Advanced

If you got it working - probably you want to know more about how to configure your render farm.

  • You can add the manager.json file with your own configs to the Manager workspace directory, like this one: 
    {
  "name": "my-turbo-blendnet-manager",
  "ip": "<IP OR NS TO OVERRIDE THE resources Manager IP>",
  "internal_ip": "<IP OR NS TO OVERRIDE THE resources Manager INTERNAL_IP>",
  "listen_host": "",
  "listen_port": 8443,
  "auth_user": "<MANAGER USER>",
  "auth_password": "<MANAGER PASSWORD>",
  "agent_listen_port": 9443,
  "agent_auth_user": "None",
  "agent_auth_password": "None",
  "agent_upload_workers": 4
}
  • You can add the agent.json file with your own configs to the Agent workspace directory, like this one: 
    {
  "listen_host": "",
  "listen_port": 9443,
  "auth_user": "<AGENT USER>",
  "auth_password": "<AGENT PASSWORD>"
}
  • If you're looking for the automation - check those documents, it will describe how to automate your system:
Clone this wiki locally