| library(shiny) | |
| # remotes::install_github("yonicd/snapper") | |
| # remotes::install_github("thomas85p/shinyFiles") | |
| library(snapper) | |
| library(base64enc) | |
| library(png) | |
| library(shinyFiles) | |
| js <- ' | |
| function get_img_src() { |
| library(processx) | |
| library(RPostgres) | |
| library(httr) | |
| library(dbplyr) | |
| library(tidyverse) | |
| # this example assumes you've created a heroku postgresql | |
| # instance and have the app name (in this example, "rpgtestcon"). | |
| # use the heroku command-line app |
| # Ruby is our language as asciidoctor is a ruby gem. | |
| lang: ruby | |
| before_install: | |
| - sudo apt-get install pandoc | |
| - gem install asciidoctor | |
| script: | |
| - make | |
| after_success: | |
| - .travis/push.sh | |
| env: |
The git command-line utility has plenty of inconsistencies http://steveko.wordpress.com/2012/02/24/10-things-i-hate-about-git/
A GUI like http://sourcetreeapp.com is often helpful, but staying on the command line usually quicker. This is a list of the commands I use most frequently, listed by functional category:
git status list which (unstaged) files have changed
