Plastic Remote AccessFor those of us who have worked on large scale software development across multiple sites and/or countries, you've probably come across ClearCase and ClearCase MultiSite. ClearCase MultiSite replicates a ClearCase VOB (repository) between installations. It makes clever use of e-mail to send differences between ClearCase servers. Engineers then simply access the replicated VOB as if it were held locally, in fact it is. All good stuff, but requires quite a bit of administration.
Plastic on the other hand doesn't support repository replication and doesn't need to. Simply access the repository from the remote client over TCP/IP. To do this we need to switch the Plastic server to use IP addresses for it's server name. Edit server.conf and add an entry <ServerName> IP addr </ServerName>. Then restart the Plastic service. Open port 8084 on your firewall(s). Ensure that the IP address you entered is an externally accessible address and not a LAN address. Then setup your router to forward port 8084 to the server.
On your clients re-run the client configuration tool and enter the server IP address. Of course, the client will have to open port 8084 on their network as well.
If the server is using Local Users authentication the user account names must match on the client and server. More extensive name serving can be performed with LDAP or Active Directory offering additional security.
I think you'll agree that Plastic is simple to setup for external access offering the benefits of low administration, centralized storage and remote client access over the Internet.