4 ms·
This is true for git, too. However, I don't know of any git command like "svn export" that doesn't also pull the .git directory. The working solution seems to b
by motoko 18y ago
This is true for git, too. However, I don't know of any git command like "svn export" that doesn't also pull the .git directory. The working solution seems to be to simply delete the .git directory after a clone ---preferably in some nice deploy script --- in conjunction with appropriate *nix file and Apache permissions.
- ionfish 18y agoThe .git directory, however, is top-level, rather than in every directory in your repository, so it'll only be a problem if your site root is the same as your repository root.
- reconbot 18y agoIf the server is ever exploited then they have all your revision history (including anything accidentally checked in that you didn't rebase(?) out) but you do have the added advantage of being able to quickly check for any modifications to any of your code. My repo's follow a /public /logs/ /app so with git (over svn) none of the repo is exposed.