topic Re: What should be in my .gitignore for a new app/add-on? in Splunk Dev

What should be in my .gitignore for a new app/add-on?

Wilcooley — Mon, 06 Feb 2012 22:08:14 GMT

I'm importing an unmaintained app into my own git repo (there is no upstream, AFAICT) and there are a handful of files that are generated and should be ignored in any working copy?

This is what I have so far for my .gitignore:

local/
metadata/local.meta
# Maybe?
viewstates.conf
# This is added automatically when the app is uploaded, isn't it?
default/MANIFEST

What else?

I realize this is probably somewhere in the documentation, but it's probably spread over several different sources.

Re: What should be in my .gitignore for a new app/add-on?

bmacias84 — Tue, 12 Aug 2014 22:02:33 GMT

So we use git for all configuration files and apps for splunk. Here's what we decided on.



*.DS_Store

*local.meta

*.csv

*.pyo

*.idea

!<some_static_lookup>.csv

.csv - is ignored if any search are generating lookups
.pyo - any pythongenerated files
local.meta - since this is updated by deployment server
!.csv - include any static lookups
.idea- since we work on macs
DS_Store - since we work on macs

Hope this helps