GitHub repository for the Shiny application - deployment-bundle: app.R, manifest.json - README.md The GitHub repository I created to keep the application code can be viewed here: I plan to create a git branching strategy so that new changes can be kept separate from the master branch and reviewed before merging. Development and Git BranchingĪpplication development occurs in the RStudio IDE. This article will not cover the basics of installing and configuring a Jenkins server.

I use Ansible to create (and tear down) small Jenkins servers that live for the duration of my experiments. Oh and i use a metric fuckton of command line.Note: I started this project with a brand new, clean Jenkins Server. The team im on uses rails for alot so i just got used to its addition in my workflow. Theres probably a better way but rails automates alot of the boring db engineering stuff and gives a separate admin platform from the shiny app if I want the shiny app to be user facing but not admin facing as happens sometimes. I also use rails for db management (development vs production) with heroku, then host the shiny app as a separate app on heroku connecting to those rails dbs. Otherwise this is a DREAM develoment setup for me. And it makes git operations generally much much easier.īut sometimes is also causes weird hiccups that can take an hour or two to resolve, but at most thats once a month and usually caused by user error. It is fucking cool to edit in either program and switch to the other and have live updates.

I use github desktop with RStudio (for real time troublehsooting) and VSC (for software engineering principles) with github desktop to develop RShiny dashboards.

Connect rstudio to github