Yes you can!
Configure the "repo_addresses=" in "splunkgit.conf" to be the absolute local path to your local git repository.
I.e: repo_addresses=/Users/petterik/developer/local_project
Read more on configuration here, then try it out!
Let me know if you have any problems by either replying here or creating a github issue.
- Petter, dev for splunkgit
Yes you can!
Configure the "repo_addresses=" in "splunkgit.conf" to be the absolute local path to your local git repository.
I.e: repo_addresses=/Users/petterik/developer/local_project
Read more on configuration here, then try it out!
Let me know if you have any problems by either replying here or creating a github issue.
- Petter, dev for splunkgit
I found that there was a bug with egrep on some platforms, which resulted in no data at all:
You might want to try the new version: http://splunk-base.splunk.com/apps/34028/splunkgit
Too get more detail on what's happnening:
You can do a search for "index=_internal fetch_git*" and you should see what's happening to the script that's indexing the git repository.
You can see something like what exit status it had, error message or (if successful) how much data was indexed
I'm still not having luck with it... I've tried both:
repo_addresses=/applData/backups/netconfig/.git
and repo_addresses=/applData/backups/netconfig
The first is the bare repository whereas the second is the local copy containing the repository:
[server]# ls -a /applData/backups/netconfig/
. .. files .git
I simply don't see any data indexed. Is there anything I can do to get more detail on what's happening?