Deploy your admin backend on Heroku
This tutorial is designed to assist people who want to have a step-by-step guide to deploy the Lumber-generated admin backend to Heroku.
If you don’t have a Heroku account yet, sign up here. Then, create your first Heroku application (1) (2).
After creating your application, simply follow the Heroku guide “Deploy using Heroku Git” to push the lumber-generated admin backend code to the Heroku application.
Push your code using the following command:
Command line
Output
1
git push heroku master
Copied!
1
Counting objects: 25, done.
2
Delta compression using up to 4 threads.
3
Compressing objects: 100% (20/20), done.
4
Writing objects: 100% (25/25), 21.56 KiB | 5.39 MiB/s, done.
5
Total 25 (delta 9), reused 0 (delta 0)
6
remote: Compressing source files... done.
7
remote: Building source:
8
remote:
9
remote: -----> Node.js app detected
10
remote:
11
remote: -----> Creating runtime environment
12
remote:
13
remote: NPM_CONFIG_LOGLEVEL=error
14
remote: NODE_VERBOSE=false
15
remote: NODE_ENV=production
16
remote: NODE_MODULES_CACHE=true
17
remote:
18
remote: -----> Installing binaries
19
remote: engines.node (package.json): unspecified
20
remote: engines.npm (package.json): unspecified (use default)
21
remote:
22
remote: Resolving node version 8.x...
23
remote: Downloading and installing node 8.11.4...
24
remote: Using default npm version: 5.6.0
25
remote:
26
remote: -----> Restoring cache
27
remote: Skipping cache restore (not-found)
28
remote:
29
remote: -----> Building dependencies
30
remote: Installing node modules (package.json + package-lock)
31
remote: added 246 packages in 7.72s
32
remote:
33
remote: -----> Caching build
34
remote: Clearing previous node cache
35
remote: Saving 2 cacheDirectories (default):
36
remote: - node_modules
37
remote: - bower_components (nothing to cache)
38
remote:
39
remote: -----> Pruning devDependencies
40
remote: Skipping because npm 5.6.0 sometimes fails when running 'npm prune' due to a known issue
41
remote: https://github.com/npm/npm/issues/19356
42
remote:
43
remote: You can silence this warning by updating to at least npm 5.7.1 in your package.json
44
remote: https://devcenter.heroku.com/articles/nodejs-support#specifying-an-npm-version
45
remote:
46
remote: -----> Build succeeded!
47
remote: -----> Discovering process types
48
remote: Procfile declares types -> (none)
49
remote: Default types for buildpack -> web
50
remote:
51
remote: -----> Compressing...
52
remote: Done: 24.2M
53
remote: -----> Launching...
54
remote: Released v3
55
remote: https://lumber-deploy-to-production.herokuapp.com/ deployed to Heroku
56
remote:
57
remote: Verifying deploy... done.
58
To https://git.heroku.com/lumber-deploy-to-production.git
59
* [new branch] master -> master
Copied!
Your admin backend is now deployed in a remote Heroku application. 🎉
The last step to have a complete running application is to deploy a database remotely.
For this, you can follow our Populate a remote database how-to.
This does not mean your project is deployed to production on Forest Admin. To deploy to production, check out this section after you've completed the above steps.
Last modified 2yr ago
Copy link