From 6baa8701b2ace4382674d6a18d904c74211c160a Mon Sep 17 00:00:00 2001 From: Quarto GHA Workflow Runner Date: Sun, 17 Sep 2023 02:00:00 +0000 Subject: [PATCH] Built site for gh-pages --- .nojekyll | 2 +- materials/d1-01-welcome/index.html | 4 +- materials/d1-02-structure/index.html | 115 ++++++++++++----------- materials/d1-9001-loadtesting/index.html | 2 +- schedule.html | 16 ++-- search.json | 9 +- sitemap.xml | 42 ++++----- units/d1-02-structure.html | 4 +- 8 files changed, 105 insertions(+), 89 deletions(-) diff --git a/.nojekyll b/.nojekyll index efad5a6..4e7c2c0 100644 --- a/.nojekyll +++ b/.nojekyll @@ -1 +1 @@ -f4105744 \ No newline at end of file +61705b62 \ No newline at end of file diff --git a/materials/d1-01-welcome/index.html b/materials/d1-01-welcome/index.html index dcb528a..4d5f37c 100644 --- a/materials/d1-01-welcome/index.html +++ b/materials/d1-01-welcome/index.html @@ -368,7 +368,7 @@

Workshop Policies

Meet the Team!

-
+
Eric Nantz @@ -376,7 +376,7 @@

Meet the Team!

-
+
Michael Thomas diff --git a/materials/d1-02-structure/index.html b/materials/d1-02-structure/index.html index d6e6ac0..3270d24 100644 --- a/materials/d1-02-structure/index.html +++ b/materials/d1-02-structure/index.html @@ -405,9 +405,9 @@

Application Structure

It’s Never Just Shiny

… at least for production-quality apps!

    -
  • External data sources
    • -
  • Connections to other execution backends
    • -
  • Additional R packages!
    • +
  • External data sources
    • +
  • Connections to other execution backends
    • +
  • Additional R packages!
@@ -461,30 +461,30 @@

Take Control with {renv}Create reproducible environments for your R projects.

    -
  • Next generation of {packrat}
    • -
  • Isolated package library from rest of your system
    • -
  • Transfer projects to different collaborators / platforms
    • -
  • Reproducible package installation
    • -
  • Easily create new projects or convert existing projects with RStudio or built-in functions.
    • +
  • Next generation of {packrat}
    • +
  • Isolated package library from rest of your system
    • +
  • Transfer projects to different collaborators / platforms
    • +
  • Reproducible package installation
    • +
  • Easily create new projects or convert existing projects with RStudio or built-in functions.

Under the Hood

Upon initializing a project:

    -
  1. Project-level .Rprofile to activate custom package library on startup
    2. -
  2. Lockfile renv.lock to describe state of project library
    3. -
  3. renv/library to hold private project library
    4. -
  4. renv/activate.R performs activation
    5. +
  5. Project-level .Rprofile to activate custom package library on startup
    6. +
  6. Lockfile renv.lock to describe state of project library
    7. +
  7. renv/library to hold private project library
    8. +
  8. renv/activate.R performs activation

Develop a Routine

Sticking with {renv} will pay off (trust me)

    -
  • Fair play to mix packages from CRAN, GitHub, and proprietary sources
    • -
  • Roll back when a package upgrade doesn’t play nicely
    • -
  • You make the call when to update your library!
    • +
  • Fair play to mix packages from CRAN, GitHub, and proprietary sources
    • +
  • Roll back when a package upgrade doesn’t play nicely
    • +
  • You make the call when to update your library!
@@ -496,17 +496,17 @@

Application Structure Options

A Single Point: app.R

Prototype apps can coast by with a single app.R

    -
  • More inputs, visualizations, modules, tabs …
    • -
  • Eventually the app.R almost explodes
    • -
  • Difficult to collaborate without conflicts
    • +
  • More inputs, visualizations, modules, tabs …
    • +
  • Eventually the app.R almost explodes
    • +
  • Difficult to collaborate without conflicts

R Directory
@@ -515,9 +515,9 @@

Enter the {golem}Opinionated framework for building production-grade Shiny applications as R packages

    -
  • Scripts guide you with first steps akin to {usethis} & {devtools}
    • -
  • Encourages Shiny best practices (especially modules)
    • -
  • Streamlines deployment on multiple platforms
    • +
  • Scripts guide you with first steps akin to {usethis} & {devtools}
    • +
  • Encourages Shiny best practices (especially modules)
    • +
  • Streamlines deployment on multiple platforms

@@ -660,18 +660,18 @@

What are Modules?

Building blocks to compose any Shiny app out of smaller, more understandable pieces

    -
  • Avoids namespace collisions when using same widget across different areas of your app
    • -
  • Allow you to encapsulate distinct app interfaces
    • -
  • Organize code into logical and easy-to-understand components
    • -
  • Facilitate collaboration
    • +
  • Avoids namespace collisions when using same widget across different areas of your app
    • +
  • Allow you to encapsulate distinct app interfaces
    • +
  • Organize code into logical and easy-to-understand components
    • +
  • Facilitate collaboration

Sound familiar?

    -
  • R functions also help avoid collisions in variable names with general R code
    • -
  • Essential for creating non-trivial and extensive workflows
    • +
  • R functions also help avoid collisions in variable names with general R code
    • +
  • Essential for creating non-trivial and extensive workflows
@@ -748,8 +748,8 @@

Anatomy of a Module (UI)

}
    -
  • id: String to use for namespace
    • -
  • ns <- NS(id): Create proper namespace function
    • +
  • id: String to use for namespace
    • +
  • ns <- NS(id): Create proper namespace function
@@ -830,7 +830,7 @@

Anatomy of a Module (Server)

@@ -868,9 +868,9 @@

Giving and Receiving

}
@@ -896,7 +896,7 @@

Giving and Receiving

) }
@@ -927,10 +927,19 @@

To () or not to ()

+
+
+
+

Code-Along

+

Code-Along 1: Add a new Shiny module to pick themes

+
+
+

Your Turn: Exercise 1

+

Create a new Shiny module with LEGO data metrics!

posit-conf-2023.github.io/shiny-r-prod

diff --git a/materials/d1-9001-loadtesting/index.html b/materials/d1-9001-loadtesting/index.html index d5b8d83..213e59d 100644 --- a/materials/d1-9001-loadtesting/index.html +++ b/materials/d1-9001-loadtesting/index.html @@ -484,7 +484,7 @@

The log

{"type":"WS_SEND","begin":"2023-09-07T13:04:17.805Z","message":"[\"D#0|m|{\\\"method\\\":\\\"update\\\",\\\"data\\\":{\\\"n_parts_display\\\":\\\"20\\\"}}\"]"} {"type":"WS_CLOSE","begin":"2023-09-07T13:04:35.561Z"}
-
+
diff --git a/schedule.html b/schedule.html index 8d451ce..8a686b9 100644 --- a/schedule.html +++ b/schedule.html @@ -206,7 +206,7 @@

Workshop Schedule

- + 9:00 - 9:30 @@ -217,7 +217,7 @@

Workshop Schedule

Eric Nantz & Michael Thomas - + 9:30 - 10:30 @@ -228,7 +228,7 @@

Workshop Schedule

Eric Nantz & Michael Thomas - + 10:30 - 11:00 @@ -239,7 +239,7 @@

Workshop Schedule

  - + TBD @@ -250,7 +250,7 @@

Workshop Schedule

Eric Nantz & Michael Thomas - + 12:30 - 13:30 @@ -261,7 +261,7 @@

Workshop Schedule

  - + TBD @@ -272,7 +272,7 @@

Workshop Schedule

Eric Nantz & Michael Thomas - + 15:00 - 15:30 @@ -283,7 +283,7 @@

Workshop Schedule

  - + TBD diff --git a/search.json b/search.json index b4f7076..ce554b9 100644 --- a/search.json +++ b/search.json @@ -676,7 +676,14 @@ "href": "materials/d1-02-structure/index.html#to-or-not-to", "title": "Application Structure", "section": "To () or not to ()", - "text": "To () or not to ()\n\n\n# app server\nsets_rv <- reactive({\n # processing\n})\n\nset_picker_server(\"mod1\", sets_rv)\n\nset_picker_server <- function(id, sets_rv) {\n moduleServer(\n id,\n function(input, output, session) {\n # ...\n\n set_selection <- reactive({\n input$set_num\n })\n\n set_selection\n }\n )\n}\n\n\n\nReactive parameters reference by name: sets_rv\nInside module, invoke reactive parameter as you would any other reactive in Shiny: sets_rv()\nAny reactive(s) returned by module should also be reference by name: set_selection, set_selection()\n\n\n\nposit-conf-2023.github.io/shiny-r-prod" + "text": "To () or not to ()\n\n\n# app server\nsets_rv <- reactive({\n # processing\n})\n\nset_picker_server(\"mod1\", sets_rv)\n\nset_picker_server <- function(id, sets_rv) {\n moduleServer(\n id,\n function(input, output, session) {\n # ...\n\n set_selection <- reactive({\n input$set_num\n })\n\n set_selection\n }\n )\n}\n\n\n\nReactive parameters reference by name: sets_rv\nInside module, invoke reactive parameter as you would any other reactive in Shiny: sets_rv()\nAny reactive(s) returned by module should also be reference by name: set_selection, set_selection()" + }, + { + "objectID": "materials/d1-02-structure/index.html#your-turn-exercise-1", + "href": "materials/d1-02-structure/index.html#your-turn-exercise-1", + "title": "Application Structure", + "section": "Your Turn: Exercise 1", + "text": "Your Turn: Exercise 1\nCreate a new Shiny module with LEGO data metrics!\n\n\nposit-conf-2023.github.io/shiny-r-prod" }, { "objectID": "materials/d1-02-structure/codealong-1.html", diff --git a/sitemap.xml b/sitemap.xml index a48db1f..5811abc 100644 --- a/sitemap.xml +++ b/sitemap.xml @@ -2,86 +2,86 @@ https://posit-conf-2023.github.io/shiny-r-prod/materials/d1-03-performance/index.html - 2023-09-17T01:31:51.699Z + 2023-09-17T01:59:27.752Z https://posit-conf-2023.github.io/shiny-r-prod/materials/d1-04-deploy-admin/index.html - 2023-09-17T01:31:51.739Z + 2023-09-17T01:59:27.768Z https://posit-conf-2023.github.io/shiny-r-prod/materials/d1-02-structure/ex-1.html - 2023-09-17T01:31:51.699Z + 2023-09-17T01:59:27.748Z https://posit-conf-2023.github.io/shiny-r-prod/materials/setup-resources/index.html - 2023-09-17T01:31:51.787Z + 2023-09-17T01:59:27.816Z https://posit-conf-2023.github.io/shiny-r-prod/materials/d1-01-welcome/index.html - 2023-09-17T01:31:51.683Z + 2023-09-17T01:59:27.732Z https://posit-conf-2023.github.io/shiny-r-prod/units/d1-01-welcome.html - 2023-09-17T01:31:51.791Z + 2023-09-17T01:59:27.820Z https://posit-conf-2023.github.io/shiny-r-prod/units/d1-04-deploy-admin.html - 2023-09-17T01:31:51.791Z + 2023-09-17T01:59:27.820Z https://posit-conf-2023.github.io/shiny-r-prod/units/d1-02-structure.html - 2023-09-17T01:31:51.791Z + 2023-09-17T01:59:27.820Z https://posit-conf-2023.github.io/shiny-r-prod/units/d1-02b-break.html - 2023-09-17T01:31:51.791Z + 2023-09-17T01:59:27.820Z https://posit-conf-2023.github.io/shiny-r-prod/schedule.html - 2023-09-17T01:31:51.787Z + 2023-09-17T01:59:27.816Z https://posit-conf-2023.github.io/shiny-r-prod/index.html - 2023-09-17T01:31:51.659Z + 2023-09-17T01:59:27.712Z https://posit-conf-2023.github.io/shiny-r-prod/LICENSE.html - 2023-09-17T01:31:51.599Z + 2023-09-17T01:59:27.648Z https://posit-conf-2023.github.io/shiny-r-prod/units/d1-03b-lunch.html - 2023-09-17T01:31:51.791Z + 2023-09-17T01:59:27.820Z https://posit-conf-2023.github.io/shiny-r-prod/units/d1-04b-break.html - 2023-09-17T01:31:51.791Z + 2023-09-17T01:59:27.820Z https://posit-conf-2023.github.io/shiny-r-prod/units/d1-03-performance.html - 2023-09-17T01:31:51.791Z + 2023-09-17T01:59:27.820Z https://posit-conf-2023.github.io/shiny-r-prod/units/d1-9001-loadtesting.html - 2023-09-17T01:31:51.791Z + 2023-09-17T01:59:27.820Z https://posit-conf-2023.github.io/shiny-r-prod/setup.html - 2023-09-17T01:31:51.787Z + 2023-09-17T01:59:27.816Z https://posit-conf-2023.github.io/shiny-r-prod/materials/d1-9001-loadtesting/index.html - 2023-09-17T01:31:51.751Z + 2023-09-17T01:59:27.780Z https://posit-conf-2023.github.io/shiny-r-prod/materials/d1-02-structure/index.html - 2023-09-17T01:31:51.699Z + 2023-09-17T01:59:27.748Z https://posit-conf-2023.github.io/shiny-r-prod/materials/d1-02-structure/codealong-1.html - 2023-09-17T01:31:51.699Z + 2023-09-17T01:59:27.748Z https://posit-conf-2023.github.io/shiny-r-prod/materials/profvis/index.html - 2023-09-17T01:31:51.751Z + 2023-09-17T01:59:27.780Z diff --git a/units/d1-02-structure.html b/units/d1-02-structure.html index cf875e2..debe90f 100644 --- a/units/d1-02-structure.html +++ b/units/d1-02-structure.html @@ -256,7 +256,7 @@

Code-Along Examples - +   @@ -286,7 +286,7 @@

Exercises

- +