Built site for gh-pages

lmu-osc · Sep 29, 2024 · 69f91de · 69f91de
1 parent 5c3f3fc
commit 69f91de
Show file tree

Hide file tree

Showing 5 changed files with 23 additions and 23 deletions.
diff --git a/.nojekyll b/.nojekyll
@@ -1 +1 @@
-cd071e25
+b370766a
diff --git a/dependencies_in_r.html b/dependencies_in_r.html
@@ -386,7 +386,7 @@ <h2 class="anchored" data-anchor-id="renv">{renv}</h2>
 <section id="pros-and-cons" class="level3">
 <h3 class="anchored" data-anchor-id="pros-and-cons">Pros and Cons</h3>
 <p>As mentioned, {renv} is likely the most popular option for package management in R, and is a highly transferable skill between both academia and industry settings<a href="#fn1" class="footnote-ref" id="fnref1" role="doc-noteref"><sup>1</sup></a>. Thus, it is the one that I recommend using for new projects, and will be the focus of the rest of this tutorial on dependency management in R.</p>
-<p>Moreover, this package can be considered a relatively stable package as it has moved beyond it’s initial development stages into a version 1 release (currently at version 1.0.8). It is maintained by professional software engineers at Posit, and also receives open-source contributions and bug reports via the public GitHub repository.</p>
+<p>Moreover, this package can be considered a relatively stable package as it has moved beyond it’s initial development stages into a version 1 release (currently at version 1.0.9). It is maintained by professional software engineers at Posit, and also receives open-source contributions and bug reports via the public GitHub repository.</p>
 <p>In comparison to {groundhog}, one of the supposed main drawbacks of {renv} is that it is project-based, meaning that you need to create an R Project (<code>.RProj</code> file) to use {renv} whereas {groundhog} allows you to simply embed the function <code>groundhog.library(pkg, date)</code> into any R file. This is not a drawback in my opinion, as using an R Project structure helps manage your working environment, but it is worth noting that the <em>default workflow</em> for {renv} is not as flexible as {groundhog} in this regard. However, {renv} also offers a similar workflow to {groundhog} via the <code>embed()</code> and <code>use()</code> functions, discussed in the supplementary material of this tutorial.</p>
 </section>
 </section>

diff --git a/search.json b/search.json
@@ -64,7 +64,7 @@
     "href": "dependencies_in_r.html#renv",
     "title": "Dependency Management in R",
     "section": "{renv}",
-    "text": "{renv}\n{renv} is another one of Posit’s inventions, and is designed to be lightweight, easy to use, and to work well with other Posit packages and CI/CD development pipelines. A separate tutorial will discuss CI/CD pipelines in detail, but, in short, using {renv} with your R projects allows you to easily automate advanced tasks like publishing Shiny apps, deploying website updates through GitHub Pages, checking the development status of R packages you create, and more. These benefits may seem a bit less tangible if you are new to R, but they are very important both for professional software development and for tasks that can make your work significantly easier in the long run.\nMore to the focus of this tutorial, however, {renv} greatly assists in making your project reproducible by creating a “snapshot” of your package dependencies in as few as two commands:\nrenv::init()\nrenv::snapshot()\nThe results of this code will be discussed in the next chapter, but, in short, the “snapshot” it creates can be shared with collaborators or used to recreate your working environment at a later date. This is referred to as restoring a project, and can be done with the aptly-named renv::restore() function.\n\nPros and Cons\nAs mentioned, {renv} is likely the most popular option for package management in R, and is a highly transferable skill between both academia and industry settings1. Thus, it is the one that I recommend using for new projects, and will be the focus of the rest of this tutorial on dependency management in R.\nMoreover, this package can be considered a relatively stable package as it has moved beyond it’s initial development stages into a version 1 release (currently at version 1.0.8). It is maintained by professional software engineers at Posit, and also receives open-source contributions and bug reports via the public GitHub repository.\nIn comparison to {groundhog}, one of the supposed main drawbacks of {renv} is that it is project-based, meaning that you need to create an R Project (.RProj file) to use {renv} whereas {groundhog} allows you to simply embed the function groundhog.library(pkg, date) into any R file. This is not a drawback in my opinion, as using an R Project structure helps manage your working environment, but it is worth noting that the default workflow for {renv} is not as flexible as {groundhog} in this regard. However, {renv} also offers a similar workflow to {groundhog} via the embed() and use() functions, discussed in the supplementary material of this tutorial.",
+    "text": "{renv}\n{renv} is another one of Posit’s inventions, and is designed to be lightweight, easy to use, and to work well with other Posit packages and CI/CD development pipelines. A separate tutorial will discuss CI/CD pipelines in detail, but, in short, using {renv} with your R projects allows you to easily automate advanced tasks like publishing Shiny apps, deploying website updates through GitHub Pages, checking the development status of R packages you create, and more. These benefits may seem a bit less tangible if you are new to R, but they are very important both for professional software development and for tasks that can make your work significantly easier in the long run.\nMore to the focus of this tutorial, however, {renv} greatly assists in making your project reproducible by creating a “snapshot” of your package dependencies in as few as two commands:\nrenv::init()\nrenv::snapshot()\nThe results of this code will be discussed in the next chapter, but, in short, the “snapshot” it creates can be shared with collaborators or used to recreate your working environment at a later date. This is referred to as restoring a project, and can be done with the aptly-named renv::restore() function.\n\nPros and Cons\nAs mentioned, {renv} is likely the most popular option for package management in R, and is a highly transferable skill between both academia and industry settings1. Thus, it is the one that I recommend using for new projects, and will be the focus of the rest of this tutorial on dependency management in R.\nMoreover, this package can be considered a relatively stable package as it has moved beyond it’s initial development stages into a version 1 release (currently at version 1.0.9). It is maintained by professional software engineers at Posit, and also receives open-source contributions and bug reports via the public GitHub repository.\nIn comparison to {groundhog}, one of the supposed main drawbacks of {renv} is that it is project-based, meaning that you need to create an R Project (.RProj file) to use {renv} whereas {groundhog} allows you to simply embed the function groundhog.library(pkg, date) into any R file. This is not a drawback in my opinion, as using an R Project structure helps manage your working environment, but it is worth noting that the default workflow for {renv} is not as flexible as {groundhog} in this regard. However, {renv} also offers a similar workflow to {groundhog} via the embed() and use() functions, discussed in the supplementary material of this tutorial.",
     "crumbs": [
       "Home",
       "Background",

diff --git a/sitemap.xml b/sitemap.xml
@@ -2,70 +2,70 @@
 <urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
   <url>
     <loc>https://lmu-osc.github.io/introduction-to-renv/ex_init_snapshot.html</loc>
-    <lastmod>2024-09-22T23:10:50.614Z</lastmod>
+    <lastmod>2024-09-29T23:09:26.607Z</lastmod>
   </url>
   <url>
     <loc>https://lmu-osc.github.io/introduction-to-renv/dependencies_in_r.html</loc>
-    <lastmod>2024-09-22T23:10:50.614Z</lastmod>
+    <lastmod>2024-09-29T23:09:26.607Z</lastmod>
   </url>
   <url>
     <loc>https://lmu-osc.github.io/introduction-to-renv/about.html</loc>
-    <lastmod>2024-09-22T23:10:50.578Z</lastmod>
+    <lastmod>2024-09-29T23:09:26.572Z</lastmod>
   </url>
   <url>
     <loc>https://lmu-osc.github.io/introduction-to-renv/ex_2.html</loc>
-    <lastmod>2024-09-22T23:10:50.614Z</lastmod>
+    <lastmod>2024-09-29T23:09:26.607Z</lastmod>
   </url>
   <url>
     <loc>https://lmu-osc.github.io/introduction-to-renv/ex_3.html</loc>
-    <lastmod>2024-09-22T23:10:50.614Z</lastmod>
+    <lastmod>2024-09-29T23:09:26.607Z</lastmod>
   </url>
   <url>
     <loc>https://lmu-osc.github.io/introduction-to-renv/restoring_a_project.html</loc>
-    <lastmod>2024-09-22T23:10:50.615Z</lastmod>
+    <lastmod>2024-09-29T23:09:26.608Z</lastmod>
   </url>
   <url>
     <loc>https://lmu-osc.github.io/introduction-to-renv/renv_getting_started.html</loc>
-    <lastmod>2024-09-22T23:10:50.615Z</lastmod>
+    <lastmod>2024-09-29T23:09:26.608Z</lastmod>
   </url>
   <url>
     <loc>https://lmu-osc.github.io/introduction-to-renv/embed_and_use.html</loc>
-    <lastmod>2024-09-22T23:10:50.614Z</lastmod>
+    <lastmod>2024-09-29T23:09:26.607Z</lastmod>
   </url>
   <url>
     <loc>https://lmu-osc.github.io/introduction-to-renv/intro_dependencies.html</loc>
-    <lastmod>2024-09-22T23:10:50.614Z</lastmod>
+    <lastmod>2024-09-29T23:09:26.607Z</lastmod>
   </url>
   <url>
     <loc>https://lmu-osc.github.io/introduction-to-renv/index.html</loc>
-    <lastmod>2024-09-22T23:10:50.614Z</lastmod>
+    <lastmod>2024-09-29T23:09:26.607Z</lastmod>
   </url>
   <url>
     <loc>https://lmu-osc.github.io/introduction-to-renv/outline.html</loc>
-    <lastmod>2024-09-22T23:10:50.614Z</lastmod>
+    <lastmod>2024-09-29T23:09:26.608Z</lastmod>
   </url>
   <url>
     <loc>https://lmu-osc.github.io/introduction-to-renv/technical_definitions.html</loc>
-    <lastmod>2024-09-22T23:10:50.615Z</lastmod>
+    <lastmod>2024-09-29T23:09:26.609Z</lastmod>
   </url>
   <url>
     <loc>https://lmu-osc.github.io/introduction-to-renv/advanced_topics.html</loc>
-    <lastmod>2024-09-22T23:10:50.578Z</lastmod>
+    <lastmod>2024-09-29T23:09:26.572Z</lastmod>
   </url>
   <url>
     <loc>https://lmu-osc.github.io/introduction-to-renv/LICENSE.html</loc>
-    <lastmod>2024-09-22T23:10:50.578Z</lastmod>
+    <lastmod>2024-09-29T23:09:26.572Z</lastmod>
   </url>
   <url>
     <loc>https://lmu-osc.github.io/introduction-to-renv/starting_details.html</loc>
-    <lastmod>2024-09-22T23:10:50.615Z</lastmod>
+    <lastmod>2024-09-29T23:09:26.608Z</lastmod>
   </url>
   <url>
     <loc>https://lmu-osc.github.io/introduction-to-renv/comp_reproducible.html</loc>
-    <lastmod>2024-09-22T23:10:50.614Z</lastmod>
+    <lastmod>2024-09-29T23:09:26.607Z</lastmod>
   </url>
   <url>
     <loc>https://lmu-osc.github.io/introduction-to-renv/caching.html</loc>
-    <lastmod>2024-09-22T23:10:50.613Z</lastmod>
+    <lastmod>2024-09-29T23:09:26.607Z</lastmod>
   </url>
 </urlset>