Update the web site URL

pgonzal · pgonzal · commit 9f989838ca41 · 2018-05-31T16:06:43.000-07:00
diff --git a/apps/rush-lib/package.json b/apps/rush-lib/package.json
@@ -10,7 +10,7 @@
     "node": ">=5.6.0"
   },
   "engineStrict": true,
-  "homepage": "http://aka.ms/rush",
+  "homepage": "https://rushjs.io",
   "main": "lib/index.js",
   "typings": "dist/rush-lib.d.ts",
   "tsdoc": {
diff --git a/apps/rush-lib/src/RushConstants.ts b/apps/rush-lib/src/RushConstants.ts
@@ -116,7 +116,7 @@ export namespace RushConstants {
   /**
    * The URL ("http://rushjs.io") for the Rush web site.
    */
-  export const rushWebSiteUrl: string = 'http://rushjs.io';
+  export const rushWebSiteUrl: string = 'https://rushjs.io';
 
   /**
    * The name of the NPM package for the Rush tool ("@microsoft/rush").
diff --git a/apps/rush/README.md b/apps/rush/README.md
@@ -3,7 +3,7 @@
 
 ![rush](https://github.com/Microsoft/web-build-tools/blob/master/common/wiki-images/rush-logo.png?raw=true)
 <br />
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; https://aka.ms/rush
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; https://rushjs.io
 
 <!-- -------------------------------------------------------------------------- -->
 <!-- Text below this line should stay in sync with Rush.md from the GitHub wiki -->
@@ -19,7 +19,7 @@
 
 - **Subset and incremental builds:** If you only plan to work with a few projects from your repo, `rush rebuild --to <project>` does a clean build of just your upstream dependencies.  After you make changes, `rush rebuild --from <project>` does a clean build of only the affected downstream projects.  And if your toolchain is [package-deps-hash](https://www.npmjs.com/package/@microsoft/package-deps-hash) enabled, `rush build` delivers a powerful cross-project incremental build (that also supports subset builds).
 
-- **Cyclic dependencies:** If you have hammers that build hammer-factory-factories, Rush has you covered!  When a package indirectly depends on an older version of itself, projects in the cycle use the last published version, whereas other projects still get the latest bits. 
+- **Cyclic dependencies:** If you have hammers that build hammer-factory-factories, Rush has you covered!  When a package indirectly depends on an older version of itself, projects in the cycle use the last published version, whereas other projects still get the latest bits.
 
 - **Bulk publishing:** When it's time to do a release, Rush can detect which packages have changes, automatically bump all the appropriate version numbers, and run `npm publish` in each folder.  If you like, configure your server to automatically run `rush publish` every hour.
 
@@ -59,4 +59,4 @@ _(If you don't have a GitHub account set up, you can use `rush install --bypass-
 
 # Getting Started
 
-The GitHub wiki has complete, up-to-date documentation: https://aka.ms/rush
+The GitHub wiki has complete, up-to-date documentation: https://rushjs.io
diff --git a/apps/rush/package.json b/apps/rush/package.json
@@ -21,7 +21,7 @@
     "node": ">=5.6.0"
   },
   "engineStrict": true,
-  "homepage": "http://aka.ms/rush",
+  "homepage": "https://rushjs.io",
   "scripts": {
     "build": "gulp test --clean"
   },
