Meta-issue: Deployment
维护者通常 2 天内回复
还没有人认领这个 Issue。
评估
调研方向
尚未确定任何实现文件或测试。首先审查从 Positron 和 Workbench 部署到 Connect 的相关问题，包括 Quarto 报告、Shiny 应用、版本控制、后端连接模式和凭据模式。完成的标准是项目已达成一致的部署设计，并制定了明确范围的实现计划。
由索引模型根据 Issue 内容生成。
描述
This issue exist to track discussions around deployment. For the initial phase we will focus on Connect deployment from Positron and Workbench as this is the stack we control - others may think about deployment in other context if they wish to do so in the mean time.
Key questions:
What does ggsql deployment look like?
Right now deployment would be in the form of a quarto report or some sort. However, the R bindings also support deploying shiny applications with ggsql code inside.
I do envision a mode where you deploy a single .ggsql file and you get an embeddable visualisation. Depending on how ggsql's own multiplot support evolves this may end up being a viable dashboard solution, though I'm not sure SQL provides the best syntax for layout work. If not, do we need a new format for dashboard-y deployments or does quarto serve that need?
For deployment, we also need to think about ggsql versioning. We are in a blissful state of just having to declare a single version and not black pit of 100s of dependencies, but declare it we must somehow. Is this a Connect responsibility or should ggsql itself do something about this?
What kind of backend connection is kept - with what kind of credentials?
Our happy path is that an analyst sits on their computer, developing an analysis using ggsql either in Positron or Workbench. They have their credentials set up so they can connect to e.g. Snowflake and visualise that data directly. They arrive at an end product and hit deploy. The deployment target is send to Connect, along with the credentials and everything just magically works. We must strive for this to be the case!
However, I can see multiple modes of connection with a backend depending on the needs, and also multiple modes of credentials:
Connection modes:
- Keep a connection to the original backend, updates to the database is reflected in the visualisation whenever it is presented
- Cache the main data sources in a local DuckDB instance and query against that in the backend - this may be updated periodically but not real-time
- Embed the data in a "static" deployment (i.e. connection is severed)
Credential mode:
- Use the authors credentials/credentials provided specifically for this deployment. All visits will use the same credentials and it is up to the analyst to not expose confidential information in the visualization
- Visitor brings their own credentials and these are used when querying the database and creating the plot. The visitor only sees data for which they have been granted access. This mode explicitly requires the first connection mode described above
- 主要语言
- Rust
- 星标
- 565
- 派生
- 31
- 平均合并
- 2 天 12 小时
- 30 天内合并 PR
- 16
环境准备
这个项目没有提供开发容器、Dockerfile 或贡献指南，环境需要你自己搭建：先看它的 README，通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
posit-dev/ggsql 的其他 Issue
-
难度 1/5 1 小时以内 新手友好度 88/100
维护者通常 2 天内回复
-
难度 2/5 1-3 小时 新手友好度 68/100
posit-dev/ggsql#565 · 2 个 reaction ·
维护者通常 2 天内回复
-
Update the positron dep for the extension to 0.2.9可能已有人在做 @thomasp85 于 17 天前认领。 未关闭
难度 2/5 1-3 小时 新手友好度 68/100
维护者通常 2 天内回复
-
writer
难度 2/5 1-3 小时 新手友好度 68/100
维护者通常 2 天内回复
-
plot building
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 2 天内回复
相似的 Issue
-
documentation good first issue
难度 2/5 半天 新手友好度 72/100
sujithputta02/Esapay#13 ·
-
needs triage
难度 2/5 1-3 小时 新手友好度 72/100
topgrade-rs/topgrade#2419 ·
维护者通常 1 天内回复
-
review-bot
难度 2/5 1-3 小时 新手友好度 72/100
midagedev/bloomery#318 · 1 条评论 ·
维护者通常 1 天内回复
-
area/infra good first issue type/bug
难度 2/5 1-3 小时 新手友好度 60/100
cristim/AztecCraft#92 ·
维护者通常 1 天内回复
-
Standalone Unix updater reports success when curl fails (`curl | sh` masks the exit status); Windows path is unaffected可能已有人在做 @akhil9tiet 今天认领。 未关闭bug CLI windows-os
难度 2/5 1-3 小时 新手友好度 72/100
维护者通常 1 天内回复