\n {{ `Log in with your ${authName} credentials` }}\n
\n\n\n You don't have permission to access this page.\n
\n\n You need to confirm your account before proceeding.\n You should have received an email with a link that will allow you to confirm your account.\n
\n\n\n It may take a few minutes for the email to arrive; you might also need to check your Spam or Junk folder.\n
\n\n\n You need to confirm your account before proceeding.\n
\n\n\n Ask your {{ serverSettings.systemDisplayName }} administrator to visit your user profile\n and obtain an account confirmation link for you.\n
\n\n You can\n
\n We need a little more information to finish setting up your account.\n
\n\n You're almost done configuring R to publish content to Posit\n Connect. Click the Connect button below to link your Posit\n Connect account ({{ username }}) to\n the rsconnect R package.\n
\n\n\n If you didn't reach this screen by initiating an account link from the\n RStudio IDE or in R via rsconnect::connectUser, click Cancel.\n
\n You've successfully connected the rsconnect package\n to Posit Connect! If you're using the RStudio IDE, click the\n Connect Account button to finish adding this account.\n
\n\n\n Now you are ready to publish a\n
\n We couldn't connect your account. Try connecting again, and contact\n your administrator if the problem persists.\n
\n \n\n \n\n If this was in error, please read the\n
\n Are you sure you want to request \"{{ privilege }}\"\n Permissions on this server? This will contact the\n {{ systemDisplayName }} administrator on your\n behalf to request these additional privileges.\n
\n \n \n\n Your user account ({{ username }}) has insufficient\n privileges to publish content to Connect.\n
\n Removing an environment can prevent the execution of content\n currently assigned to use that environment.\n
\n\n Proceed only if you are comfortable with this potential effect on published content.\n
\n\n Are you sure you want to remove the environment titled:\n
\n\n \n {{ environment.title }}\n \n
\n\n which references the image:\n
\n\n \n {{ environment.name }}\n \n
\n\n {{ systemDisplayName }} could not find available branches.\n Double-check your repository permissions.\n
\n\n Scanning returned the error: {{ branchScanningError }}\n
\n\n Scanning is taking too long.\n
\n\n The selected branch does not contain deployable content.\n No directory with a manifest.json was found in that branch.\n Click \"Back\" to use a different branch.\n
\n You can make a directory deployable by creating a manifest.json using\n the R function rsconnect::writeManifest() or the\n Python CLI rsconnect write-manifest\n See the\n
\n Scanning is taking too long.\n
\n\n We will not show you these examples next time you login.\n
\n\n\n To view them any time, just pick Jump Start Examples from the Publish menu.\n
\n\n{{ selected.description }}
\nOverride this, please.
\n\n\n\n","\n\n\n\n To publish a Jupyter notebook to {{ systemDisplayName }}, first install\n the rsconnect-jupyter plugin in your Jupyter environment.\n
\n\n
\n If you already have a Jupyter notebook, open it. If\n not, go ahead and make one.\n
\n\n
\n Python users can publish to {{ systemDisplayName }} using Jupyter Notebooks\n , a popular tool for literate programming. Rendered notebooks can\n be deployed to {{ systemDisplayName }} for easy distribution, or the source notebook\n and environment can be published making it easy to refresh,\n schedule, and distribute.\n
\n\n Unzip {{ zip }}, then navigate to the {{ dir }}\n directory and upload {{ source }} from within Jupyter:\n
\n
\n
\n Once your notebook is published, you control who can access it,\n when it gets updated, and much more via its settings panels.\n
\n \n \n\n In the Jupyter toolbar, press the\n Publish\n button and follow the on-screen instructions.\n
\n\n
\n If you don't see the Publish button, the required\n rsconnect-jupyter plugin has not been correctly installed in your\n Jupyter environment.\n
\n\n\n Note:\n You must have a matching version of Python installed and configured\n on the {{ systemDisplayName }} server.\n
\n\n\n Use the Upload command in the Files pane\n to upload {{ zip }}, and then open\n {{ rprojLegend }} from within the IDE.\n
\n Unzip {{ zip }} locally, then open\n {{ rprojLegend }} from within the IDE.\n
\n Use your desktop version, or Posit Workbench if your organization\n supports it.\n
\n\n Advanced:\n Using pins is an advanced topic that requires an understanding\n of environment variables and using an API key.\n
\n\n\n The following environment variables must be set locally and within {{ systemDisplayName }} for pins to work:\n
\n\n\n {{ variables }}\n \n \n In the IDE, press the\n Publish\n button in the upper-right corner of\n the Source pane or the Output pane and follow the on-screen instructions.\n
\n\n
\n If you're publishing for the first time, enter the URL for {{ systemDisplayName }}:\n
\n\n\n {{ serverAddress }}\n \n \n Note:\n Publishing for the first time can often take a while,\n since {{ systemDisplayName }} will download and build all dependent packages.\n
\n\n\n
\n If you already have an R Markdown file, open it. If not, go ahead\n and make one.\n
\n\n
\n \n R Markdown is the underpinning for persuasive, dynamic, data-driven\n documents. Combine text, tables and visualizations in a seamless\n story. Schedule updates, and email the results automatically to\n your colleagues.\n \n
\n\n \n Let's walk through how to publish one.\n \n
\n\n Once your pin is published, you control who can access it,\n when it gets updated, and much more via its settings panels.\n
\n \n \n{{ source }}\n and run the example by pressing the\n {{ buttonAction }}\n button in the Source pane header.\n \n \n \n Note:\n \n The RStudio IDE will prompt you to install any required packages\n — this may take a few minutes.\n
\n\n If you already have a Plumber API file, open it. If not, go ahead\n and make one.\n
\n\n
\n Deploy a model for other systems to use in production via a Plumber\n API. Plumber and {{ systemDisplayName }} make it easy to create and deploy RESTful\n Web APIs using R.\n
\n\n Let's walk through how to publish one.\n
\n\n Once your Plumber API is published, your code can be accessed from\n other systems. You control who can access it and more via its\n settings panels.\n
\n \n \n\n Unzip {{ zip }} locally, and open a command prompt to the unzipped\n project directory.\n
\n {{ installCode }}\n \n\n \n Use the rsconnect-python package to deploy the unzipped project.\n Replace <api-key> with a valid API key.\n
{{ deployCode }}\n \n To publish {{ primaryKind }} content to {{ displayName }}, first install\n the rsconnect-python package in your Python environment.\n
{{ connectCode }}\n\n \n Once your Python API is published, your code can be accessed from\n other systems. You control who can access it and more via its\n settings panels.\n
\n \n \n\n Once your Bokeh app is published, you control who can access it,\n its runtime settings, and much more via its settings panels.\n
\n \n \n\n Once your Dash app is published, you control who can access it,\n its runtime settings, and much more via its settings panels.\n
\n \n \n\n Once your Python FastAPI is published, your code can be accessed from\n other systems. You control who can access it and more via its\n settings panels.\n
\n \n \n\n Once your Shiny app is published, you control who can access it,\n its runtime settings, and much more via its settings panels.\n
\n \n \n\n Once your Streamlit app is published, you control who can access it,\n its runtime settings, and much more via its settings panels.\n
\n \n \n\n Once your Vetiver API is published, your code can be accessed from\n other systems. You control who can access it and more via its\n settings panels.\n
\n \n \n\n A Quarto installation is needed to render and publish Quarto content.\n
\n\n RStudio and Posit Workbench users have Quarto available by default in\n the RStudio UI, at the R console, and in the integrated terminal.\n
\n\n Please\n
\n
\n Once your content is published, you control who can access it,\n when it gets updated, and much more via its settings panels.\n
\n \n \n\n Use the rsconnect package to deploy the unzipped project.\n
\n\n\n If this is your first time publishing from RStudio, you need to\n
\n Publish your content by using the R console to run the following command:\n
\n\n\n {{ publishCode }}\n \n\n \n Note:\n Publishing for the first time can often take a while,\n since {{ systemDisplayName }} will download and build all dependent packages.\n
\n\n\n If you already have a Quarto file or project, open it. If not, go\n ahead and make one. It is strongly recommended that you use\n v2022.02 or newer of the RStudio IDE, which includes support for editing\n and previewing Quarto documents.\n
\n\n
\n Quarto is an open-source scientific and technical publishing\n system built on Pandoc. Author with scientific markdown. Create\n dynamic content with Python, R, and Observable. Publish articles,\n reports, presentations, websites, and more.\n
\n\n Let's walk through how to publish Quarto content.\n
\n\n Note:\n Quarto publishing is not available.\n To publish Quarto content, an adminstrator must install and\n configure Quarto on this server.\n
\n\n
\n Declare one or more params in the YAML header and use those params\n in your R Markdown code.\n
\n\n
\n \n Adding parameters to an R Markdown document gives you all the joy\n of R Markdown plus interactivity. When you add params to an R\n Markdown document, you and others can provide inputs to dynamically\n tailor the resulting report.\n \n
\n\n \n Here's how to publish and interact with one.\n \n
\n\n Once published, anyone with access can change the input parameters\n via the Input panel in {{ systemDisplayName }}.\n
\n\n The resulting customized reports can be saved and shared with\n others, or kept private.\n
\n \n \n\n Once your document is published, you control who can access it,\n when it gets updated, and much more via its settings panels.\n
\n \n \n\n If you already have a Shiny App, open it. If not, go ahead and make\n one.\n
\n\n
\n Shiny is an R package that makes it easy to build interactive web\n apps straight from R.\n
\n\n Let's walk through how to publish one.\n
\n\n Once your Shiny App is published, you control who can access it,\n its runtime settings, and much more via its settings panels.\n
\n \n \n\n Need permissions to publish content?\n
\n\n No content has been published, or none is visible to you. You are currently a Viewer.\n If you think you should have publisher permissions, you can submit a request.\n
\n\n Start publishing and sharing!\n
\n\n You have no visible published content. You can get started with\n publishing new content by clicking the Publish button.\n
\n \n\n Oops, no luck with that search.\n
\n\n Try using a different search query or refer to the\n
Showing {{ itemStart }} to {{ itemEnd }} of {{ total }}
\n \n0 results
\n \n\n The definition of the tagging schema for the content in your\n organization starts with categories. Within each category, you define tags,\n which can be nested any number of levels deep.\n
| \n {{ log.time }}\n | \n\n {{ log.userDescription }}\n | \n\n {{ log.eventDescription }}\n | \n \n
\n These settings are controlled by your configuration file.\n
\n \n Please visit the\n{{ reportResults.run.hostname }}\n \n ✅ {{ reportResults.run.passed }} passed\n
\n\n ⚠️ {{ warnings }}\n
\n\n {{ result.test.description }}\n
\n{{ result.output }}\n {{ result.error }}\n \n {{ helpText }}\n
\n\n Oops, it looks like you have more than your licensed number of active users!\n Please contact \n {{ salesEmail }}\n \n
\n \n \n\n The usage scorecard indicates what top line Posit Connect features\n you have used.\n
\n\n To help improve Connect, you can send Posit this usage information\n from time to time by copying the scorecard and emailing us.\n
\n \n{{ hasData ? usageMetricsReport : 'Unable to load usage scorecard data.' }}\n\n \n The usage scorecard data has been copied. Please paste it into an\n email and send it to\n
\n Thank you for making Posit Connect better!\n
\n\n Learn more about our privacy policy:\n