-
Notifications
You must be signed in to change notification settings - Fork 72
Analytics docs refresh #798
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
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Add callout in technical changelog for all versions that upgrade Postgres.
23ca848
to
45350e8
Compare
Update dead link in Postgres docs to external Postgres provider.
Remove incorrect customer advisement to not use docker compose and instead use an install script or machine images
Remove incorrect customer advisement to not use docker compose and instead use an install script or machine images
Remove another warning telling customers not to use docker compose in a part of the docs that customers would already be running or have chosen docker compose.
Remove reference to install script
Add better description for the best use case of machine images. Highlight strengths and weaknesses.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hey @dadlerj reviewed the PR. I made direct commits to your PR with the suggestions I had. Thanks a ton :)
Looks good. Let's prepare it for the 1/29 launch.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just one tiny fix. Otherwise approved. Thanks Maedah!
This PR will refresh our analytics docs for admins. This centralizes all customer-facing analytics content into a single, top-level product section, and describes the future structure of our analytics (cloud vs. self-hosted).
While these docs still have a lot of blanks, and don't perfectly reflect the current reality (e.g. "Cody Analytics" hasn't become "Sourcegraph Analytics" yet; the self-hosted analytics product isn't available in GA yet; etc.), it's a better setup than what we currently have and is a format we can build on in the coming months.
Please call out any gaps or issues you see here.
I use screenshots from the current cody analytics product and from the offsite grafana product
-Preview: https://sourcegraph-docs-git-analytics-docs-5e5d08-sourcegraph-f8c71130.vercel.app/docs/analytics