For using one single library asset directory for all nodes, there are two basic options currently afaik:
A) You have to relink the asset paths in library.mat manually to your network assets location primarily.
Then you can either roll out the changed library to all nodes (simple copy), you can still use the Corona material browser as it then uses the relinked paths.
Or you could use the relinked library (mat file + assets) just as a standard library centralised on your network. Using the Corona browser (with a local, unchanged library) will then result in locally linked assets of course - so it should/could not be used any more.
Hybrid: You copy the relinked library to your workstations only, slaves pick up the assets from the network and do not need to have installed anything of the library.
B) To symlink the complete Corona\material directory initially once on every node to a network location may be another solution (which works) - somehow I don't like the idea.
But if you want to just network render with the unchanged library and you don't fear to deploy the library to all nodes during installation, there should be no problem with network rendering even when local paths are used because lib + asssets should be the same everywhere. It's rather better because assets do not have to be transferred :) So the above is only for faster maintaining or if you want to adjust a few materials for your needs network wide.
Good Luck
Edit:
Btw: "About this forum" is definitely the wrong board to post this question :)
« Last Edit: 2017-10-26, 14:05:09 by Frood »
Logged
Never underestimate the power of a well placed level one spell.