JanetGilbert Posted January 23, 2019 Report Share Posted January 23, 2019 How do I set up the cloud edition so that artists can use exclusive locks but coders don't have to? I want it to give an error if a developer tries to push a checkin to the server that tries to change a file that an artist has checked out. Is this possible? I see a lot of references to lock.conf in the documentation, but I'm not sure if this is needed for the cloud. I've set up the cloud admin page to have lock rules for the repository in question, but it didn't create a lock.conf file on disk... was it meant to? Link to comment Share on other sites More sharing options...
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!Register a new account
Already have an account? Sign in here.Sign In Now