Settings General - Revision history

Bakerboy448 at 22:00, 6 May 2021

2021-05-06T22:00:42Z

Bakerboy448: /* Backups */

2021-05-06T13:53:13Z

Backups

Bakerboy448: /* Updates */

2021-03-10T20:35:14Z

Updates

RobinDadswell: /* Sonarr */

2021-03-08T22:34:23Z

Sonarr

RobinDadswell: /* Sonarr */

2021-03-08T22:25:48Z

Sonarr

RobinDadswell: /* Sonarr */

2021-03-08T22:23:00Z

Sonarr

RobinDadswell: /* Sonarr */

2021-03-08T22:20:45Z

Sonarr

Bakerboy448 at 03:33, 25 February 2021

2021-02-25T03:33:37Z

Bakerboy448: /* Host */ enhance base

2021-02-06T19:08:04Z

Host: enhance base

Bakerboy448: /* Host */

2021-02-06T19:06:42Z

Host

@@ Line 193: / Line 193: @@
 ** develop (Nightly) : This is the bleeding edge. It is released as soon as code is committed and passes all automated tests. This build may have not been used by us or other users yet. There is no guarantee that it will even run in some cases. This branch is only recommended for advanced users. Issues and self investigation are expected in this branch.
 ** phantom-develop (v3-preview): This is EOL and the built-in updater will automatically update to main.
-* * Automatic - Automatically download and install updates. You will still be able to install from System: Updates.  Note: Windows Users are always automatically updated.
+** Automatic - Automatically download and install updates. You will still be able to install from System: Updates.  Note: Windows Users are always automatically updated.
 * Mechanism - Use Sonarr built-in updater or a script
 ** Built-in - Use Sonarr's own updater

@@ Line 234: / Line 234: @@
 * Folder - This allows you to select the backup location
 ** In docker you will be limited to what you allow the container to see
 * Interval - How often would you like Radarr to make a backup
 * Retention - How long would you like Radarr to hold on to each backup. After a new backup is made the oldest backup will be removed
@@ Line 242: / Line 243: @@
 * Folder - This allows you to select the backup location
 ** In docker you will be limited to what you allow the container to see
 * Interval - How often would you like Sonarr to make a backup
 * Retention - How long would you like Sonarr to hold on to each backup. After a new backup is made the oldest backup will be removed
@@ Line 250: / Line 252: @@
 * Folder - This allows you to select the backup location
 ** In docker you will be limited to what you allow the container to see
 * Interval - How often would you like Lidarr to make a backup
 * Retention - How long would you like Lidarr to hold on to each backup. After a new backup is made the oldest backup will be removed
@@ Line 258: / Line 261: @@
 * Folder - This allows you to select the backup location
 ** In docker you will be limited to what you allow the container to see
 * Interval - How often would you like Readarr to make a backup
 * Retention - How long would you like Readarr to hold on to each backup. After a new backup is made the oldest backup will be removed

@@ Line 181: / Line 181: @@
 * Branch - This is the branch of Radarr that you are running on. Please see [[Radarr_FAQ#How_do_I_update_Radarr.3F|the FAQ]] for available branches and version information
-* Automatic - Automatically download and install updates. You will still be able to install from System: Updates
+* Automatic - Automatically download and install updates. You will still be able to install from System: Updates.  Note: Windows Users are always automatically updated.
 * Mechanism - Use Radarr's built-in updater or a script
 ** Docker - Do not update Radarr from inside the Docker, instead pull a brand new image with the new update
 ** Script - Have Radarr run the update script
@@ Line 189: / Line 190: @@
 <section begin=sonarr_settings_general_updates />
 * Branch - This is the branch of Sonarr that you are running on. Please see [https://github.com/Sonarr/Sonarr Github] for available branches and version information. These branches only apply to V3.
-** main (Stable): This has been tested by users on nightly branch and it's not known to have any major issues. This branch should be userd by the majority of users.
+** main (Stable): This has been tested by users on nightly branch and it's not known to have any major issues. This branch should be used by the majority of users.
 ** develop (Nightly) : This is the bleeding edge. It is released as soon as code is committed and passes all automated tests. This build may have not been used by us or other users yet. There is no guarantee that it will even run in some cases. This branch is only recommended for advanced users. Issues and self investigation are expected in this branch.
 ** phantom-develop (v3-preview): This is EOL and the built-in updater will automatically update to main.
-* Automatic - Automatically download and install updates. You will still be able to install from System: Updates
+* * Automatic - Automatically download and install updates. You will still be able to install from System: Updates.  Note: Windows Users are always automatically updated.
 * Mechanism - Use Sonarr built-in updater or a script
 ** Built-in - Use Sonarr's own updater
@@ Line 208: / Line 209: @@
 === Lidarr ===
 <section begin=lidarr_settings_general_updates />
-* If your using a docker container to run your Lidarr instance. Do not update Lidarr while inside the container. This has a bad tendancy to break things. Instead update the actual docker image which has the most current build.
+* Branch - This is the branch of Lidarr that you are running on.
 <section end=lidarr_settings_general_updates />
 === Readarr ===
 <section begin=readarr_settings_general_updates />
-* If your using a docker container to run your Lidarr instance. Do not update Lidarr while inside the container. This has a bad tendancy to break things. Instead update the actual docker image which has the most current build.
+* Branch - This is the branch of Readarr that you are running on.
 <section end=readarr_settings_general_updates />

@@ Line 189: / Line 189: @@
 <section begin=sonarr_settings_general_updates />
 * Branch - This is the branch of Sonarr that you are running on. Please see [https://github.com/Sonarr/Sonarr Github] for available branches and version information. These branches only apply to V3.
-** main (Stable): This has been tested by users on nightly branch and it's not known to have any major issues.
+** main (Stable): This has been tested by users on nightly branch and it's not known to have any major issues. This branch should be userd by the majority of users.
-** develop (Nightly) : This is the bleeding edge. It is released as soon as code is committed and passes all automated tests. This build may have not been used by us or other users yet. There is no guarantee that it will even run in some cases.
+** develop (Nightly) : This is the bleeding edge. It is released as soon as code is committed and passes all automated tests. This build may have not been used by us or other users yet. There is no guarantee that it will even run in some cases. This branch is only recommended for advanced users. Issues and self investigation are expected in this branch.
 ** phantom-develop (v3-preview): This is EOL and the built-in updater will automatically update to main.
 * Automatic - Automatically download and install updates. You will still be able to install from System: Updates

@@ Line 191: / Line 191: @@
 ** main (Stable): This has been tested by users on nightly branch and it's not known to have any major issues.
 ** develop (Nightly) : This is the bleeding edge. It is released as soon as code is committed and passes all automated tests. This build may have not been used by us or other users yet. There is no guarantee that it will even run in some cases.
-** phantom-develop (v3-preview): This is EOL and will be redirected to main. There will be no more updates to this branch.
+** phantom-develop (v3-preview): This is EOL and the built-in updater will automatically update to main.
 * Automatic - Automatically download and install updates. You will still be able to install from System: Updates
 * Mechanism - Use Sonarr built-in updater or a script

@@ Line 123: / Line 123: @@
 ** Debug - Debug will include all the information that Info includes plus more information that can be useful.
 *** This log files contains fatal, error, warn, info and debug entries
-** Trace - The most advance and detailed logging on Radarr, Trace will include all the information gathered by Info and Debug and more. This is the most common type of log that is going to be asked for when trouble shooting on Discord or Reddit. If you're needing help please select your log to Trace and redo the task that was giving you problems to capture the log.
+** Trace - The most advance and detailed logging on Radarr, Trace will include all the information gathered by Info and Debug and more. This is the most common type of log that is going to be asked for when troubleshooting on Discord or Reddit. If you're needing help please select your log to Trace and redo the task that was giving you problems to capture the log.
 *** This log files contains fatal, error, warn, info, debug and trace entries.
 <section end=radarr_settings_general_logging />
@@ Line 133: / Line 133: @@
 ** Debug - Debug will include all the information that Info includes plus more information that can be useful.
 *** This log files contains fatal, error, warn, info and debug entries
-** Trace - The most advance and detailed logging on Sonarr, Trace will include all the information gathered by Info and Debug and more. This is the most common type of log that is going to be asked for when trouble shooting on Discord or Reddit. If you're needing help please select your log to Trace and redo the task that was giving you problems to capture the log.
+** Trace - The most advance and detailed logging on Sonarr, Trace will include all the information gathered by Info and Debug and more. This is the most common type of log that is going to be asked for when troubleshooting on Discord or Reddit. If you're needing help please select your log to Trace and redo the task that was giving you problems to capture the log.
 *** This log files contains fatal, error, warn, info, debug and trace entries.
 <section end=sonarr_settings_general_logging />
@@ Line 143: / Line 143: @@
 ** Debug - Debug will include all the information that Info includes plus more information that can be useful.
 *** This log files contains fatal, error, warn, info and debug entries
-** Trace - The most advance and detailed logging on Lidarr, Trace will include all the information gathered by Info and Debug and more. This is the most common type of log that is going to be asked for when trouble shooting on Discord or Reddit. If you're needing help please select your log to Trace and redo the task that was giving you problems to capture the log.
+** Trace - The most advance and detailed logging on Lidarr, Trace will include all the information gathered by Info and Debug and more. This is the most common type of log that is going to be asked for when troubleshooting on Discord or Reddit. If you're needing help please select your log to Trace and redo the task that was giving you problems to capture the log.
 *** This log files contains fatal, error, warn, info, debug and trace entries.
 <section end=lidarr_settings_general_logging />
@@ Line 153: / Line 153: @@
 ** Debug - Debug will include all the information that Info includes plus more information that can be useful.
 *** This log files contains fatal, error, warn, info and debug entries
-** Trace - The most advance and detailed logging on Readarr, Trace will include all the information gathered by Info and Debug and more. This is the most common type of log that is going to be asked for when trouble shooting on Discord or Reddit. If you're needing help please select your log to Trace and redo the task that was giving you problems to capture the log.
+** Trace - The most advance and detailed logging on Readarr, Trace will include all the information gathered by Info and Debug and more. This is the most common type of log that is going to be asked for when troubleshooting on Discord or Reddit. If you're needing help please select your log to Trace and redo the task that was giving you problems to capture the log.
 *** This log files contains fatal, error, warn, info, debug and trace entries.
 <section end=readarr_settings_general_logging />

@@ Line 10: / Line 10: @@
 ** Note: If using Docker do not touch
 * URL Base - For reverse proxy support, default is empty
-** Note: If using a reverse proxy (IE: mydomain.com/radarr) you would enter '/radarr' for URL Base.
+** Note: If using a reverse proxy (example: mydomain.com/radarr) you would enter '/radarr' for URL Base.
 * Enable SSL - If you have SSL credentials and would like to secure communication to and from your Radarr enable this option.
 ** Note: do not mess with unless you know what you're doing
@@ Line 23: / Line 23: @@
 ** Note: If using Docker do not touch
 * URL Base - For reverse proxy support, default is empty
-** Note: If using a reverse proxy (IE: mydomain.com/sonarr) you would enter '/sonarr' for URL Base.
+** Note: If using a reverse proxy (example: mydomain.com/sonarr) you would enter '/sonarr' for URL Base.
 * Enable SSL - If you have SSL credentials and would like to secure communication to and from your Sonarr enable this option.
 ** Note: do not mess with unless you know what you're doing
@@ Line 36: / Line 36: @@
 ** Note: If using Docker do not touch
 * URL Base - For reverse proxy support, default is empty
 * Enable SSL - If you have SSL credentials and would like to secure communication to and from your Lidarr enable this option.
 ** Note: do not mess with unless you know what you're doing
@@ Line 48: / Line 49: @@
 ** Note: If using Docker do not touch
 * URL Base - For reverse proxy support, default is empty
 * Enable SSL - If you have SSL credentials and would like to secure communication to and from your Readarr enable this option.
 ** Note: do not mess with unless you know what you're doing

@@ Line 4: / Line 4: @@
 <section begin=radarr_settings_general_host />
 * Binding Address - Valid IP4 address or '*' for all interfaces
 * Port Number - The port number that you are wanting to use to access the webUI for Radarr
 ** Note: If using Docker do not touch
@@ Line 14: / Line 17: @@
 <section begin=sonarr_settings_general_host />
 * Binding Address - Valid IP4 address or '*' for all interfaces
 * Port Number - The port number that you are wanting to use to access the webUI for Sonarr
 ** Note: If using Docker do not touch
@@ Line 24: / Line 30: @@
 <section begin=lidarr_settings_general_host />
 * Binding Address - Valid IP4 address or '*' for all interfaces
 * Port Number - The port number that you are wanting to use to access the webUI for Lidarr
 ** Note: If using Docker do not touch
@@ Line 33: / Line 42: @@
 <section begin=readarr_settings_general_host />
 * Binding Address - Valid IP4 address or '*' for all interfaces
 * Port Number - The port number that you are wanting to use to access the webUI for Readarr
 ** Note: If using Docker do not touch