New tutorial on using R keyring

[falkmielke]

Description

Sharing some best practices which I experienced when using keyring in a set of automated scripts.

Related Issue

None.

Task list

• My tutorial or article is placed in a subfolder of tutorials/content/
• The novel tutorial has a meaningful name, in relation to the content of the tutorial.
• The filename of my tutorial or article is index.md. In case of an Rmarkdown tutorial I have knitted my index.Rmd to index.md (both files are pushed to the repo).
• yaml header:
  • (recommended) I am included as author in the authors yaml tag, using [MY_AUTHOR_ID]. An author information file exists in <tutorials>/data/authors/<author>.toml.
  • I have added categories to the YAML header and my category tags are from the list of categories.
  • I have included meaningful and applicable tags (i.e. keywords) in the YAML header to improve the visibility of the new tutorial (see the tags listed in the tutorials website side bar).
  • The date is in format YYYY-MM-DD and adjusted.
• (recommended) I have previewed this PR locally (see steps below; ask previous contributors for help) and confirmed that the new content renders as expected.

Previewing the pull request

Thanks to GitHub Actions, an artifact (=zip file) of the rendered website is automatically created for each pull request.
This provides a way to preview how these updates will look on the website, useful to contributors and reviewers.

Instructions to preview the updated website

1. On the PR page, you can find a "details" link under "checks - On PR, build the site and ...". Go there, click on the top link in the left sidebar ("Summary"), and download the generated artifact at the bottom of the page.
2. Decompress it into a target directory, e.g. Downloads/tutorials_preview.
3. To preview the website, use a program which can serve http sites on your local machine. One such option is the servr package in R: & '\C:\Program Files\R\R-4.4.2\bin\Rscript.exe' -e "servr::httd('./tutorials_preview')" -p8887 (make sure to adjust the path to your Rscript.exe; on Linux, simply use Rscript -e [...]).
4. Point your browser to http://localhost:8887.
5. Review the updated website. As a contributor, you can push extra commits to update the PR. As a reviewer, you can accept/refuse/comment the PR.

Note: for step 3, you can use any other simple HTTP server to serve the current directory, e.g. Python http.server: python -m http.server 8887 --bind localhost --directory path/to/tutorials_preview

Alternative: Locally Building the Site

Alternatively, you can build the entire site locally (see the README for instructions); the Hugo preview server will update changes on the fly.
This requires Hugo to be installed on your computer.

[falkmielke]

this is ready to be reviewed, thank you!

[RCinbo]

I've read your tutorial with great interest and have made some small textual suggestions.
I have only used keyring once in one repository.
What I often do, is store passwords as environmental variables in an .Renviron file (include this file in gitignore so it is not shared) and then get them when I need them with Sys.getenv(). It's simpler then what I read here but probably not as safe since anyone with access to my computer can read it...

[falkmielke]

Thank you @RCinbo for reviewing and finding the typo's.
I agree, the environment variables are a quick option, but usually less safe.

I have re-read it as well; ready for publication from my side.