Other Plastic SCM is scary

I'm sure this is simple. But because I'm unfamiliar with how Plastic SCM works, I'm scared of losing all my work.

I have created a local Plastic SCM repo. It has been working fine. But now I have reached a point where I want to upload it to the server. I don't know how to do that. Much of the documentation online is old and in forums which cannot necessarily be relied upon.

So, I noticed my local repo was stored in 'default@local'. So I went to 'view repositories' and changed the name to something that is more relevant. Success!

YIKES! Heart attack! Now branch explorer says The specified repository couldn't be found: default.



Now I have to explore SCM to see how to get this working again. This is scary because I did something that I thought would be safe: 'rename' and it's not. So anything else I explore may not be safe or may move me further away from getting back to a working state.

All this because all I want to do is upload my repo to the cloud, but can't figure out how to do it.

 

I don't now exactly what 'user defined sync view' means. But it's the window that came up when I clicked 'sync to cloud'. I expected to 'sync to cloud.' Instead, what I got was a bunch of configuration.

Okay, so I tried Add src repo because that's what I want to do to the cloud server.

Instead, I got a new item: default@local instead of what I expected default@cloud.

So I must have done something wrong. So I should undo what I just did. But there's no undo. Instead I have the very scary option to potentially delete all my work: Delete src repo.

Does this mean destroy the actual src repo or delete the pointer to the src repo.

I don't know, thus I can't risk it.

More scariness: Delete src repo

 

What does dst repo and src repo mean anyway?

Which is which? is dst repo the cloud repo because it's the destination where I want to send my files to that destination? or is src repo the cloud repo because that's where the source code resides?

Online forums make it even worse by suggesting that this design choice is intentionally versatile so that you can switch the definitions whenever you want. So that right there tells me that danger! I should proceed cautiously because it is designed so that you could configure it wrong.

And thus, I probably would fail if I just guessed what dest repo and src repo are supposed to be because one option is designed to be just as good as another for the sake of versatility. If every binary choice allows me to configure it wrong, and I have already had 2 choices that I got wrong: rename and sync to cloud, then I don't have confidence that I can complete all of the choices from here until my goal is satisfied to be able to store my source code safely in the cloud.

 

Well, I've struggled with this for an hour. So I'm going with plan B--- backup to a local USB drive.

I do like Plastic SCM's features as a local source control management system. But if the process to backup and use this on a different computer is so much harder than making a copy to a USB drive, then I'm just going to do that.