-
-
Notifications
You must be signed in to change notification settings - Fork 26.9k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Add external links to deployment services (#3265)
- Loading branch information
Showing
1 changed file
with
11 additions
and
11 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -1816,11 +1816,11 @@ If you are not using the HTML5 `pushState` history API or not using client-side | |
| This will make sure that all the asset paths are relative to `index.html`. You will then be able to move your app from `http://mywebsite.com` to `http://mywebsite.com/relativepath` or even `http://mywebsite.com/relative/path` without having to rebuild it. | ||
|
|
||
| ### Azure | ||
| ### [Azure](https://azure.microsoft.com/) | ||
|
|
||
| See [this](https://medium.com/@to_pe/deploying-create-react-app-on-microsoft-azure-c0f6686a4321) blog post on how to deploy your React app to [Microsoft Azure](https://azure.microsoft.com/). | ||
| See [this](https://medium.com/@to_pe/deploying-create-react-app-on-microsoft-azure-c0f6686a4321) blog post on how to deploy your React app to Microsoft Azure. | ||
|
|
||
| ### Firebase | ||
| ### [Firebase](https://firebase.google.com/) | ||
|
|
||
| Install the Firebase CLI if you haven’t already by running `npm install -g firebase-tools`. Sign up for a [Firebase account](https://console.firebase.google.com/) and create a new project. Run `firebase login` and login with your previous created Firebase account. | ||
|
|
||
|
|
@@ -1881,7 +1881,7 @@ Now, after you create a production build with `npm run build`, you can deploy it | |
|
|
||
| For more information see [Add Firebase to your JavaScript Project](https://firebase.google.com/docs/web/setup). | ||
|
|
||
| ### GitHub Pages | ||
| ### [GitHub Pages](https://pages.github.com/) | ||
|
|
||
| >Note: this feature is available with `[email protected]` and higher. | ||
|
|
||
|
|
@@ -1951,7 +1951,7 @@ GitHub Pages doesn’t support routers that use the HTML5 `pushState` history AP | |
| * You could switch from using HTML5 history API to routing with hashes. If you use React Router, you can switch to `hashHistory` for this effect, but the URL will be longer and more verbose (for example, `http://user.github.io/todomvc/#/todos/42?_k=yknaj`). [Read more](https://reacttraining.com/react-router/web/api/Router) about different history implementations in React Router. | ||
| * Alternatively, you can use a trick to teach GitHub Pages to handle 404 by redirecting to your `index.html` page with a special redirect parameter. You would need to add a `404.html` file with the redirection code to the `build` folder before deploying your project, and you’ll need to add code handling the redirect parameter to `index.html`. You can find a detailed explanation of this technique [in this guide](https://github.com/rafrex/spa-github-pages). | ||
|
|
||
| ### Heroku | ||
| ### [Heroku](https://www.heroku.com/) | ||
|
|
||
| Use the [Heroku Buildpack for Create React App](https://github.com/mars/create-react-app-buildpack).<br> | ||
| You can find instructions in [Deploying React with Zero Configuration](https://blog.heroku.com/deploying-react-with-zero-configuration). | ||
|
|
@@ -1989,7 +1989,7 @@ remote: npm ERR! argv "/tmp/build_a2875fc163b209225122d68916f1d4df/.heroku/node/ | |
|
|
||
| In this case, ensure that the file is there with the proper lettercase and that’s not ignored on your local `.gitignore` or `~/.gitignore_global`. | ||
|
|
||
| ### Netlify | ||
| ### [Netlify](https://www.netlify.com/) | ||
|
|
||
| **To do a manual deploy to Netlify’s CDN:** | ||
|
|
||
|
|
@@ -2018,9 +2018,9 @@ To support `pushState`, make sure to create a `public/_redirects` file with the | |
|
|
||
| When you build the project, Create React App will place the `public` folder contents into the build output. | ||
|
|
||
| ### Now | ||
| ### [Now](https://zeit.co/now) | ||
|
|
||
| [now](https://zeit.co/now) offers a zero-configuration single-command deployment. You can use `now` to deploy your app for free. | ||
| Now offers a zero-configuration single-command deployment. You can use `now` to deploy your app for free. | ||
|
|
||
| 1. Install the `now` command-line tool either via the recommended [desktop tool](https://zeit.co/download) or via node with `npm install -g now`. | ||
|
|
||
|
|
@@ -2038,11 +2038,11 @@ When you build the project, Create React App will place the `public` folder cont | |
|
|
||
| Details are available in [this article.](https://zeit.co/blog/unlimited-static) | ||
|
|
||
| ### S3 and CloudFront | ||
| ### [S3](https://aws.amazon.com/s3) and [CloudFront](https://aws.amazon.com/cloudfront/) | ||
|
|
||
| See this [blog post](https://medium.com/@omgwtfmarc/deploying-create-react-app-to-s3-or-cloudfront-48dae4ce0af) on how to deploy your React app to Amazon Web Services [S3](https://aws.amazon.com/s3) and [CloudFront](https://aws.amazon.com/cloudfront/). | ||
| See this [blog post](https://medium.com/@omgwtfmarc/deploying-create-react-app-to-s3-or-cloudfront-48dae4ce0af) on how to deploy your React app to Amazon Web Services S3 and CloudFront. | ||
|
|
||
| ### Surge | ||
| ### [Surge](https://surge.sh/) | ||
|
|
||
| Install the Surge CLI if you haven’t already by running `npm install -g surge`. Run the `surge` command and log in you or create a new account. | ||
|
|
||
|
|
||