Sponsors
Sponsor Products
State of the art - Windows artist environments
posted by Michael Stein  on Feb. 21, 2018, 4:35 p.m. (5 years, 9 months, 9 days ago)
2 Responses     0 Plus One's     0 Comments  
Ive searched the archives and Slack and came up empty. 
Whats the current SSA state of the art for managing Artist environments under Windows? Im specific referring to controlling versions of software (both third-party and in-house) on a per project basis, e.g. setting your project, then starting an app, and getting the right version. 
Related to this question - how are people storing software? On central server mounted  as a drive or network share, or all local?
I have these problems and figure that this wheel has been invented. 

Thread Tags:
  discuss-at-studiosysadmins 

Response from Julian Firminger @ Feb. 22, 2018, 2:25 a.m.
+100 PDQ Deploy.Everything msi + regkeys scriptedWorks awesome.
On 22 Feb. 2018 01:00, "Dan Mons" <dmons@cuttingedge.com.au> wrote:
On 22 February 2018 at 07:57, Jean-Francois Panisset <panisset@gmail.com> wrote:
I've said this before, but the best "installer" is a zip file...

Amen to that! When will vendors ever learn?
-Dan

Thisemailis confidential and solely for the use of the intended recipient.If you have received thisemailin error please notify the author and delete it immediately. Thisemailis not to be distributed without the author's written consent.Unauthorised forwarding, printing, copying or use is strictly prohibited and may be a breach of copyright. Any views expressed in thisemailare those of the individual sender unless specifically stated to be the views ofCutting EdgePost Pty Ltd (Cutting Edge). Although thisemailhas been sent in the belief that it is virus-free, it is the responsibility of the recipient to ensure that it is virus free. No responsibility is accepted byCutting Edgefor any loss or damage arising in any way from receipt or use of thisemail. Thisemailmay contain legally privileged information and privilege is not waived if you have received thisemailin error.



To unsubscribe from the list send a blank e-mail to mailto:studiosysadmins-discuss-request@studiosysadmins.com?subject=unsubscribe

0 Plus One's     0 Comments  
   

Response from Jean-Francois Panisset @ Feb. 21, 2018, 5 p.m.
Most Windows apps can be installed locally, harvested and copied to and run off a network share (of course Adobe apps being a notable exception), but it seems that as a general rule the performance of running Windows apps off a network share is not very good: the same app version on Linux running off NFS from the same server will start up infinitely faster. So we wrote an in-house caching system that will make a local copy of "big / slow to start" apps (Houdini, Maya, Nuke...), and uses a LRU policy to keep the cache size reasonable while ensuring that "active" projects quickly find the app versions they need (this is useful on both artist workstations and render nodes). This allows you to freeze multiple projects to different app versions (through a Shotgun-based app launcher), and deal with apps that either want to install incremental updates on top of older versions, or have quick release cycles that would quickly fill the largest of local disks if you installed everything locally. I've said this before, but the best "installer" is a zip file... JF On Wed, Feb 21, 2018 at 1:30 PM, Michael Stein wrote: > Ive searched the archives and Slack and came up empty. > > Whats the current SSA state of the art for managing Artist environments > under Windows? Im specific referring to controlling versions of software > (both third-party and in-house) on a per project basis, e.g. setting your > project, then starting an app, and getting the right version. > > Related to this question - how are people storing software? On central > server mounted as a drive or network share, or all local? > > I have these problems and figure that this wheel has been invented. > > > To unsubscribe from the list send a blank e-mail to > mailto:studiosysadmins-discuss-request@studiosysadmins.com?subject=unsubscribe To unsubscribe from the list send a blank e-mail to mailto:studiosysadmins-discuss-request@studiosysadmins.com?subject=unsubscribe

0 Plus One's     0 Comments