R or Python content via a variety of m ethods: push-button, CLI, git-backed, or Server API. 2 Execution Publish static content, or source code-backed item s. Set up docum ents to run on a schedule, control resource allocation to interactive applications and APIs. 3 M anagem ent Control the m etadata associated w ith a content item . Publish new versions in place, roll forw ard/backw ard. Access scheduled report history. Add organizational tags. Track the usage m etrics. 4 Distribution Add view ers and collaborators. Set a vanity URL. Schedule a custom em ail to be set on success criteria.
explicitly grant themselves content access ◦ Actions are audited ◦ Special access to the Admin tab and certain content settings • Publishers ◦ Can upload new content items • Viewers ◦ Can see content items • Content Collaborators ◦ Can publish new versions ◦ Manage settings ◦ Download source bundles (code) • Content Viewers ◦ Can only see and interact with the content itself Content Privileges
18.07 LTS & 20.04 LTS • SLES 12 SP5 • SLES 15 SP2 / openSUSE 15.2 *Distributions such as Rocky Linux and AlmaLinux can be used as long as they stay 1:1 binary compatible with RHEL 8. CentOS Stream is not supported by RStudio.
live on long-running Linux servers. RStudio products are entirely compatible with treating a container like the underlying Linux server to better encapsulate dependencies and diminish server statefulness. In this model, each RStudio product is placed in its own long-running container and treated as a standalone instance of the product. Multiple containers can be load-balanced and treated as a cluster. These containers can be managed by a Kubernetes cluster, should you wish. There are some specific considerations for running RStudio products in containers, which are detailed in this article.
Hosted Evaluation https://www.rstudio.com/products/connect/evaluation/ 2. Useful but you have to DIY: 45-day Evaluation Key https://www.rstudio.com/products/connect/download-commercial/
Groups Current-User Execution Password (built-in) Yes (can also be disabled) Groups must be managed locally in Connect No PAM No Groups must be managed locally in Connect Yes (per-app basis) LDAP/AD No Groups can come from the Provider or be local to Connect No SAML No Groups can come from the Provider or be local to Connect No OIDC - Google No Groups must be managed locally in Connect No OIDC - Others No Groups can come from the Provider or be local to Connect No Proxied through an external service No Groups can come from the Provider or be local to Connect No
Connect Installations require open dialog between admins and publishers. • Do you know who your Publishers are? • Do your Publishers know who you are? • Do you know what types of content they will be publishing? • Do you know what versions of R and Python they'll need? • Do you know how they plan to connect to data sources? This is also your chance to make any Dev/SecOps policies and expectations known.
place limits on allowed viewership? (all, logged_in, acl) ◦ Applications.MostPermissiveAccessType ◦ Applications.AdminMostPermissiveAccessType Vanity URL Management • Will Publishers be allowed to set vanity URLs for content? ◦ Authorization.PublishersCanManageVanities Content Organization: Tags • Work with your Publishers to set up a Tag Schema for content organization
between processes • Application owners can set Minimum and Maximum processes • Use Scheduler.MinProcessLimit to cap resources if this becomes a problem • Scheduler.MaxProcessLimit is also available
for an app to start Scheduler.InitTimeout = 60s • The minimum time to keep a worker process alive after it goes idle Scheduler.IdleTimeout = 5s After the last user disconnects from a process, RStudio Connect waits 5s before that process is reaped. You might want to increase Scheduler.IdleTimeout if you have a process that is resource-intensive to start up.
scheduled reports to run in parallel • Setting this to zero will disable scheduled execution This lets you control (throttle) scheduled content execution • If all your publishers schedule reports to run at midnight, Connect will iterate through them as quickly as possible.
Content bundles (uploaded compressed bundles from users) • Unzipped bundles for running applications • Package cache ◦ One copy of each version of each package specific to the R (or Python) version • Metrics (RAM and CPU usage) • R/Python process information/logs
each content item • Applications.BundleRetentionLimit (default 0, which retains everything) If you experience problems with large bundles: • Ask publishers not to package large sets of data in the content bundle and provision data on the server separately
disk for any one application: ◦ Jobs.MaxCompleted (default: 1000) • Maximum age of a completed job retained on disk: ◦ Jobs.OldestCompleted (default: 30d) On-disk job metadata is removed if either the MaxCompleted or OldestCompleted restrictions are violated. Adjust this retention window based on your auditing requirements.
Here are some cases where the reward is worth the effort: • When you are working on a long-term project, and need to safely upgrade packages. • In cases where you and your team need to collaborate on the same project, using a common source of truth. • If you need to validate and control the packages you’re using. • When you are ready to deploy a data product to production, such as a Shiny app, R Markdown document, or plumber API.
package repository. Hosting an internal repository allows organizations to: • Share and version their internal packages • Access and govern packages from external sources • Audit package use
and recommendations for Using R for Validated Work ❏ Can you recreate your environment? ❏ Can you trust the things in your environment? ❏ Learn about the Validated Environment Strategy ❏ Learn about Internal Package Repositories
your own. • Direct logged-in users to a landing page of your choice when they first enter RStudio Connect. • Generate custom content landing pages with R code using connectwidgets. • Customize what anonymous and logged-out users see when they visit your server. • Control email settings such as sender display name, “from” address, sender address headers, and subject prefix. • Hide the Documentation tab from viewers.
anonymous or logged-out users will see. Workbook Exercise: Use the Server.LandingDir configuration setting to specify the path to a directory that contains index.html and all assets (CSS, images, javascript, etc.)
Users • Server.RootRedirect (Default: The Server.Dashboard path) The URL logged-in users will be redirected to when visiting the public URL used to access the server. • Server.DashboardPath (Default: "/connect") The URL path name to be used where RStudio Connect's dashboard is hosted. One option for creating a custom landing page is to make a content showcase with the connectwidgets R package.
Page Customization • Managing multiple clients ◦ User Isolation: Authorization.ViewersCanOnlySeeThemselves, Server.HideEmailAddresses ◦ Viewer Restrictions: Server.ViewerKiosk When enabled, users with viewer role will not be allowed to submit permission requests for content access or to request elevated role privileges. • Multiple authentication providers ◦ Federated authentication: RStudio Connect will authenticate against an external identity provider (usually via SAML), and the provider will federate identity management to all the different authentication providers.
file: Is Server.Address set? ❏ Verify your email server configuration: Send a test email ❏ Maintain an open dialog with your publisher users ❏ Before you start publishing content: ❏ Make an informed decision about your authentication provider ❏ Make an informed decision about your package repository ❏ Life is better with Package Manager or an Internal Repository
if a valid license is available: sudo /opt/rstudio-connect/bin/license-manager status • The Connect dashboard will display a notification to admins and publishers when the license is within 15 days of expiration. • You can disable this with Licensing.ExpirationUIWarning
created / pre-provisioned or auto-registered. Details and capabilities differ by authentication provider. ◦ Example: Server API driven user provisioning • Locking Users ◦ Forbids login and publishing ◦ Removes user from your license count ◦ Example: Server API documentation • Removing Users ◦ Last resort option ◦ Could Require content ownership migration
“People” tab ◦ Manage with the RStudio Connect Server API ◦ Disable local group support with: Authorization.UserGroups (existing groups must be removed) • Remote Groups ◦ Management is the responsibility of of the external authentication provider ◦ Group memberships are locally synchronized through successful login events Note! Having a mix of Local and Remote groups on your server is not recommended. Migrate completely from one mode to the other when making a change.
HTML messages to the User Interface: • Server.PublicWarning - Visible on the unauthenticated landing page • Server.LoggedInWarning - Visible above recent content when logged in ◦ Useful for things like scheduling maintenance windows
2022, RStudio Connect will no longer support Python 2. Factors that have gone into our decision include the following: • Python 3 is now widely adopted and is the actively-developed version of the Python language. • In January 2021, the pip 21.0 release officially dropped support for Python 2. • A large number of projects pledged to drop support for Python 2 in 2020 including TensorFlow, scikit-learn, Apache Spark, pandas, XGBoost, NumPy, Bokeh, Matplotlib, IPython, and Jupyter notebook.
access control list details for each content item on your RStudio Connect server Example • Audit all the unpublished (orphaned) content items on your RStudio Connect server Example • Audit all the vanity URLs currently in use on your RStudio Connect server Example • Audit all the tags currently in use on the server, and list all the tagged content items Example
information about each visit and the length of that visit Other Content: • Records information about each visit: user, timestamp, content rendering info
for 18 months • We recommend upgrading at least once a year. • Most upgrades should require less than five minutes unless breaking changes have occurred in the interim and require configuration adjustments. • Consult the release notes before undergoing an upgrade.
installation script works across all supported Linux distributions, validates the GPG key of the downloaded package, and includes support for offline use. Example: curl -Lo rsc-installer.sh https://cdn.rstudio.com/connect/installer/installer-v1.9.5.sh sudo -E bash ./rsc-installer.sh 2021.10.0
server diagnostic report: If you are on RStudio Connect version 1.7.2 and later, run the following command on the server and send us the output: sudo /opt/rstudio-connect/scripts/run-diagnostics.sh /path/to/output/dir
the publication, execution, management, and distribution of their work in a safe and sophisticated manner, fully sanctioned by their IT admins. Strategic Goals: Increase the types of content available to share, improve content discovery and management, and facilitate production deployments. Early 2022 Administrators can enable remote content execution on a Kubernetes back-end while maintaining easy self-serve publishing. • Publishers are able to drive viewer engagement on their work • Publishers can manage process automation workflows • Feature parity for Python users • Extend Cloud Native capabilities to ease integrations • Improvements to Docker-friendly installation October 2021 BI Integration: Extend Tableau dashboards with R, Shiny and Python
in December, runs until the GA launch in early 2022 • Beta will not have feature parity with RStudio Connect local execution Sign-up form Requirements: • A Kubernetes cluster where you have full cluster-admin privileges • A PostgreSQL database that meets Connect’s requirements • An NFS server that meets Connect’s shared storage requirements • Willingness to provide feedback on the installation/configuration process • Publishers who are willing to provide feedback
kellobri
colly
jnunemaker
skipperchong
morganepeng
scottboms
quramy
yeseniaperezcruz
productmarketing
ufuk
sferik
philhawksworth
tanoku
