Appdata Directory Misc - Revision history

RobinDadswell at 23:02, 27 April 2021

2021-04-27T23:02:09Z

Bakerboy448 at 00:04, 18 April 2021

2021-04-18T00:04:41Z

Bakerboy448: /* Arguments */

2021-02-24T20:40:24Z

Arguments

Bakerboy448: /* Arguments */ typos

2021-02-21T17:34:47Z

Arguments: typos

Bakerboy448: /* Arguments */ add args

2021-02-21T17:34:22Z

Arguments: add args

Drazzilb: /* Arguments */

2020-11-28T06:10:15Z

Arguments

Drazzilb: /* Arguments */

2020-11-28T03:56:12Z

Arguments

Drazzilb: /* Arguments */

2020-11-28T03:43:18Z

Arguments

Drazzilb: /* Sonarr */

2020-11-28T03:40:33Z

Sonarr

Drazzilb: /* Sonarr */

2020-11-28T03:38:52Z

Sonarr

← Older revision		Revision as of 23:02, 27 April 2021
Line 34:		Line 34:
	On windows this would be <code>/nobrowser</code>		On windows this would be <code>/nobrowser</code>
	<section end=readarr_appdata_directory_arguments />		<section end=readarr_appdata_directory_arguments />
		+	=== Prowlarr ===
		+	<section begin=prowlarr_appdata_directory_arguments />
		+	The <code>-data=</code> argument forces the location of the AppData folder, so your startup command may be forcing a specific location. This is required when trying to run multiple instances.
		+	On windows this would be <code>/data=</code>
		+
		+	The <code>-nobrowser</code> argument refrains from launching/opening the browser on startup.
		+	On windows this would be <code>/nobrowser</code>
		+	<section end=prowlarr_appdata_directory_arguments />

@@ Line 3: / Line 3: @@
 === Radarr ===
 <section begin=radarr_appdata_directory_arguments />
-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 required when trying to run multiple instances.
 On windows this would be <code>/data=</code>
@@ Line 11: / Line 11: @@
 === Sonarr ===
 <section begin=sonarr_appdata_directory_arguments />
-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 required when trying to run multiple instances.
 On windows this would be <code>/data=</code>
@@ Line 20: / Line 20: @@
 === Lidarr ===
 <section begin=lidarr_appdata_directory_arguments />
-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 required when trying to run multiple instances.
 On windows this would be <code>/data=</code>
@@ Line 28: / Line 28: @@
 === Readarr ===
 <section begin=readarr_appdata_directory_arguments />
-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 required when trying to run multiple instances.
 On windows this would be <code>/data=</code>

@@ Line 3: / Line 3: @@
 === Radarr ===
 <section begin=radarr_appdata_directory_arguments />
-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.
 <section end=radarr_appdata_directory_arguments />
 === Sonarr ===
 <section begin=sonarr_appdata_directory_arguments />
-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.
 <section end=sonarr_appdata_directory_arguments />
 === Lidarr ===
 <section begin=lidarr_appdata_directory_arguments />
-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.
 <section end=lidarr_appdata_directory_arguments />
 === Readarr ===
 <section begin=readarr_appdata_directory_arguments />
-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.
 <section end=readarr_appdata_directory_arguments />

@@ 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>-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 />
@@ 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>-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 />
@@ 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>-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 />
 === 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>-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 />

@@ Line 3: / Line 3: @@
 === Radarr ===
 <section begin=radarr_appdata_directory_arguments />
-Radarr Arguments Text
+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.
 <section end=radarr_appdata_directory_arguments />
@@ Line 9: / Line 11: @@
 <section begin=sonarr_appdata_directory_arguments />
 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.
-<div style="margin-left: 2em;"><pre>
+The <code>-nobrowser</code>argument refrains from launching/opening the browser on startup.
 <section end=sonarr_appdata_directory_arguments />
 === Lidarr ===
 <section begin=lidarr_appdata_directory_arguments />
-Lidarr Arguments Text
+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.
 <section end=lidarr_appdata_directory_arguments />
 === Readarr ===
 <section begin=readarr_appdata_directory_arguments />
-Readarr Arguments Text
+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.
 <section end=readarr_appdata_directory_arguments />

← Older revision		Revision as of 03:56, 28 November 2020
Line 1:		Line 1:
		+	'''Misc page for Appdata Directory'''
	== Arguments ==		== Arguments ==
	=== Radarr ===		=== Radarr ===

@@ Line 17: / Line 17: @@
 ExecStart=/usr/bin/mono --debug /usr/lib/sonarr/sonarr.exe -nobrowser -data=/var/lib/sonarr
 ...</pre></div>
-<section end=sonarr_appdata_directiory_augments />
+<section end=sonarr_appdata_directory_arguments />
 === Lidarr ===