SQLite DB backend

March 4, 2019 @chrisengelhardt Chris Engelhardt

@chrisengelhardt wrote:

Hi friends,

We have a shiny application that uses a SQLite DB backend. Our goal is to deploy this application to Connect, but we are unsure of where best to host the DB backend.

We mistakenly had the following configuration in /etc/rstudio-connect/rstudio-connect.gcfg (thinking we could reference it with a path in the app files):

[Database]
Provider = sqlite

[SQLite]
Dir = /var/lib/rstudio-connect/sqlite

However, this specification is problematic for a number of reasons (e.g., this SQLite DB, as specified here, is used for Connect meta data).

In addition, this directory seems to be "masked," as per the documentation on sandboxing (https://docs.rstudio.com/connect/admin/process-management.html#process-management-sandboxing), and in light of this post (https://support.rstudio.com/hc/en-us/articles/360007981134-Persistent-Storage-on-RStudio-Connect), the answer seems to be to host the SQLite backend in a top-level directory (e.g., /sqlite_db).

Will hosting the SQLite backend in, say, /sqlite_db and referencing the location via an absolute path be a viable solution? We're aware of the multiple write problem and will not have the DB hosted on an NFS server. The amount of data written to the DB backend is extremely trivial, which is why we're not considering other options like Oracle, hdfs, or PostgreSQL.

Thanks for the insight anyone might have on this issue.

Best,

Chris

Posts: 10

Participants: 2

Read full topic

Previous Article
RStudio Connect Viewer Account Permissions to Hide Other Users
RStudio Connect Viewer Account Permissions to Hide Other Users

@gibran wrote: Hi, Is there a way to set RStudio Connect viewer account permissi...

Next Video
Accessing and responding to Plotly events in Shiny
Accessing and responding to Plotly events in Shiny

For several years now, the Plotly package has provided an `event_data()` function for accessing click, hove...