Grouper Users - Open Discussion List

[John Gasper <>]

Thanks Chris and Andy. Flexibility is good always good as everyone's
situation is different, but I do think that there should really be a
standard (RFC, etc) set for skinning cats, huh? :)

On 2/20/15 11:47 AM, Chris Hyzer wrote:
> Yeah, we have 4 UI and WS servers at Penn... I patch one and rsync the 
> webapp dir to the others.  I agree that patching individual servers is not 
> ideal :)  But I hear you on wanting to build... theres a jira :)
>
> Thanks,
> Chris
>
> -----Original Message-----
> From: Andrew Morgan 
> [mailto:]
>  
> Sent: Friday, February 20, 2015 2:45 PM
> To: Chris Hyzer
> Cc: John Gasper; 
> 
> Subject: RE: [grouper-users] patching the UI with grouperInstaller
>
> On Fri, 20 Feb 2015, Chris Hyzer wrote:
>
>> There are pros and cons to both approaches… Im not saying there is no 
>> value in your approach, but with the current strategy you can patch a UI 
>> without having to do another build.  Therefore only a very small change 
>> will be made to the system which reduces risk in my opinion.  You don’t 
>> have to worry about doing a build and overwriting a prior patch or doing 
>> something else unintended.  I don’t think one is best, if the current 
>> way fits in your deployment model, I think you will have less risk.  If 
>> not, then you have to do it the other way ☺  This isn’t a trivial 
>> change, will need to look into it.
>>
>> https://bugs.internet2.edu/jira/browse/GRP-1113
> I can see both ways being useful, maybe at different scales or deployment 
> models.  Here at OSU we have 2 frontend servers.  I prefer to patch the 
> base directory and then build the WAR.  That way I can deploy an identify 
> WAR on both servers.  I'd like the patches and the upgrades to work the 
> same way.
>
> Thanks,
>       Andy