4 ms·
Why are you pushing files with rsync with a working copy? That is what "export" is for. There is no special security in the .svn folder, because you are not s
by miratom 18y ago
Why are you pushing files with rsync with a working copy? That is what "export" is for. There is no special security in the .svn folder, because you are not supposed to publish it to the website.
- agotterer 18y agoTo be perfectly honest I'm not sure if its an rsync or a checkout. I'm not the sys admin or the person who set up the process. But doing an export makes sense, that was something I was thinking about after I discovered this. Thanks for the confirmation. Regardless, this problem exists and it exists on some extremely large websites.
- joeyo 18y agoYou seem to have made a mistake with the rewrite rule. I think you mean: RewriteRule (\.svn)/(.*?) - [F,L] Note the backslash before the .svn directory. I'm also not entirely sure that the question mark (zero or one quantifier) is necessary; it seems like (.*) would suffice for catching files within the .svn directory, but this is quickly getting out of my league.
- agotterer 18y agoYour right, I forget to transcribe the backslash (its correct in my htaccess). I will update the article. Thanks!
- brianr 18y agorsync is fine, just make sure to exclude .svn and anything else you don't want the world to see, for example: cd $build_dir svn co path/to/project rsync -qaz -c --delete --exclude=.svn project $host:/var/www
- dreur 18y ago+1
- agotterer 18y agoI mentioned this to our sys admin. He made a good point... Export will copy every file in the repository over, every time. Our repo is quite large and we push often. We use rsync so it only copies the most recent changes. They also go out to a number of servers.