Thoric Posted September 17, 2013 Report Share Posted September 17, 2013 I've managed to keep Community scope by avoiding the password-protection features of VIPM, which is otherwise responsible for damaging the library (Known issue 13790). I now perform my own project cloning and password protection through a bit of scripting, and leave VIPM to just apply the license file. I really don't think I can live without Community scope in my toolkit, so this workaround will have to do 1 Quote Link to comment
Thoric Posted November 11, 2013 Report Share Posted November 11, 2013 Just to close this thread from my input. I've abandoned Community Scope. It was too much of a headache, and the inability to password protect everything safely has led to a need to revert to Public scope. A bit disappointing, but in the end I'll live. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.