In this chapter, we will cover how to publish our App on Splunkbase, the community for Splunk developers. We will discuss the process step by step, and any caveats that may arise. We will talk about Certified Applications, and what that means to you as an App developer. We will also start a discussion on communities, and why the community is important in the culture of Splunk, as well as around the globe.
Then we will see some links and references to other commonly used Splunk resources, such as the Splunk Wiki and the Splunk documentation (which you should already be familiar with). Finally, we will hit upon Splunk user groups, how to find a group, and what to expect.
The first method of publishing an App is by doing it yourself. This can mean that you are storing the data, keeping the App under control, and generally excluding Splunkbase altogether. This is a good methodology, especially when you are trying to monetize your App on a per-license basis. Splunkbase doesn't have a methodology for restricting downloads, other than for export reasons. Really, if you don't use Splunkbase, you can publish your App anywhere, and as long as people find it and download it, it is published. There are many different ways to share your App. These are just a few: Apache/IIS web server, Amazon S3, and Dropbox. It's a short list, not meant to be comprehensive, but just enough to give you ideas on where to publish and display your App.