-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add a hubTemplate section that describes how to access hub data from S3 #22
Comments
I'm wondering how best to organize the cloud documention, given that we have a related open issue about expanding cloud documentation for hub admins: hubverse-org/hubDocs#92 Option 1 Add a separate hubverse.io/
├─ About/
├─ Quickstart - hub administration/
├─ User Guide/
├─ Developer Guide/
├─ Hubverse Cloud Hosting/
│ ├─ overview
│ ├─ onboarding to cloud
│ ├─ accessing cloud data
│ ├─ developer-related cloud stuff
├─ Code of Conduct/
Option 2 Add cloud topics to existing documentation structure, e.g., hubverse.io/
├─ About/
├─ Quickstart - hub administration/
│ ├─ onboarding to cloud
├─ User Guide/
│ ├─ accessing cloud data
├─ Developer Guide/
│ ├─ developer-related cloud stuff
├─ Code of Conduct/
|
I like option two because it integrates cloud hosting into the other topics so that one can decide whether to pursue the cloud path in any given approach. |
Also I think accessing cloud data should fall under a more general topic of accessing data. The mechanics are the same between local and cloud, you just point to a different location |
Thanks for weighing in! Wrong issue! For this issue, we decided to limit the scope of the data access documentation to the READMEs of individual hubs and hub dashboards (starting with the templates, and then submitting PRs to hubs that are hosted on the cloud). This will help surface the data access information where people are looking for it (we can add to the revised Hubverse website when the time comes). |
Moved the dashboard-template part of this work to its own issue: hubverse-org/hub-dashboard-template#4 |
Background
@nickreich noted on Slack that Hubverse hubs that sync their data to AWS:
The Hubverse should do a better job of advertising data available on S3.
Definition of done
Once we agree on the wording and location for this info in the above templates, the follow-up work will be submitting PRs to existing hubs with data on S3.
The text was updated successfully, but these errors were encountered: