How brender work internally and other technical remarks - oenvoyage/brender GitHub Wiki

Home • Features development • FAQ • Technical remarks

There are 4 main components:

1. the database

Tthis is where all the information is stored : the list of all available clients, the projects, server settings and jobs.

2. the brender_server.php script

This is the main php script that will check clients, and job to be rendered. It will then dispatch rendering task to idle clients. To do so it will add a render order to the orders table. This order will have a rem that is the actual blender command line to be run in background mode (rem includes the path to the .blend file and the path to the output)

3. the brender_client.php script

Is run by a client. it will loop through the orders until it finds one that is adressed to himself. orders can be of type enable,disable, render, benchmark etc. 
Once this order is executed, the brender_client.php will erase that order(as it is finished)

4. the web interface

Is the main place for managing your renders. You can add, pause or restart jobs, check that everything runs fine and verify your images.

The render order syntax :

Basically it is the following : $blender_path -b $project_blend_path/$scene/$shot.blend -o $project_output_path/$scene/$shot0001.$FORMAT -P $config.py -s $current -e $current+($chunk*$number_of_processors) -a

for more informations on the blender command line please check the official blender wiki