Tasks
Tasks are content items that run to completion. Unlike apps, which stay running to serve requests, a task runs once and then stops. Examples are an R script that builds a report, a Python ETL pipeline, or a Quarto document that renders to HTML.
See the content items overview for the full list of task types.
Task types
Section titled “Task types”| Content Type | Description |
|---|---|
r | An R script with the extension .R or .r. |
rmd | An R Markdown document. Can be served as a static site. |
quarto-r | A Quarto document using an R runtime. Can be served as a static site. |
Python
Section titled “Python”| Content Type | Description |
|---|---|
python | A Python script with the extension .py. |
quarto-py | A Quarto document using a Python runtime. Can be served as a static site. |
jupyter | A Jupyter notebook with the extension .ipynb. Always served as a static site. |
| Content Type | Description |
|---|---|
julia | A Julia script. |
quarto-jl | A Quarto document using a Julia runtime. Can be served as a static site. |
Working with tasks
Section titled “Working with tasks”- Invoking tasks: run tasks on demand from the UI, CLI, or REST API
- Scheduling tasks: run tasks on a repeating schedule
- Static sites: serve static HTML built by tasks such as R Markdown or Quarto
Deployment
Section titled “Deployment”See the deployment guide to deploy tasks with the CLI or git integration. For project requirements, see the guide for your language: