Kurono

Ok... so i found that there is a way. If i comment all the branches i want to sync with "main branch" or similar. I can just write "main branch" in the filter and then use the Push/Pull Visible buttons, which will only sync the filtered branches (only the branches with the comment). The only issue i'm finding with this workflow is that the filter is not saved. I way forget to add the filter one day and accidentally sync all the branches. Although, i don't think it will happen, but still there's that concern.

Hello, What i'm trying to do is to only sync the /main branch to a remote repo (due to size concerns, because many binary files are involved). In the future i may also want to sync more branches (only "/main" and "/main/v2" for example). In the image below, i know i could just exclude ".../TestBranch1" and ".../TestBranch2". The problem is that i need to do that process each time i create a new branch. So, is there a simpler way to sync only certain branches (/main in this case)?

I believe this is what you need: https://www.plasticscm.com/documentation/administration/plastic-scm-version-control-administrator-guide#Chapter17:Transformableworkspaces Although it would be cool to be able to work with only certain parts of the repo just like perforce handles it with their GUI, and to be able to see the repo and the folders/files before downloading them (and selecting which folders/files are going to be downloaded).

There's a guihelp-dontshowagain.conf file in /user/myuser/appdata/local/plastic/. I guess if you get that file from someone who has all the list of ignored tips, you could disable them all.

Hello, i'm not really a security expert but i found a possible security issue that could be exploited (although most of the responsibility here relies in the plastic server admin of the company). So, while i was testing plastic server on linux (on a Digital Ocean server) for the company i work for, i was unable to connect to the Web Admin Tool for some reason. So i decided to do all the settings manually by modifying the server .conf files (i'm also pretty sure that many people setup the server this way, specially if they have the production-ready .conf files lying around). The possible security issue i'm talking about is that even if i can't access to the web admin tool, doesn't really mean that anyone else can't. So someone could access, generate a password, reset a repo user password and create havok in the repos. Since setting up or using the Web Admin Tool isn't mandatory for running up the server, i believe that an initial password should be generated (unencrypted initially, until prompted a password change in the first visit) OR setting up a Web Admin Tool password should be a mandatory process when installing the server. So, of course, one solution here is to disable the Web Admin Tool (in the server.conf file) and also copy a webadmin.conf generated from other machine, just in case.