I would be very worried if people got access to my SQL backupsTechie-Micheal wrote:and /store, don't worry about putting that in SVN as it contains SQL backups
Yeah.A_Jelly_Doughnut wrote:Evil<3: Micheal meant "don't spend the effort to put /store/ in SVN", not "don't worry about the effects of putting /store/ in SVN"
You should hear my double-speak. Yeah, I'm not even sure how I came up with such a paragraph going back and reading it again. Sorry about that.eviL<3 wrote:Ah, okay. That wasn't quite clear. My apologies
This is actually a really good idea and something I believe we may even implement for one of our sites (you get three guesses, and the first two don't count).Yautja_cetanu wrote:We've got a bunch of people managing one live board. Its got a bunch of mods we've developed or we're tweaking (when trying to fix problems for example).
So we're thinking of putting the entire live board's files up in a SVN repository that would be publically available. Obviously we won't put anything in cache, files, stores, images or config.php. But is this an issue? Are there any security issues we haven't thought about?
We have our own svn repository that's hosted on a server protected by a SSL layer (login required), so it's not open to the public.andrewbelcher wrote:Hey, I'm from the same boards... The idea isn't for people to download it pre-modded. The idea is that we can keep track of everything done to our live boards very easily, which would be useful as we develop our mods.
The problem is sourceforge (our SVN host) don't enable you to hide parts of the repositry, so they'd be live... The question is really are there any security problems with putting those files up there - does it pose any risk to data integrity or anything. The only files we could think might are config.php, /cache, /stores, /files and /images... Are there any others that put our boards at risk?