Here's how GITHUB.COM makes money* and how much!

*Please read our disclaimer before using our estimates.
Loading...

GITHUB . COM {}

Detected CMS Systems:

  1. Analyzed Page
  2. Matching Content Categories
  3. CMS
  4. Monthly Traffic Estimate
  5. How Does Github.com Make Money
  6. How Much Does Github.com Make
  7. Wordpress Themes And Plugins
  8. Keywords
  9. Topics
  10. Payment Methods
  11. Questions
  12. Schema
  13. External Links
  14. Analytics And Tracking
  15. Libraries
  16. Hosting Providers

We are analyzing https://github.com/readthedocs/readthedocs.org/issues/3530.

Title:
"Edit on Github" points to non-existing commit Β· Issue #3530 Β· readthedocs/readthedocs.org
Description:
Details Project URL: https://esrally.readthedocs.io Build URL (if applicable): https://readthedocs.org/projects/esrally/builds/6575685/ Read the Docs username (if applicable): danielmitterdorfer Expected Result Each page of the Rally doc...
Website Age:
17 years and 8 months (reg. 2007-10-09).

Matching Content Categories {πŸ“š}

  • Technology & Computing
  • Social Networks
  • DIY & Home Improvement

Content Management System {πŸ“}

What CMS is github.com built with?


Github.com is based on WORDPRESS.

Traffic Estimate {πŸ“ˆ}

What is the average monthly size of github.com audience?

πŸš€πŸŒ  Tremendous Traffic: 10M - 20M visitors per month


Based on our best estimate, this website will receive around 10,653,780 visitors per month in the current month.

check SE Ranking
check Ahrefs
check Similarweb
check Ubersuggest
check Semrush

How Does Github.com Make Money? {πŸ’Έ}


Subscription Packages {πŸ’³}

We've located a dedicated page on github.com that might include details about subscription plans or recurring payments. We identified it based on the word pricing in one of its internal links. Below, you'll find additional estimates for its monthly recurring revenues.

How Much Does Github.com Make? {πŸ’°}


Subscription Packages {πŸ’³}

Prices on github.com are in US Dollars ($). They range from $4.00/month to $21.00/month.
We estimate that the site has approximately 5,316,107 paying customers.
The estimated monthly recurring revenue (MRR) is $22,327,651.
The estimated annual recurring revenues (ARR) are $267,931,808.

Wordpress Themes and Plugins {🎨}

What WordPress theme does this site use?

It is strange but we were not able to detect any theme on the page.

What WordPress plugins does this website use?

It is strange but we were not able to detect any plugins on the page.

Keywords {πŸ”}

github, commit, docs, danielmitterdorfer, link, points, build, page, rally, sign, edit, issue, stable, bebaacdecebbcb, htmltheme, githubversion, readthedocs, projects, problem, context, false, true, content, navigation, open, readthedocsorg, pull, requests, actions, security, nonexisting, closed, project, url, applicable, result, clicking, shows, latest, master, repo, output, cat, docsconfpy, information, usingtheme, confpypath, githubuser, elastic, githubrepo,

Topics {βœ’οΈ}

/elastic/rally/blob/467b22ebaacde0366846696747c419e42bbc971b/docs/index org/projects/esrally/downloads/pdf/stable/ org/projects/esrally/downloads/htmlzip/stable/ org/projects/esrally/downloads/epub/stable/ org/projects/esrally/builds/6575685/ read cat docs/conf io build url activity danielmitterdorfer mentioned vcs integration docs danielmitterdorfer expected result current stable version danielmitterdorfer closed comment metadata assignees io/en/stable/' index page points rally docs /elastic/rally type projects projects milestone dead github link open content docs username u'esrally' github repo https build output issue /en/stable/ 'downloads' actual result personal information respective file' detailed analysis template context keys explicitly user configuration explicitly overridden context shown manually inject quick answer assigned labels labels type milestone relationships valid commit '/docs/' commit key correct commit /docs/ commit hash 'rally'

Payment Methods {πŸ“Š}

  • Braintree

Questions {❓}

  • Already have an account?

Schema {πŸ—ΊοΈ}

DiscussionForumPosting:
      context:https://schema.org
      headline:"Edit on Github" points to non-existing commit
      articleBody:## Details * Project URL: https://esrally.readthedocs.io * Build URL (if applicable): https://readthedocs.org/projects/esrally/builds/6575685/ * Read the Docs username (if applicable): danielmitterdorfer ## Expected Result Each page of the Rally docs contains an "Edit on Github" link. Clicking on that link will open a Github page that shows the respective file's content. ## Actual Result Each page of the Rally docs contains an "Edit on Github" link. Clicking on that link opens a Github 404 page (except for "latest" which correctly points to master). ## More detailed analysis An example that demonstrates the problem is e.g. [the current stable version](https://esrally.readthedocs.io/en/stable/). At the moment this link on the index page points to https://github.com/elastic/rally/blob/467b22ebaacde0366846696747c419e42bbc971b/docs/index.rst. However, the problem is that `467b22ebaacde0366846696747c419e42bbc971b` is not a valid commit in the Github repo https://github.com/elastic/rally. In the build output in the Readthedocs build id `6575685` we see a build step `cat docs/conf.py` which shows (shortened): ```python #Add project information to the template context. context = { 'using_theme': using_rtd_theme, 'html_theme': html_theme, 'current_version': "stable", 'version_slug': "stable", 'MEDIA_URL': "https://media.readthedocs.org/", 'PRODUCTION_DOMAIN': "readthedocs.org", 'versions': [ ("latest", "/en/latest/"), ("stable", "/en/stable/"), ("0.9.0", "/en/0.9.0/"), ("0.8.1", "/en/0.8.1/"), ("0.8.0", "/en/0.8.0/"), ], 'downloads': [ ("pdf", "//readthedocs.org/projects/esrally/downloads/pdf/stable/"), ("htmlzip", "//readthedocs.org/projects/esrally/downloads/htmlzip/stable/"), ("epub", "//readthedocs.org/projects/esrally/downloads/epub/stable/"), ], 'subprojects': [ ], 'slug': 'esrally', 'name': u'esrally', 'rtd_language': u'en', 'programming_language': u'py', 'canonical_url': 'http://esrally.readthedocs.io/en/stable/', 'analytics_code': 'None', 'single_version': False, 'conf_py_path': '/docs/', 'api_host': 'https://readthedocs.org', 'github_user': 'elastic', 'github_repo': 'rally', 'github_version': '467b22ebaacde0366846696747c419e42bbc971b', 'display_github': True, 'bitbucket_user': 'None', 'bitbucket_repo': 'None', 'bitbucket_version': '467b22ebaacde0366846696747c419e42bbc971b', 'display_bitbucket': False, 'gitlab_user': 'None', 'gitlab_repo': 'None', 'gitlab_version': '467b22ebaacde0366846696747c419e42bbc971b', 'display_gitlab': False, 'READTHEDOCS': True, 'using_theme': (html_theme == "default"), 'new_theme': (html_theme == "sphinx_rtd_theme"), 'source_suffix': SUFFIX, 'user_analytics_code': '', 'global_analytics_code': 'UA-17997319-1', 'commit': 'bd851fdc', } ``` The `commit` key at the end actually points the correct commit whereas the `github_version` doesn't (that commit does not exist in the repo). I also tried to define these keys explicitly as described in the [VCS integration docs](https://docs.readthedocs.io/en/latest/vcs.html): ```python html_context = { "display_github": True, "github_user": "elastic", "github_repo": "rally", "github_version": "master", "conf_py_path": "/docs/" } ``` However, I've seen in the build output of `cat docs/conf.py` that the user configuration is explicitly overridden with the contents of `context` shown above. Is there any possibility to either manually inject a commit hash or use the same commit hash in `github_version` and `commit`?
      author:
         url:https://github.com/danielmitterdorfer
         type:Person
         name:danielmitterdorfer
      datePublished:2018-01-18T09:37:34.000Z
      interactionStatistic:
         type:InteractionCounter
         interactionType:https://schema.org/CommentAction
         userInteractionCount:2
      url:https://github.com/3530/readthedocs.org/issues/3530
      context:https://schema.org
      headline:"Edit on Github" points to non-existing commit
      articleBody:## Details * Project URL: https://esrally.readthedocs.io * Build URL (if applicable): https://readthedocs.org/projects/esrally/builds/6575685/ * Read the Docs username (if applicable): danielmitterdorfer ## Expected Result Each page of the Rally docs contains an "Edit on Github" link. Clicking on that link will open a Github page that shows the respective file's content. ## Actual Result Each page of the Rally docs contains an "Edit on Github" link. Clicking on that link opens a Github 404 page (except for "latest" which correctly points to master). ## More detailed analysis An example that demonstrates the problem is e.g. [the current stable version](https://esrally.readthedocs.io/en/stable/). At the moment this link on the index page points to https://github.com/elastic/rally/blob/467b22ebaacde0366846696747c419e42bbc971b/docs/index.rst. However, the problem is that `467b22ebaacde0366846696747c419e42bbc971b` is not a valid commit in the Github repo https://github.com/elastic/rally. In the build output in the Readthedocs build id `6575685` we see a build step `cat docs/conf.py` which shows (shortened): ```python #Add project information to the template context. context = { 'using_theme': using_rtd_theme, 'html_theme': html_theme, 'current_version': "stable", 'version_slug': "stable", 'MEDIA_URL': "https://media.readthedocs.org/", 'PRODUCTION_DOMAIN': "readthedocs.org", 'versions': [ ("latest", "/en/latest/"), ("stable", "/en/stable/"), ("0.9.0", "/en/0.9.0/"), ("0.8.1", "/en/0.8.1/"), ("0.8.0", "/en/0.8.0/"), ], 'downloads': [ ("pdf", "//readthedocs.org/projects/esrally/downloads/pdf/stable/"), ("htmlzip", "//readthedocs.org/projects/esrally/downloads/htmlzip/stable/"), ("epub", "//readthedocs.org/projects/esrally/downloads/epub/stable/"), ], 'subprojects': [ ], 'slug': 'esrally', 'name': u'esrally', 'rtd_language': u'en', 'programming_language': u'py', 'canonical_url': 'http://esrally.readthedocs.io/en/stable/', 'analytics_code': 'None', 'single_version': False, 'conf_py_path': '/docs/', 'api_host': 'https://readthedocs.org', 'github_user': 'elastic', 'github_repo': 'rally', 'github_version': '467b22ebaacde0366846696747c419e42bbc971b', 'display_github': True, 'bitbucket_user': 'None', 'bitbucket_repo': 'None', 'bitbucket_version': '467b22ebaacde0366846696747c419e42bbc971b', 'display_bitbucket': False, 'gitlab_user': 'None', 'gitlab_repo': 'None', 'gitlab_version': '467b22ebaacde0366846696747c419e42bbc971b', 'display_gitlab': False, 'READTHEDOCS': True, 'using_theme': (html_theme == "default"), 'new_theme': (html_theme == "sphinx_rtd_theme"), 'source_suffix': SUFFIX, 'user_analytics_code': '', 'global_analytics_code': 'UA-17997319-1', 'commit': 'bd851fdc', } ``` The `commit` key at the end actually points the correct commit whereas the `github_version` doesn't (that commit does not exist in the repo). I also tried to define these keys explicitly as described in the [VCS integration docs](https://docs.readthedocs.io/en/latest/vcs.html): ```python html_context = { "display_github": True, "github_user": "elastic", "github_repo": "rally", "github_version": "master", "conf_py_path": "/docs/" } ``` However, I've seen in the build output of `cat docs/conf.py` that the user configuration is explicitly overridden with the contents of `context` shown above. Is there any possibility to either manually inject a commit hash or use the same commit hash in `github_version` and `commit`?
      author:
         url:https://github.com/danielmitterdorfer
         type:Person
         name:danielmitterdorfer
      datePublished:2018-01-18T09:37:34.000Z
      interactionStatistic:
         type:InteractionCounter
         interactionType:https://schema.org/CommentAction
         userInteractionCount:2
      url:https://github.com/3530/readthedocs.org/issues/3530
Person:
      url:https://github.com/danielmitterdorfer
      name:danielmitterdorfer
      url:https://github.com/danielmitterdorfer
      name:danielmitterdorfer
InteractionCounter:
      interactionType:https://schema.org/CommentAction
      userInteractionCount:2
      interactionType:https://schema.org/CommentAction
      userInteractionCount:2

Analytics and Tracking {πŸ“Š}

  • Site Verification - Google

Libraries {πŸ“š}

  • Clipboard.js
  • D3.js
  • Lodash

Emails and Hosting {βœ‰οΈ}

Mail Servers:

  • aspmx.l.google.com
  • alt1.aspmx.l.google.com
  • alt2.aspmx.l.google.com
  • alt3.aspmx.l.google.com
  • alt4.aspmx.l.google.com

Name Servers:

  • dns1.p08.nsone.net
  • dns2.p08.nsone.net
  • dns3.p08.nsone.net
  • dns4.p08.nsone.net
  • ns-1283.awsdns-32.org
  • ns-1707.awsdns-21.co.uk
  • ns-421.awsdns-52.com
  • ns-520.awsdns-01.net
8.8s.