Plastic Cloud is an extension to Team Edition.
It is the perfect way to synchronize multiple teams running Plastic SCM servers on-premise.
Plastic can encrypt files before uploading to the Cloud for total security. You are the only owner of the keys.
You can host gigabytes of data in your Plastic Cloud repositories without issues.
2 GB is not the limit here. Plastic supports big files and huge repo sizes by design. Plastic Cloud starts with 15GB and grows as you need.
Plastic Cloud is designed for teams who need private repos in the cloud on a safe way.
You can setup your Plastic Cloud organization to use encrypted data. Data will always be encrypted in the cloud and only decrypted on your computers.
Developers will take advantage of the push/pull workflow while team members using Plastic Gluon can go for a simpler direct checkin cycle.
The familiar push/pull way of working. The option of choice if you work with code.
Just checkin your changes. No intermediate repos. No push and pull. The best option for artists in games (together with Plastic Gluon). Also available for coders who want to work centralized.
You can select where your data is stored. The closest to you, the fastest the data transfer is going to be.
It is very simple:
Besides a Plastic Cloud subscription (which includes the cloud server plus storage) you need a valid Plastic SCM license to use Plastic Cloud. This is because you need the actual client tools (GUIs, integrations with IDEs, merge, and so on) which come with Team, Enterprise, Personal or Community Editions. Find more details in the FAQ.
Then, there are different setups you can use with Plastic Cloud:
Direct checkin will be the workflow typically used by artists in game development and team members who don’t work in code but documents, plans and so on.
They can now simply continue using Plastic Gluon and checkin directly to Plastic Cloud.
Each developer works on his machine, from his home office. They both belong to the same Plastic Cloud organization and deliver changes to Plastic Cloud through push/pull. Each of them has his own local Plastic SCM repo (or collection of repositories) so that checkins are always local and blazing fast.
Direct checkin will be the workflow typically used by developers working on code.
They can now simply continue using Plastic SCM and checkin directly to Plastic Cloud.
The members of each team directly checkin or push/pull to their own team server. Then team servers are synchronized using Plastic Cloud as rendezvous point, instead of requiring one of the servers to be accessible through the internet.
Using the Plastic Cloud server is just like using a regular Plastic server. The only extra step is that we added an extra layer on it: organizations. An organization is a way to group repositories for a given team or company.
Steps to work with Plastic Cloud:
Please note that we’re using robotmaker@cloud as the server name, where robotmaker is your organization name.
This is actually the only change to keep in mind while using the cloud server. Normally you use servers like myserver:8087, but in the cloud you use <org_name>@cloud, no need to specify the address or the port.
By the way, all commands work using organizations at the cloud: you can try this to list your repos:
cm lrep <org_name>@cloud
