Skip to content

Encourage users to read tracks documentation#1568

Merged
pquentin merged 2 commits intoelastic:masterfrom
pquentin:encourage-browsing-repo
Aug 30, 2022
Merged

Encourage users to read tracks documentation#1568
pquentin merged 2 commits intoelastic:masterfrom
pquentin:encourage-browsing-repo

Conversation

@pquentin
Copy link
Copy Markdown
Member

This addresses the following user feedback:

I think the main thing that made me not look for documentation was the
message on the repository main page. It gave me the impression I
shouldn't be there unless I want to create my own tracks.

@pquentin pquentin added :Docs Changes to the documentation cleanup Linter changes, reformatting, removal of unused code etc. labels Aug 29, 2022
@pquentin pquentin requested review from DJRickyB and dliappis August 29, 2022 11:29
@pquentin pquentin self-assigned this Aug 29, 2022
Copy link
Copy Markdown
Contributor

@dliappis dliappis left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Left a small nit-y comment.

docs/faq.rst Outdated
---------------------------------------------

Rally comes with a set of tracks out of the box which we maintain in the `rally-tracks repository on Github <https://github.com/elastic/rally-tracks>`_. This repository contains the track descriptions. The actual data are stored as compressed files in an S3 bucket.
Rally comes with a set of tracks out of the box which we maintain in the `rally-tracks repository on Github <https://github.com/elastic/rally-tracks>`_. This repository contains the track descriptions. The actual data are stored as compressed files in an S3 bucket. Each track is documented in README files, including parameters and example data.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

are stored as compress files in an S3 bucket.

This is no longer true (some time now). They are on GCS and served via a CDN/proxy.

I think this is a detail that doesn't matter, and could always change. What if instead we say: as compressed files in a cloud bucket.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed, thanks.

We're using GCS and a proxy now, but it's an implementation detail.
Copy link
Copy Markdown
Contributor

@dliappis dliappis left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

------------------------------

So far the track is only available on your local machine. To share your track you could check it into version control. To avoid committing the potentially huge data file you can expose it via http (e.g. via an S3 bucket) and reference it in your track with the property ``base-url``. Rally expects that the URL points to the parent path and appends the document file name automatically.
So far the track is only available on your local machine. To share your track you could check it into version control. To avoid committing the potentially huge data file you can expose it via HTTP (e.g. via a cloud bucket) and reference it in your track with the property ``base-url``. Rally expects that the URL points to the parent path and appends the document file name automatically.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: as we support http and https maybe we should encourage https in this day and age?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We have many occurrences of "HTTP" in the codebase and the docs, I don't see it as referring specifically to plain text traffic

@pquentin pquentin merged commit 2e1073b into elastic:master Aug 30, 2022
@pquentin pquentin added this to the 2.7.0 milestone Nov 2, 2022
@pquentin pquentin deleted the encourage-browsing-repo branch February 16, 2023 06:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

cleanup Linter changes, reformatting, removal of unused code etc. :Docs Changes to the documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants