[dev2] [Part 4] Configuration files: remotes.json (#2963)

* remotes and minor fixes

* wip

* improved

* Removed MesonDeps conan-io/conan#13134

reference/commands/list.rst

@@ -1,3 +1,5 @@
+.. _reference_commands_list:
+
 conan list
 ==========
 

reference/config_files.rst

@@ -12,3 +12,4 @@ These are the most important configuration files, used to customize conan.
     config_files/global_conf
     config_files/profiles
     config_files/settings
+    config_files/remotes

reference/config_files/global_conf.rst

@@ -228,22 +228,25 @@ effect because it's the first one evaluated, and after that, Conan is overriding
 general one, so it deserves to pay special attention to the order.
 
 
+.. _reference_config_files_global_conf_ssl_certificates:
+
 Configuration of client certificates
 ------------------------------------
 
 Conan supports client TLS certificates. You can configure the path to your existing *Cacert* file and/or your client
 certificate (and the key) using the following configuration variables:
 
 * ``core.net.http:cacert_path``: Path containing a custom Cacert file.
-* ``core.net.http:client_cert``: Path or tuple of files containing a client cert (and key).
+* ``core.net.http:client_cert``: Path or tuple of files containing a client certificate (and the key). See more details in
+  `Python requests and Client Side Certificates <https://requests.readthedocs.io/en/latest/user/advanced/#client-side-certificates>`_
 
 For instance:
 
 .. code-block:: text
     :caption: **[CONAN_HOME]/global.conf**
 
-    core.net.http:cacert_path=/path/to/cacert_file
-    core.net.http:client_cert=/path/to/client_certificate
+    core.net.http:cacert_path=/path/to/cacert.pem
+    core.net.http:client_cert=('/path/client.cert', '/path/client.key')
 
 
 .. seealso::

reference/config_files/remotes.rst

@@ -0,0 +1,39 @@
+.. _reference_config_files_remotes_json:
+
+remotes.json
+============
+
+The **remotes.json** file is located in the Conan user home directory, e.g., *[CONAN_HOME]/remotes.json*.
+
+The default file created by Conan looks like this:
+
+.. code-block:: json
+    :caption: **remotes.json**
+
+    {
+     "remotes": [
+      {
+       "name": "conancenter",
+       "url": "https://center.conan.io",
+       "verify_ssl": true
+      }
+     ]
+    }
+
+Essentially, it tells Conan where to list/upload/download the recipes/binaries from the remotes specified by their URLs.
+
+The fields for each remote are:
+
+* ``name`` (Required, ``string`` value): Name of the remote. This name will be used in commands
+  like :ref:`reference_commands_list`, e.g., :command:`conan list zlib/1.2.11 --remote my_remote_name`.
+* ``url`` (Required, ``string`` value): indicates the URL to be used by Conan to search for the recipes/binaries.
+* ``verify_ssl`` (Required, ``bool`` value): Verify SSL certificate of the specified url.
+* ``disabled`` (Optional, ``bool`` value, ``false`` by default): If the remote is enabled or not to be used by commands
+  like search, list, download and upload. Notice that a disabled remote can be used to authenticate against it even
+  if it's disabled.
+
+
+.. seealso::
+
+    - :ref:`How to manage SSL (TLS) certificates <reference_config_files_global_conf_ssl_certificates>`
+    - :ref:`How to manage remotes.json through CLI: conan remotes <reference_commands_remote>`.

reference/config_files/settings.rst

@@ -146,7 +146,7 @@ Operating systems
 -----------------
 
 ``baremetal`` operating system is a convention meaning that the binaries run directly
-on the hardware, without an operating system or equivalent layer. This is to differentiate to the ``None`` value,
+on the hardware, without an operating system or equivalent layer. This is to differentiate to the ``null`` value,
 which is associated to the "this value is not defined" semantics. ``baremetal`` is a common name convention for
 embedded microprocessors and microcontrollers' code. It is expected that users might customize the space inside the
 ``baremetal`` setting with further subsettings to specify their specific hardware platforms, boards, families, etc.
@@ -189,7 +189,7 @@ This can be configured in your profiles with the ``tools.microsoft.msbuild:vs_ve
 In this case, the ``vcvars`` will activate the Visual Studio 16 installation, but the ``190`` compiler version will still be used
 because the necessary ``toolset=v140`` will be set.
 
-The settings define the last digit ``update: [None, 0, 1, 2, 3, 4, 5, 6, 7, 8, 9]``, which by default is ``None`` and means that Conan
+The settings define the last digit ``update: [null, 0, 1, 2, 3, 4, 5, 6, 7, 8, 9]``, which by default is ``null`` and means that Conan
 assumes binary compatibility for the compiler patches, which works in general for the Microsoft compilers. For cases where finer
 control is desired, you can just add the ``update`` part to your profiles:
 

reference/tools/meson.rst

@@ -7,5 +7,4 @@ conan.tools.meson
     :maxdepth: 2
 
     meson/mesontoolchain
-    meson/mesondeps
     meson/meson