And once we've got our project working locally, we would probably want to share it with the rest of
the world.
Right.
And even though there are many hosting options out there for this project, we will use awesome service
called fire.
Why?
Well, because I just enjoy using metaphor for all my projects.
If you don't have the account already.
Make sure you sign up since you can create a free account in a few minutes.
And don't worry, they are not after your credit card information.
So essentially you can just sign up for free.
Before we push our project to production, though, I would want to share a few gotchas when it comes
to notify Underreact Browder as well as notify and create react.
Rest assured, both things are already taken care of.
If you're using Star project.
But I just thought that it's a very useful info to know for your future projects.
Let's start by navigating back to read me.
In the bottom of the document, look for additional info on the side.
If you want to have a gate to notify, of course you can use this link.
But when we're looking for is this additional info.
Like I said, both things are already taken care of.
But I just want to share this information with you.
So essentially, what happens if you use react rather enaam?
If you deploy your project on Model VI, you might run into issues where once you navigate to a single
page, let's say, I dunno, some kind of page that's in your project, you might get page not found.
Now, in order to fix that, you would need to create a redirects file.
So on the score, redirects file in the public folder, which again we already have, and then have
this content.
The index is schlemiel.
If you are interested in learning about this bug and gotcha.
And how we would fix it.
Of course I share a resource here.
Awesome blog post that covers that.
But I'm not going to go into more details.
Just remember that if you're using reactor hour down a metal ify, you should the underscore redirect
while in public and then have the content here.
So that way you'll avoid all the annoying bugs.
Now, the second thing are the warnings we create, react up and notify.
So you see, while we're developing locally, everything is fine because every time we set up a dev
server, even if we have warnings, we're good to go.
However, once we deploy our application on MusclePharm, as the build process takes place, if we have
warnings recently, it has stopped the whole build process.
So in order to avoid that in the package.
Jason, where we have build command instead of just having react, grifts build.
We go with this.
See, I am on the equal sign again.
You want to find out more about this bug and how it would fix it?
Of course, I have a link here for the blog post and all that.
But if you're using Star Project, Minorities' set up the command in a back.
And Jason, for you.
So those are two gotchas that I wanted to share before we deploy our project.
And now we can start doing that.