Search the Community
Showing results for tags 'cloud'.
Found 4 results
I'm evaluating Plastic Cloud Edition using Gluon as the front end. I've tried searching the web and forums to see if it is possible to manage access to individual cloud repositories but haven't been able to find any clear information. I'm interested specifically in the following: - Can you grant people access to specific repositories and not others? - Can access be restricted to read-only? - and if so how is this managed?
Hi, In trying out Plastic Cloud, I created a repository which I no longer need. I deleted this repo yesterday, but it still shows up in my Organization's usage details. Is there another step I need to take in order to reclaim the space? I'm currently on the 5GB plan so those 400MB are actually quite substantial.
Hi! I'm new to PlasticSCM and am setting up a new repository on the cloud service. I'm a developer using the PlasticSCM client proper, which is working fine... but when I set up Gluon for our artist, I'm getting weird errors. Several hundred files appear to be locked and checked out to the artist. The Check In option isn't available. And when we try Check Out, there's an error message saying "These items are exclusively checked out by [artist name]." Is there anyway to reset the checkouts on these files? Thanks, Brian
Hello everyone, I'm having a bit of a bother with Plastic when it comes to creating a new local workspace. I have created a cloud repo with no issues whatsoever. When I try to create a new local workspace, Plastic tells me that the 'workspace already' exists.. but for my existing workspace and not the new one. Plastic happily creates a new local folder and the same issue occurs if I choose an already existing local source folder. I've only got a single pre-existing workspace also linked to a cloud repo. The new one has nothing to do with the existing one. Perhaps someone could advise me as to a solution? Thanks Dan.