Skip to content

Instantly share code, notes, and snippets.

Embed
What would you like to do?
dance2die@dokku:~/node-js-getting-started$ git push dokku master
Enter passphrase for key '/home/dance2die/.ssh/id_rsa':
Counting objects: 3, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (2/2), done.
Writing objects: 100% (3/3), 291 bytes | 291.00 KiB/s, done.
Total 3 (delta 1), reused 0 (delta 0)
-----> Cleaning up...
-----> Building node-js-getting-started from herokuish...
-----> Adding BUILD_ENV to build environment...
-----> Node.js app detected
-----> Creating runtime environment
NPM_CONFIG_LOGLEVEL=error
NODE_ENV=production
NODE_MODULES_CACHE=true
NODE_VERBOSE=false
-----> Installing binaries
engines.node (package.json): 10.x
engines.npm (package.json): unspecified (use default)
Resolving node version 10.x...
Downloading and installing node 10.16.3...
Using default npm version: 6.9.0
-----> Restoring cache
- node_modules
-----> Installing dependencies
Installing node modules (package.json)
added 79 packages from 65 contributors and audited 248 packages in 3.84s
found 0 vulnerabilities
-----> Build
-----> Pruning devDependencies
removed 79 packages and audited 127 packages in 1.386s
found 0 vulnerabilities
-----> Caching build
- node_modules
-----> Build succeeded!
-----> Discovering process types
Procfile declares types -> web
-----> Releasing node-js-getting-started (dokku/node-js-getting-started:latest)...
-----> Deploying node-js-getting-started (dokku/node-js-getting-started:latest)...
-----> App Procfile file found (/home/dokku/node-js-getting-started/DOKKU_PROCFILE)
DOKKU_SCALE declares scale -> web=1
-----> Attempting pre-flight checks
For more efficient zero downtime deployments, create a file CHECKS.
See http://dokku.viewdocs.io/dokku/deployment/zero-downtime-deploys/ for examples
CHECKS file not found in container: Running simple container check...
-----> Waiting for 10 seconds ...
-----> Default container check successful!
-----> Running post-deploy
-----> VHOST support disabled. Skipping domains setup
-----> Creating http nginx.conf
-----> Running nginx-pre-reload
Reloading nginx
-----> Renaming containers
Found previous container(s) (5e9e0a95731a) named node-js-getting-started.web.1
Renaming container (5e9e0a95731a) node-js-getting-started.web.1 to node-js-getting-started.web.1.1569718919
Renaming container (bccaa0d7a197) goofy_rhodes to node-js-getting-started.web.1
-----> Shutting down old containers in 60 seconds
5e9e0a95731a1368971159ec9d0b837b0c65451081b373cc577210eefcdd7c31
=====> Application deployed:
http://dokku:45143
To 192.168.22.242:node-js-getting-started
97e6c72..1d859f3 master -> master
dance2die@dokku:~/node-js-getting-started$
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.