Difference between revisions of "Appdata Directory Misc"
Bakerboy448 (talk | contribs) (→Arguments: add args) |
Bakerboy448 (talk | contribs) m (→Arguments: typos) |
||
Line 5: | Line 5: | ||
The <code>-data</code> argument forces the location of the AppData folder, so your startup command may be forcing a specific location. This is especially useful when trying to run multiple instances. | The <code>-data</code> argument forces the location of the AppData folder, so your startup command may be forcing a specific location. This is especially useful when trying to run multiple instances. | ||
− | The <code>-nobrowser</code>argument refrains from launching/opening the browser on startup. | + | The <code>-nobrowser</code> argument refrains from launching/opening the browser on startup. |
<section end=radarr_appdata_directory_arguments /> | <section end=radarr_appdata_directory_arguments /> | ||
Line 12: | Line 12: | ||
The <code>-data</code> argument forces the location of the AppData folder, so your startup command may be forcing a specific location. This is especially useful when trying to run multiple instances. | The <code>-data</code> argument forces the location of the AppData folder, so your startup command may be forcing a specific location. This is especially useful when trying to run multiple instances. | ||
− | The <code>-nobrowser</code>argument refrains from launching/opening the browser on startup. | + | The <code>-nobrowser</code> argument refrains from launching/opening the browser on startup. |
<section end=sonarr_appdata_directory_arguments /> | <section end=sonarr_appdata_directory_arguments /> | ||
Line 19: | Line 19: | ||
The <code>-data</code> argument forces the location of the AppData folder, so your startup command may be forcing a specific location. This is especially useful when trying to run multiple instances. | The <code>-data</code> argument forces the location of the AppData folder, so your startup command may be forcing a specific location. This is especially useful when trying to run multiple instances. | ||
− | The <code>-nobrowser</code>argument refrains from launching/opening the browser on startup. | + | The <code>-nobrowser</code> argument refrains from launching/opening the browser on startup. |
<section end=lidarr_appdata_directory_arguments /> | <section end=lidarr_appdata_directory_arguments /> | ||
=== Readarr === | === Readarr === | ||
Line 25: | Line 25: | ||
The <code>-data</code> argument forces the location of the AppData folder, so your startup command may be forcing a specific location. This is especially useful when trying to run multiple instances. | The <code>-data</code> argument forces the location of the AppData folder, so your startup command may be forcing a specific location. This is especially useful when trying to run multiple instances. | ||
− | The <code>-nobrowser</code>argument refrains from launching/opening the browser on startup. | + | The <code>-nobrowser</code> argument refrains from launching/opening the browser on startup. |
<section end=readarr_appdata_directory_arguments /> | <section end=readarr_appdata_directory_arguments /> |
Revision as of 17:34, 21 February 2021
Misc page for Appdata Directory
Arguments
Radarr
The -data
argument forces the location of the AppData folder, so your startup command may be forcing a specific location. This is especially useful when trying to run multiple instances.
The -nobrowser
argument refrains from launching/opening the browser on startup.
Sonarr
The -data
argument forces the location of the AppData folder, so your startup command may be forcing a specific location. This is especially useful when trying to run multiple instances.
The -nobrowser
argument refrains from launching/opening the browser on startup.
Lidarr
The -data
argument forces the location of the AppData folder, so your startup command may be forcing a specific location. This is especially useful when trying to run multiple instances.
The -nobrowser
argument refrains from launching/opening the browser on startup.
Readarr
The -data
argument forces the location of the AppData folder, so your startup command may be forcing a specific location. This is especially useful when trying to run multiple instances.
The -nobrowser
argument refrains from launching/opening the browser on startup.