ricochet-rs/ricochet

Use for questions about making an app, report, notebook, or script work once deployed, such as keeping a SQLite or DuckDB database or other files across deployments, which content type or entrypoint to use, which port to listen on, links that break under /app/<id>, or serving a rendered report as a website, for Shiny, Plumber, plumber2, Ambiorix, FastAPI, Flask, Dash, Streamlit, Shiny for Python, Genie, Dash.jl, HTTP.jl, Quarto, R Markdown, Jupyter, and R, Python, or Julia scripts.

Use for questions about triggering an R, Python, or Julia script, a Quarto or R Markdown report, or a Jupyter notebook to run on demand or in response to an event, such as running it now, from code, from CI, from a webhook or GitHub push, or after another job finishes, including ricochet task invoke, the invoke API, webhook receivers in FastAPI, Plumber, or HTTP.jl, and redeploying from CI.

Use for any request to deploy, publish, host, share, or put online a Shiny app, Plumber or plumber2 API, Ambiorix, FastAPI, Flask, Dash, Streamlit, Shiny for Python, Genie, or Dash.jl app, a Quarto or R Markdown report, a Jupyter notebook, or an R, Python, or Julia script, and for installing the ricochet CLI, getting a server, signing in, writing _ricochet.toml, environment variables, running and scheduling tasks, deleting content, and CLI errors.

Use for questions about where a deployed project's R, Python, or Julia packages install from, such as slow package installs during a deploy, using binary packages or a faster CRAN mirror, setting CRAN to cran.rpkgs.com, adding a Posit Package Manager or p3m.dev repository, or using a private CRAN-like repository or Python index.

Use for questions about how much CPU or memory a deployed app, script, report, or notebook gets, such as an app or task running out of memory, giving a script more CPU, setting memory or CPU limits and requests, or a package install that times out during a deploy, for R, Python, and Julia apps and tasks.

Use when calling the Ricochet REST API from code or curl, including finding an endpoint in the API docs, creating an API key, running a task and waiting for it to finish, reading deployments and their logs, changing a schedule or settings, and listing content, from R, Python, Julia, shell, or CI.

Use for questions about scaling a deployed app to handle more users, such as setting the minimum and maximum number of instances, keeping an app warm to avoid slow first loads, how many connections one instance takes, when a new instance starts, or why a Shiny app disconnects after a while, for Shiny, Plumber, FastAPI, Flask, Dash, Streamlit, Shiny for Python, Genie, and other apps.

Use for any question about how to schedule a Python, R, or Julia script, set up a cron job, or make a script, Quarto or R Markdown report, or Jupyter notebook run automatically, such as nightly, every weekday morning, hourly, or monthly, by deploying it to Ricochet as a scheduled task, including writing the cron expression, converting local times to UTC, and changing or removing the schedule later.

Use for questions about why a deployed Shiny app, API, report, notebook, or R, Python, or Julia script fails to deploy, start, or run, such as a failed or out-of-sync deployment, package install errors, an app stuck loading or never binding its port, missing styles or broken links, data lost after a redeploy, a failing task run, a different R or Python version, or finding the logs that explain it.

Use for questions about authenticating users or finding out who is signed in to a deployed app, such as how to authenticate a Shiny app, get the current user's name or email, show per-user data, or restrict pages by group or role, in Shiny, Plumber, plumber2, FastAPI, Flask, Streamlit, Dash, Shiny for Python, Genie, or HTTP.jl.