d0mokun

Hello! I want to change the name of my Cloud organisation, however when I do so the system stops working. Any function (push, pull) performed within a workspace takes ages and then returns an error about the host closing the connection. Changing the name back to the original one makes it all work again. I've tried modifying the ServerProfiles lines in profiles.conf and it had no effect. How do I change the organisation name and still maintain the ability to use workspaces? Thanks Dan.

Evening all, I'm trying to do an initial push but I keep getting this error: The server "server@cloud" requires encryption, but your server is not configured with the encryption key. To configure your local server make sure you become the admin of the server (owner), try again and you will be asked to enter encryption key. Otherwise, ask your sysadmin or search 'Encrypt all data' in the online docu. Searching that term in the online documentation yields nothing. Search yields nothing. Please help! Best Dan.

Hi Manu, Certainly. Thanks!

Hi Manu, cm mkwk wkTest c:\Users\Dan\wkspaces\Test The above didn't work. The command seemed to execute and the folder created, though no change in SCM. It still says the workspace already exists for the previous project. Thanks Dan.

Hi Manu, The result of that command is KehuaMap@PIXL-HUDSON c:\Users\Dan\wkspaces\KehuaMap I'm attempting to create the directory outside of the above one, indeed it already exists. Even if I use the workspace tool to create a new folder, it gives the same error. Thanks Dan.

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.