R Shiny at IQSS
  • Introduction
  • Getting started
    • Determining your resource requirements
    • Applying for an account
  • Deploying
    • Setup your environment
    • Deploying an example Shiny app
    • Bootstrapping a new Shiny app or migrating a pre-existing Shiny application
    • Developing locally with RStudio
    • Developing locally using Docker
    • Speeding up deployments with Packrat
  • Configuration
    • Setting up a custom domain for your Shiny app
    • Installing additional system-level packages
    • Limiting the number of R Threads
  • Best Practices
    • File storage
    • Using promises
    • Adding routes
  • Troubleshooting
    • Resolving Application Error screen
    • Viewing app logs
    • Viewing resource consumption
    • Configuring Shiny session auto-reconnect
    • Getting support
Powered by GitBook
On this page
  1. Best Practices

File storage

PreviousBest PracticesNextUsing promises

Last updated 5 years ago

Never commit large files to your Git repository. This will slow down all deployments and may make your project undeployable.

Your Shiny application may use large CSVs, JPEGs, PNGs, etc. Large binaries or large CSVs should be stored in Amazon S3 or in a database.

Heroku allows you to provision addons for your app, including databases like PostgreSQL or S3 buckets for asset storage.

Explore the .

For storing images, we suggest using .

Most add-ons when provisioned add environment variables to your Shiny application which contain the credentials and paths to access these add-ons from your code.

Please start with the lowest tier of each add-on you're using. If you need a larger database, S3 bucket, or other add-on, contact support to discuss options. E-mail .

add-ons Heroku offers
Bucketeer
support@help.hmdc.harvard.edu