This is about continuous deploying an RMarkdown website, but not a blogdown site.
The problem I have is that the site builds inside my RStudio client (in this case, the HTML-site is stored in the _site subdirectory) I can push that to my GitHub remote. I have set Netlify to deploy from that directory. But, the site is already built. Netlify does not seem to get triggered by GitHub, after the push – but will deploy if I manually trigger at netlify. or manually drag the _site folder to netlify.
I have a github repo that uses RStudio to build a site. The build command is an R function, part of the rmarkdown package:
rmarkdown::render_site(encoding = 'UTF-8') That function renders/builds HTML/CSS in the _site sibdirectory. Since this is not a blogdown site, it doesn’t use hugo to build the site.
I’m not sure what to put in the build command for Netlify deployment.
- But do I have to build at Netlify? Can I have netlify trigger from new files in _site subdirectory of the GitHub repo?
I have set the netlify publish directory to _site
Is there some other way or additional settings to get Netlify to trigger by the changes in the GitHub/repo/_site directory? I’ve looked through several pieces of documentation (1 2, these support message, more). So far, what I am seeing documented addresses blogdown/hugo. Sorry if I’m missing something, but I would be grateful for any help.
deploy log from dragging files or manually triggering a deploy: