GitHub, Connect, and CodeSpaces
byandell.github.io/Documentation
GitHub Pages
My main GitHub Page byandell.github.io, with source at https://github.com/byandell/byandell.github.io, was modeled on (forked from) https://github.com/barryclark/jekyll-now. This has to cool feature of blog pages.
In addition to my main GitHub Page, I have a separately generated subpage byandell.github.io/ESIIL, with source at https://github.com/byandell/ESIIL, that was forked from https://github.com/CU-ESIIL/Postdoc_OASIS.
- R for Data Sciences GitHub Links
- ESIIL Data Short Course: Create your own portfolio webpage
- GitHub Pages Documentation
- Publish Your Project Documentation with GitHub Pages
- GitHub Page Themes
- Jekyll Now
- MkDocs (advanced topic)
- Resolving Git Push for CI/CD Workflows (TutorialPedia)
Connect
Posit’s Connect is a platform for sharing resources such as R shiny apps, Quarto documents, and python apps.
Deployment of apps using GitHub repos to a Connect server can be tricky, as Connect relies on the renv package to create reproducible environments for your R projects. A message like Deployment error: unknown package source indicates that the renv package does not recognize where a package was installed, for instance if one uses devtools::install_github(). renv cannot track the source well enough to reproduce it, and it refuses to bundle the app as a result. The fix is to reinstall the package using renv::install() instead, which records the GitHub source in a way that renv can reproduce:
renv::install("github_user/package_name")
renv::snapshot()
After running those two lines, retry the deployment. The snapshot validator should pass and the bundle should reach the server cleanly. If for any reason that does not work, you can also try explicitly recording the source before deploying:
renv::record("github_user/package_name")
CodeSpaces
Always stop a codespace when done to save resources!