Added channel RSS feed info

makbigc · Jul 30, 2019 · 5fbea5b · 5fbea5b
1 parent 553637b
commit 5fbea5b
Show file tree

Hide file tree

Showing 3 changed files with 51 additions and 7 deletions.
diff --git a/docs/source/user-guide/concepts/channels.rst b/docs/source/user-guide/concepts/channels.rst
@@ -57,3 +57,47 @@ Priority decreases from left to right - the first argument is higher priority th
 
 Learn more about :doc:`managing channels <../tasks/manage-channels>`.
 
+.. _rss-feed:
+
+Conda clone channel RSS feed
+============================
+
+We offer a RSS feed that represents all the things
+that have been cloned by the channel clone and are
+now available behind the CDN (content delivery network).
+The RSS feed shows what has happened on a rolling,
+two-week time frame and is useful for seeing where
+packages are or if a sync has been run. 
+
+Let's look at the `conda-forge channel RSS feed <https://conda-static.anaconda.org/conda-forge/rss.xml>`_
+as an example.
+
+In that feed, it will tell you every time that it runs a sync.
+The feed includes other entries for packages that were added or
+removed. Each entry is formatted to show the subdirectory
+the package is from, the action that was taken (addition or removal),
+and the name of the package. Everything has a publishing date,
+per standard RSS practice.
+
+.. code-block:: xml
+
+  <rss version="0.91">
+    <channel>
+      <title>conda-forge updates</title>
+      <link>https://anaconda.org</link>
+      <description>Updates in the last two weeks</description>
+      <language>en</language>
+      <copyright>Copyright 2019, Anaconda, Inc.</copyright>
+      <pubDate>30 Jul 2019 19:45:47 UTC</pubDate>
+        <item>
+          <title>running sync</title>
+          <pubDate>26 Jul 2019 19:26:36 UTC</pubDate>
+        </item>
+        <item>
+          <title>linux-64:add:jupyterlab-1.0.4-py36_0.tar.bz2</title>
+          <pubDate>26 Jul 2019 19:26:36 UTC</pubDate>
+        </item>
+        <item>
+          <title>linux-64:add:jupyterlab-1.0.4-py37_0.tar.bz2</title>
+          <pubDate>26 Jul 2019 19:26:36 UTC</pubDate>
+        </item>
diff --git a/docs/source/user-guide/concepts/conda-performance.rst b/docs/source/user-guide/concepts/conda-performance.rst
@@ -98,10 +98,10 @@ process. Listing a version and build string for each of your specs can
 dramatically reduce the number of packages that are considered when solving
 so that the SAT doesn’t have as much work to do.
 
- Reducing the index:
-    * Reduces unnecessary input into generating solver clauses.
-    * Reduces solve complexity.
-    * Prefers newer packages that apply constraints.
+Reducing the index:
+  * Reduces unnecessary input into generating solver clauses.
+  * Reduces solve complexity.
+  * Prefers newer packages that apply constraints.
 
- Read more on `Understanding and Improving Conda's Performance
+Read more on `Understanding and Improving Conda's Performance
 <https://www.anaconda.com/understanding-and-improving-condas-performance/>`_.
diff --git a/docs/source/user-guide/concepts/environments.rst b/docs/source/user-guide/concepts/environments.rst
@@ -100,7 +100,7 @@ Some other traits are:
 |
 
 Why use venv-based virtual environments
-===================================
+=======================================
 - You prefer their workflow or spec formats
 - You prefer to use the system Python and libraries
 - Your project maintainers only publish to PyPI, and you prefer packages that come more directly from the project maintainers,   rather than someone else providing builds based on the same code
@@ -118,7 +118,7 @@ Workflow differentiators
 ========================
 
 Some questions to consider as you determine your preferred
-workflow and virtual environment: 
+workflow and virtual environment:
 
 - Is your environment shared across multiple code projects?
 - Does your environment live alongside your code or in a separate place?