Changes: run_info to get_system_load
Changes: Added more detailed information in README.md
Cleanup: Dashboard code organization
Added: Added condition if worker doesn’t exist then show response page instead of error
Small Changes:  Changes for worker page for refresh button / icon
Major Change: Settings page now changes setting and doesn’t error out if you only set one os path
Upgrades: upgraded to bootstrap 3.0.2

Added caching for run_often reason for it so you can spam the refresh button (more earlier on resources this way)

New Dependencies (psutil, gocept.cache)

Changed Readme.md to reflect new dependencies

Small Changes for job dispatching and shot completion

so that we get the correct color from CSS class.
problem : "enabled" doesnt seem to be a valid class, its jquery
keyword...

- removed the (enable/disable) buttons in each client row
- now you need to check a worker and enable an action.
- selecting mutliple workers and apply a batch action doesnt work
yet...
 + need to add refresh dataTable to show new status

Added if statement for shots that are completed

# By fsiddi
# Via fsiddi
* 'master' of https://github.com/fsiddi/brender:
  Upgrage to Boostrap 3

Several layout changes to make the current markup compatible with
Boostrap 3

Added if statement for shots that are completed

- Made workder report progress back to the server when rendering is over
- Hooked Shot start/stop buttons to the interface

For the moment we only specify the general Linux and OSX blender binary
path. Useful for testing render jobs code!

Changes for Indentation of files

Makes code cleaner and easier to read

Missing log files exception fix

# By Olivier Amrein
# Via Olivier Amrein
* 'master' of https://github.com/fsiddi/brender:
  run_command() rename + cleaning
  typo

Fixed issue with log being displayed

I renamed the function run_command() to render_chunk().
It can always be renamed later if needed
It can now get 3 arguments from the server : start, end, and
blendfile-path
I think it is the basic stuff we need for the moment.

after adding the system column we forgot to offset the fnUpdate to
column 5

right now I just do a javascript alert, it would be good to implement a
messaging system later ( a bit like flask.flash(), but on the html side.

WARNING: this commit requires the addition of a 'system' column in the
workers table.
When a worker is started we detect the operating system and the
version. This is useful for sending the right commands to workers later
via the server.

We use the request.remote_addr value to determine the request.
Apparently it's very hard to get the IP address of a machine
consistently on OSX and Linux. Probably there will be problems when we
work with non LAN IPs but for the moments it seems to work.

And the 'status' value gets carried up to the server.