This post is part of the series 30 Days of React.

In this series, we're starting from the very basics and walk through everything you need to know to get started with React. If you've ever wanted to learn React, this is the place to start!


Edit this page on Github

Today, we'll look through some ready-to-go options so we can get our site up and running. By the end of today, you'll be able to share a link to your running application.

We left off yesterday preparing for our first deployment of our application. We're ready to deploy our application. Now the question is where and what are we going to deploy?

Let's explore...


While deploying a single page application has it's own intricasies, it's similar to deploying a non-single page application. What the end-user's browser requests all need to be available for the browser to request. This means all javascript files, any custom fonts, images, svg, stylesheets, etc. that we use in our application need to be available on a publicly available server.

Webpack takes care of building and packaging our entire application for what we'll need to give the server to send to our clients. This includes any client-side tokens and our production confi...

Learn React the right way

The up-to-date, in-depth, complete guide to React and friends.

Download the first chapter

This page is a preview of 30 Days of React

Get the rest of this chapter and 300+ pages of React instruction for free.

Download 30 Days of React PDF (free)

Ari Lerner

Hi, I'm Ari. I'm an author of Fullstack React and ng-book and I've been teaching Web Development for a long time. I like to speak at conferences and eat spicy food. I technically got paid while I traveled the country as a professional comedian, but have come to terms with the fact that I am not funny.

Connect with Ari on Twitter at @auser.