<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: App development - few beginner questions in Splunk Dev</title>
    <link>https://community.splunk.com/t5/Splunk-Dev/App-development-few-beginner-questions/m-p/299842#M3850</link>
    <description>&lt;P&gt;Hi there!&lt;/P&gt;

&lt;OL&gt;
&lt;LI&gt;&lt;CODE&gt;debug/refresh&lt;/CODE&gt; is a great way to reload specific items of Splunk. By appending &lt;CODE&gt;&amp;amp;entity=admin/views&lt;/CODE&gt; or other similar entities, you can reload only a portion of Splunk, in this case views. I don't generally like to develop on a "non-cached" Splunk instance, it makes my page reloads too slow, a simple &lt;CODE&gt;_bump&lt;/CODE&gt; or &lt;CODE&gt;debug/refresh&lt;/CODE&gt; would do just find for most changes.&lt;/LI&gt;
&lt;LI&gt;Make sure they are &lt;CODE&gt;PNG&lt;/CODE&gt;, and are the exact sizes listed in that table. You can also stick them in &lt;CODE&gt;$APP_HOME/appserver/static&lt;/CODE&gt;. This is probably not needed, but IIRC, there are older versions of Splunk that look there as a back.&lt;/LI&gt;
&lt;LI&gt;Well, that, ... is just .... what? Ok, so you shouldn't need your app to consume a file from a location within the App. You should configure your app to have a sourcetype configuration, and instruct users to consume that file from anywhere, but with your custom sourcetype. Also, &lt;CODE&gt;data&lt;/CODE&gt; is not part of the folder structure. You should have any &lt;CODE&gt;conf&lt;/CODE&gt; file in &lt;CODE&gt;$APP_HOME/default&lt;/CODE&gt;. You are making the app, put the configs in &lt;CODE&gt;default&lt;/CODE&gt;.&lt;BR /&gt;&lt;/LI&gt;
&lt;/OL&gt;

&lt;P&gt;If this App is intended for distribution (ie SplunkBase), then  you need to read up on some best practices on app dev. If you find me on Slack (splk.it/slack), I'm &lt;CODE&gt;alacercogitatus&lt;/CODE&gt;, and I do app dev. We have a channel #appdev, that we can help with narrowing down your problems and help to resolve them. Thanks!&lt;/P&gt;</description>
    <pubDate>Mon, 02 Apr 2018 13:02:23 GMT</pubDate>
    <dc:creator>alacercogitatus</dc:creator>
    <dc:date>2018-04-02T13:02:23Z</dc:date>
    <item>
      <title>App development - few beginner questions</title>
      <link>https://community.splunk.com/t5/Splunk-Dev/App-development-few-beginner-questions/m-p/299841#M3849</link>
      <description>&lt;P&gt;hello fellow splunker.&lt;/P&gt;

&lt;P&gt;i am new to splunk and just starting to learn the basics about the app development.&lt;/P&gt;

&lt;P&gt;i have a few questions and topics i would appreciate your help with and hope that somebody can help me.&lt;/P&gt;

&lt;UL&gt;
&lt;LI&gt;first, i am wondering if there is no other way to "deploy" the changes i made to the app-files than calling &lt;A href="http://localhost:8000/de-DE/debug/refresh" target="_blank"&gt;http://localhost:8000/de-DE/debug/refresh&lt;/A&gt; everytime i make changes. i tried to adjust cache settings in web.conf, e.g. cacheEntriesLimit and cacheBytesLimit, which didn't happen to work.&lt;/LI&gt;
&lt;LI&gt;second, i couldn't get a custom app-icon to work. i placed the images $SPLUNK_HOME/etc/apps/your_app_name/static/ as described here [&lt;A href="http://dev.splunk.com/view/webframework-developapps/SP-CAAAE86" target="_blank"&gt;http://dev.splunk.com/view/webframework-developapps/SP-CAAAE86&lt;/A&gt;], restarted splunk...unfortunately without success.&lt;/LI&gt;
&lt;LI&gt;last, i am wondering how to automatically add a data-file (e.g. $SPLUNK_HOME/etc/apps/your_app_name/local/data/thedata.txt) when the app is first started. i have a custom props.conf, indexes.conf and inputs.conf with [monitor://....] in $SPLUNK_HOME/etc/apps/your_app_name/local/data, props and indexes are included in the $SPLUNK_HOME/etc/apps/your_app_name/metadata/local.meta but now i am struggeling to actually get the data, the inputs.conf, into splunk.&lt;/LI&gt;
&lt;/UL&gt;

&lt;P&gt;i appreciate every help or hint, where to find the solution.&lt;/P&gt;

&lt;P&gt;thank you very much&lt;/P&gt;</description>
      <pubDate>Tue, 29 Sep 2020 18:45:15 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Dev/App-development-few-beginner-questions/m-p/299841#M3849</guid>
      <dc:creator>didhavn</dc:creator>
      <dc:date>2020-09-29T18:45:15Z</dc:date>
    </item>
    <item>
      <title>Re: App development - few beginner questions</title>
      <link>https://community.splunk.com/t5/Splunk-Dev/App-development-few-beginner-questions/m-p/299842#M3850</link>
      <description>&lt;P&gt;Hi there!&lt;/P&gt;

&lt;OL&gt;
&lt;LI&gt;&lt;CODE&gt;debug/refresh&lt;/CODE&gt; is a great way to reload specific items of Splunk. By appending &lt;CODE&gt;&amp;amp;entity=admin/views&lt;/CODE&gt; or other similar entities, you can reload only a portion of Splunk, in this case views. I don't generally like to develop on a "non-cached" Splunk instance, it makes my page reloads too slow, a simple &lt;CODE&gt;_bump&lt;/CODE&gt; or &lt;CODE&gt;debug/refresh&lt;/CODE&gt; would do just find for most changes.&lt;/LI&gt;
&lt;LI&gt;Make sure they are &lt;CODE&gt;PNG&lt;/CODE&gt;, and are the exact sizes listed in that table. You can also stick them in &lt;CODE&gt;$APP_HOME/appserver/static&lt;/CODE&gt;. This is probably not needed, but IIRC, there are older versions of Splunk that look there as a back.&lt;/LI&gt;
&lt;LI&gt;Well, that, ... is just .... what? Ok, so you shouldn't need your app to consume a file from a location within the App. You should configure your app to have a sourcetype configuration, and instruct users to consume that file from anywhere, but with your custom sourcetype. Also, &lt;CODE&gt;data&lt;/CODE&gt; is not part of the folder structure. You should have any &lt;CODE&gt;conf&lt;/CODE&gt; file in &lt;CODE&gt;$APP_HOME/default&lt;/CODE&gt;. You are making the app, put the configs in &lt;CODE&gt;default&lt;/CODE&gt;.&lt;BR /&gt;&lt;/LI&gt;
&lt;/OL&gt;

&lt;P&gt;If this App is intended for distribution (ie SplunkBase), then  you need to read up on some best practices on app dev. If you find me on Slack (splk.it/slack), I'm &lt;CODE&gt;alacercogitatus&lt;/CODE&gt;, and I do app dev. We have a channel #appdev, that we can help with narrowing down your problems and help to resolve them. Thanks!&lt;/P&gt;</description>
      <pubDate>Mon, 02 Apr 2018 13:02:23 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Dev/App-development-few-beginner-questions/m-p/299842#M3850</guid>
      <dc:creator>alacercogitatus</dc:creator>
      <dc:date>2018-04-02T13:02:23Z</dc:date>
    </item>
  </channel>
</rss>

