diff --git a/404.html b/404.html new file mode 100644 index 0000000..a0857c3 --- /dev/null +++ b/404.html @@ -0,0 +1,115 @@ + + +
+ + + + +YEAR: 2020 +COPYRIGHT HOLDER: Sean Davis ++ +
Copyright (c) 2020 Sean Davis
+Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
+The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
+THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
+vignettes/HOWTO_BUILD_WORKSHOP.Rmd
+ HOWTO_BUILD_WORKSHOP.Rmd
First, this package doesn’t do much except add a template Github +Action to build all the pieces necessary for a workshop.
+ +To accomplish this follow each of the 7 steps below. Once your edit +the yaml files, Github actions will run each time you commit to github +and will create for you:
+Clone this repo, fork and rename it,
+OR
+(PREFERRED) create a repo from this template
+DESCRIPTION
file
+Depends: Biobase Suggests: knitr, rmarkdown, pkgdown If your packages
+depend on a github R repos, be sure to specify the correct repo
+username/reponame
. Installation will deal with this.
In your repository, click on settings or url https://github.com/*GITHUB_USERNAME*/*REPO_NAME*/settings. +Midway down the page, in the GitHub Pages section, select source +‘gh-pages branch’. If only ‘master branch’ is visible, select master for +now, but once Github actions runs, ‘gh-pages branch’ will be available +and is required to render the website.
+In the DESCRIPTION file, update the URL: to the website url eg https://seandavi.github.io/BuildABiocWorkshop/ (but +substitute your own repo, etc.)
+Edit the file _pkgdown.yml, updating the url:, title and href: which +should be your website url, title of your workshop and github repos url +respectively. You do not need to edit this file further. You do not need +to add menus or links to vignettes. GitHub Actions and pkgdown will do +this when it builds the website
+.github/workflows yaml
as needed (likely no
+need)
+You do not need to create a docker image manually. Github actions
+will read Dockerfile located in this template, and using the yaml files
+will create, build and push to the Github Container Registry an image
+with the name (default)
+ghcr.io/yourgithubuser/yourgithubreponame
, all
+lowercase.
In the DESCRIPTION file, the DockerImage: should match your +the docker image name (should be lowercase).
+Edit the README.md. and add one or more Rmd vignettes that will
+constitute the workshop materials. It is normal R package that should
+pass rcmdcheck::rcmdcheck()
, and be installed using regular
+R package install commands.
vignettes/workshop_example.Rmd
+ workshop_example.Rmd
Authors: Author Name2, Another Author3.
Last modified:
+14 May, 2018.
Along with the topic of your workshop, include how students can +expect to spend their time. For the description may also include +information about what type of workshop it is (e.g. instructor-led live +demo, lab, lecture + lab, etc.). Instructors are strongly recommended to +provide completely worked examples for lab sessions, and a set of +stand-alone notes that can be read and understood outside of the +workshop.
+List any workshop prerequisites, for example:
+List relevant background reading for the workshop, including any +theoretical background you expect students to have.
+List any R / Bioconductor packages that will be +explicitly covered.
+An example for a 45-minute workshop:
+Activity | +Time | +
---|---|
Packages | +15m | +
Package Development | +15m | +
Contributing to Bioconductor | +5m | +
Best Practices | +10m | +
List “big picture” student-centered workshop goals and learning +objectives. Learning goals and objectives are related, but not the same +thing. These goals and objectives will help some people to decide +whether to attend the conference for training purposes, so please make +these as precise and accurate as possible.
+Learning goals are high-level descriptions of what +participants will learn and be able to do after the workshop is over. +Learning objectives, on the other hand, describe in very +specific and measurable terms specific skills or knowledge attained. The +Bloom’s Taxonomy may be a useful framework for +defining and describing your goals and objectives, although there are +others.
+Divide the workshop into sections (## A Section
).
+Include fully-evaluated R code chunks. Develop exercises and
+solutions, and anticipate that your audience will walk through the code
+with you, or work on the code independently – do not be too ambitious in
+the material that you present.
This package is a template for building a Bioconductor workshop. The package includes Github actions to:
+DESCRIPTION
file)rcmdcheck::rcmdcheck
+ghcr.io/gihub_user/repo_name
, all lowercase.Package authors are primarily responsible for:
+DESCRIPTION
file as the URL
.DockerImage:
in the DESCRIPTION
file.Both of those tasks can be accomplished using the Github actions included in this template package. The vignette accompanying this package describes how to accomplish both of these tasks.
+pkgdown
website at https://YOURUSERNAME.github.io/YOURREPOSITORYNAME/
+latest
, sha-XXXXXX
where XXXXXX
is the hash of the current master
commit, and master
.Once running, navigate to http://localhost:8787/ and then login with rstudio
:yourchosenpassword
.
To try with this repository docker image:
+ +NOTE: Running docker that uses the password in plain text like above exposes the password to others in a multi-user system (like a shared workstation or compute node). In practice, consider using an environment variable instead of plain text to pass along passwords and other secrets in docker command lines.
+