How to avoid storage of _sgbak in the working folder?

[HansMerkl]

Hi,

I am trying to use Vault for my website. The data is in a folder tree that gets traversed whenever a user requests something.

Now the problem is that each time I modify a file and check it in, Vault creates a folder called _sgbak in the working folder. This additional directory also gets traversed and subsequently the web site doesn't work properly.

Can I configure Vault in way that _sgbak doesn't get created or at least outside the working folder?

Thanks

Hans

[dan]

By default, Vault backs up files that are either edited or unknown before overwritting them, and it backs them up in the _sgbak folder. Unfortunately, you can't currently specify a different location for the backup folder, but you can turn it off so that it doesn't back the files up at all.

Go to Tools->Options->Local Files and uncheck "Save files in backup folder before overwriting"

[HansMerkl]

Dan,

Thanks. That should work.


Hans

[mwoffenden]

Will there be an option for this in the future?

[dan]

This is on our list, but we don't have a targetted release for it yet. We'll add your vote to it though.

[matzen]

add +1 for me

[Snowdevil]

Add my vote for this as well. It's actually quite annoying having a gazillion little _sgbak folders everywhere. I understand the importance of the job they're doing, but surely this job could be done from one base folder instead? I just had to go through a project structure in Visual Studio without about 300 folders and manually exclude each _sgbak folder one-by-one from the project. Very very tedious. It's also annoying went you want to upload a web folder structure because you have to either put up with an irrelevant set of _sgbak folders in your production environment or somehow work out how to exclude them from the upload.

I am totally in favour of a single [ProjectRoot]\_sgbak\[EVERYTHING GOES HERE][/i]

[stephen]

You shouldn't ever include sgbak folders into a websolution. so then if you deploy from the ide to another webserver sgbak folders are irrelevant.
I don't find sgbak folders problematic. They server a very good purpose.

[dsellers]

There is a program called Unleash It which will FTP your files to your webserver and has easy to use filters that will filter out those _sgbak folders. you can find it at http://www.eworldui.net/UnleashIt/

[Sean Malloy]

You can always make a copy of the webapp, into a new location, do a search for "_sgbak" folders in Windows explorer, and delete all of them in one foul swoop. Then deploy the copy of the version. Pretty easy

[Sean Malloy]

Oh and +1 vote for me for specifying the location of the _sgbak folder. I'd set it to C:\TEMP, which I wipe on boot.

[lbauer]

Vault 3.1, due out later this spring will let you choose where to store the Vault client cache files and the _sgbak folder.

You'll also have the option NOT to save files in the backup folder. The state or baseline files (_sgvault) will need to be either in the working folder or the client cache folder.