-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy path44_production_deploy(alpha_blog).txt
More file actions
46 lines (28 loc) · 1.44 KB
/
44_production_deploy(alpha_blog).txt
File metadata and controls
46 lines (28 loc) · 1.44 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
Production deploy - text follow-up
-----------------------------------------------------------------------------------------
We used the following steps to deploy our application to production (using Heroku). If you
have not set up a Heroku account and deployed the application at the end of section 3
(including all the setup steps like installing Heroku CLI and creating a heroku app),
you are encouraged to do so now before moving forward. If you would rather not deploy
to production, then you can safely skip this step.
Steps we followed:
- verify Gemfile
- issue the following command in the terminal bundle install --without production
- make a commit of code
-- git add -A
-- git commit -m "helpful message depending on what you are committing to your repo"
-----------------------------------------------------------------------------
To deploy to heroku:
git push heroku master
To push to GitHub repo:
git push origin master
Since we now have a db component to our application with the articles table, we will need to
run migrations in production so the production articles table is created. To run migrations
at heroku, you can use the following command:
heroku run rails db:migrate
You can preview your production app by issuing the following command from the terminal:
heroku open
or,
You can directly pull up a browser window and paste in the name of your application. It'll
take the following format:
https://yourappname.herokuapp.com