1
00:00:00,270 --> 00:00:03,500
With both of our applications complete and it's time to deploy.

2
00:00:03,960 --> 00:00:09,840
And we're going to start by deploying our backend our strapping up to Heroku and once that is complete

3
00:00:09,870 --> 00:00:13,420
we're going to change the URL string in our front end up.

4
00:00:13,530 --> 00:00:16,250
Remember it is still pointing to a local host.

5
00:00:16,350 --> 00:00:20,200
And then we're going to deploy it to notify as far as Heroku.

6
00:00:20,220 --> 00:00:26,420
I picked it because a few reasons it is free and the install is mostly straightforward.

7
00:00:26,430 --> 00:00:33,780
The downside of her uncle that if the app is not used it goes to sleep meaning it sometimes takes one

8
00:00:33,780 --> 00:00:38,890
to two minutes for your response to arrive and also Heroku wipes out the cache.

9
00:00:38,910 --> 00:00:44,040
That's the reason why when we deployed the rock when we for sure need to have our cloud marry.

10
00:00:44,130 --> 00:00:49,710
Otherwise if you're just going to use the local uploads while you can do that at the moment the app

11
00:00:49,710 --> 00:00:51,150
is gonna go to sleep.

12
00:00:51,150 --> 00:00:52,780
Everything is gonna be wiped up.

13
00:00:52,800 --> 00:00:58,650
I mean not the end of the world the problems that Heroku has but probably not the best user experience

14
00:00:59,190 --> 00:01:01,190
since Travis is a node app.

15
00:01:01,290 --> 00:01:03,350
You're not limited to just Heroku.

16
00:01:03,750 --> 00:01:09,750
So for example a better option probably would be something like Digital Ocean but since the setup is

17
00:01:09,750 --> 00:01:13,320
somewhat tedious we need to setup SSA keys.

18
00:01:13,350 --> 00:01:21,470
We need to configure injects and etc. We are just going to stick with Heroku for our backend front end.

19
00:01:21,480 --> 00:01:26,450
I mean there's really not much to say which is deployed to notify and we're good to go.