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.
… 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: https://github.com/trilbymedia/grav-plugin-git-sync/issues/54 https://github.com/trilbymedia/grav-plugin-git-sync/issues/33 https://github.com/trilbymedia/grav-plugin-git-sync/issues/25