SVN+SSH Tunneling - Checking Out Files in Editor
I have a project that is source controlled through SVN on a private server that I own. I have a team of about 20-30 users that need access to the SVN. I have the access figured out by using SSH key authentication through one master SVN account on the server. The tunneled user shows up as the team member's name when they commit through Tortoise and it works great.
The way the repository is organized is that in the main trunk I have an Engine folder which is the compiled release build off of GitHub and my project directory as well as an Assets folder which holds uncompressed art assets.
The problem comes in when users try to check out files within the Editor using the built-in SVN source control. I followed the answer submitted by muchcharles on another thread linked (here) and got the editor to recognize the connection with source control however because the access is managed by one user account I think it doesn't quite understand who is checking out what. Every time that I attempt to checkout an asset within the editor, it gives an error (Unable to check out file) and then proceeds to lock the asset with the correct tunneled user name; however with a blue check and a lock. The only work around that I've been able to figure out is to make the file writable and then commit via Tortoise but that kinda defeats the purpose.
asked Jan 14 '17 at 09:30 AM in Everything Else
The way I have it setup is multiple users on the svn host, and then they are all in a unix group that has write permissions on the repository. Make sure you follow svn instructions on using the "sticky" bit on the repo to preserve the group permissions.
answered Jan 14 '17 at 11:27 PM
Follow this question
Once you sign in you will be able to subscribe for any updates here