Make consistent usage of repositoryPath in GitSync class and make the… #95
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
… repository path configurable.
Background of this is, that by making the repository path of the sync directory configurable, you can define a path like: user/git-sync
This way, the content repo is outside the user root, which in many cases is part of a global git repo. Moving the pages directory (and any other directory defined in "folders" of git-sync) to this custom defined git-sync directory and adding symlinks to the user directory itself to keep Grav running seems a solid solution to this for me.
You will end up with smth. linke that:
/
/user/pages -> symlink to /user/git-sync/pages
/user
/user/git-sync
/user/git-sync/pages
But that only works by changing the repository path of git-sync.
Similar issues have been discussed in:
#54
#33
#25