Skip to content

Commit 2c34805

Browse files
committed
update readme and double checking continuous deply
1 parent b6b3753 commit 2c34805

File tree

1 file changed

+11
-2
lines changed

1 file changed

+11
-2
lines changed

_README2_how-to-build-this-website.md

Lines changed: 11 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -10,9 +10,18 @@ This site is built with R Markdown's website feature. [Read more about websites
1010
- knit Rmd docs one at a time from within the script editor
1111
- In console: `rmarkdown::render_site(encoding = 'UTF-8')`
1212

13-
3. Copy /docs web to the serving location
13+
3. Hosted by Netlify.com
1414

15-
**UPDATE**: I've just written this script using `library(fs)` that creates a link from ~/blogdown/static/map to the "docs" directory. This may obviate the need to run step three continuously. Not sure if I have to run that script (`_ZZ_move_HTML-docs_to_blog-dir.Rmd`) more than once (i.e. after every site "Build" operation.)
15+
1. After committing and pushing to github
16+
1. Login as the owner of the GitHub repo
17+
1. Separate tab, login to Netlify.com
18+
1. Associate Netlify New Site deploy with the GitHub Repo
19+
1. Associate Netlify to the `docs` subdir of the gitHub repo
20+
1. Now each GitHub commit will result in a new deploy on Netlify.
21+
1. You May want to check how the domains are handled on Netlify. And, you may want to check how redirects are handled, e.g. netlify.toml
22+
23+
24+
**UPDATE-OLD No Longer in effect**, but keeping around b/c the code might be useful to me again some day. This script using `library(fs)` that creates a link from ~/blogdown/static/map to the "docs" directory. This script uses `library(here)` and `library(usethis)` to create a sym-link from one repo to another on my local file system. But this is clunky and so I've moved to the above, step 3 above. (`_ZZ_move_HTML-docs_to_blog-dir.Rmd`)
1625

1726
- e.g. github repo served by Netlify
1827
- in this case: rfun (blogdown-rfun2 on github)

0 commit comments

Comments
 (0)