Browsing about this topic I found that if you have an application at the top of your stack with a configuration outside of /etc you can also store it's configuration in the etckeeper repository, to make commits to both application, stack and system configuration in the same changesets in the same repo:
I understand however that if your repo gets to be too big, you can run etckeeper vcs gc if you're using git, and if it gets way too big you can get rid of the changes using etckeeper uninit.
Also I believe that it's also possible to use something like sshfs to mount a share on another machine if you wish to keep the etckeeper repo somewhere else where it won't take up so much space on the production server.
Browsing about this topic I found that if you have an application at the top of your stack with a configuration outside of /etc you can also store it's configuration in the etckeeper repository, to make commits to both application, stack and system configuration in the same changesets in the same repo:
https://www.turnkeylinux.org/forum/support/20151207/using-git-store-server-configuration
However, I still have some questions on this if you know anything about them:
http://unix.stackexchange.com/questions/249785/how-do-i-know-when-what-i-should-store-in-my-external-to-etc-configuraitons-in
http://unix.stackexchange.com/questions/250216/what-directory-does-etckeeper-store-its-permissions-meta-data-in
I understand however that if your repo gets to be too big, you can run
etckeeper vcs gcif you're using git, and if it gets way too big you can get rid of the changes usingetckeeper uninit.Also I believe that it's also possible to use something like sshfs to mount a share on another machine if you wish to keep the etckeeper repo somewhere else where it won't take up so much space on the production server.
This is a pretty good post too: http://rsabalburo.blogspot.com/2011/09/sysadmin-guide-to-using-git-and.html