1 00:00:00,260 --> 00:00:05,010 And once we've got our project working locally, we would probably want to share it with the rest of 2 00:00:05,010 --> 00:00:05,430 the world. 3 00:00:05,670 --> 00:00:05,920 Right. 4 00:00:06,250 --> 00:00:11,730 And even though there are many hosting options out there for this project, we will use awesome service 5 00:00:12,120 --> 00:00:13,310 called fire. 6 00:00:13,770 --> 00:00:14,130 Why? 7 00:00:14,650 --> 00:00:19,020 Well, because I just enjoy using metaphor for all my projects. 8 00:00:19,560 --> 00:00:20,940 If you don't have the account already. 9 00:00:21,270 --> 00:00:25,470 Make sure you sign up since you can create a free account in a few minutes. 10 00:00:25,800 --> 00:00:29,490 And don't worry, they are not after your credit card information. 11 00:00:29,820 --> 00:00:31,470 So essentially you can just sign up for free. 12 00:00:32,010 --> 00:00:38,700 Before we push our project to production, though, I would want to share a few gotchas when it comes 13 00:00:38,700 --> 00:00:43,990 to notify Underreact Browder as well as notify and create react. 14 00:00:44,910 --> 00:00:48,310 Rest assured, both things are already taken care of. 15 00:00:48,690 --> 00:00:50,310 If you're using Star project. 16 00:00:50,790 --> 00:00:55,470 But I just thought that it's a very useful info to know for your future projects. 17 00:00:56,070 --> 00:00:58,980 Let's start by navigating back to read me. 18 00:01:00,180 --> 00:01:04,610 In the bottom of the document, look for additional info on the side. 19 00:01:05,280 --> 00:01:08,550 If you want to have a gate to notify, of course you can use this link. 20 00:01:09,030 --> 00:01:12,600 But when we're looking for is this additional info. 21 00:01:13,170 --> 00:01:16,200 Like I said, both things are already taken care of. 22 00:01:16,230 --> 00:01:18,780 But I just want to share this information with you. 23 00:01:19,320 --> 00:01:23,190 So essentially, what happens if you use react rather enaam? 24 00:01:23,930 --> 00:01:32,970 If you deploy your project on Model VI, you might run into issues where once you navigate to a single 25 00:01:32,970 --> 00:01:39,060 page, let's say, I dunno, some kind of page that's in your project, you might get page not found. 26 00:01:39,540 --> 00:01:44,730 Now, in order to fix that, you would need to create a redirects file. 27 00:01:45,060 --> 00:01:51,570 So on the score, redirects file in the public folder, which again we already have, and then have 28 00:01:51,570 --> 00:01:52,140 this content. 29 00:01:52,560 --> 00:01:53,790 The index is schlemiel. 30 00:01:54,270 --> 00:01:59,190 If you are interested in learning about this bug and gotcha. 31 00:01:59,660 --> 00:02:00,990 And how we would fix it. 32 00:02:01,350 --> 00:02:03,060 Of course I share a resource here. 33 00:02:03,720 --> 00:02:05,310 Awesome blog post that covers that. 34 00:02:05,700 --> 00:02:07,890 But I'm not going to go into more details. 35 00:02:08,280 --> 00:02:14,370 Just remember that if you're using reactor hour down a metal ify, you should the underscore redirect 36 00:02:14,390 --> 00:02:17,400 while in public and then have the content here. 37 00:02:17,790 --> 00:02:20,760 So that way you'll avoid all the annoying bugs. 38 00:02:21,240 --> 00:02:26,590 Now, the second thing are the warnings we create, react up and notify. 39 00:02:27,220 --> 00:02:33,210 So you see, while we're developing locally, everything is fine because every time we set up a dev 40 00:02:33,210 --> 00:02:36,050 server, even if we have warnings, we're good to go. 41 00:02:36,680 --> 00:02:43,830 However, once we deploy our application on MusclePharm, as the build process takes place, if we have 42 00:02:43,830 --> 00:02:47,130 warnings recently, it has stopped the whole build process. 43 00:02:47,610 --> 00:02:50,760 So in order to avoid that in the package. 44 00:02:50,820 --> 00:02:56,940 Jason, where we have build command instead of just having react, grifts build. 45 00:02:57,440 --> 00:02:58,290 We go with this. 46 00:02:58,610 --> 00:03:02,310 See, I am on the equal sign again. 47 00:03:02,520 --> 00:03:07,290 You want to find out more about this bug and how it would fix it? 48 00:03:07,650 --> 00:03:12,030 Of course, I have a link here for the blog post and all that. 49 00:03:12,480 --> 00:03:17,850 But if you're using Star Project, Minorities' set up the command in a back. 50 00:03:17,850 --> 00:03:19,260 And Jason, for you. 51 00:03:19,740 --> 00:03:24,270 So those are two gotchas that I wanted to share before we deploy our project. 52 00:03:24,790 --> 00:03:26,550 And now we can start doing that.