Closed karlbright closed 8 years ago
This adds some simple Heroku configuration and setup to allow us to deploy to http://fendersbot.herokuapp.com. Although this may change, this is a simple solution for something we need sooner rather than later.
http://fendersbot.herokuapp.com
Counting objects: 9, done. Delta compression using up to 4 threads. Compressing objects: 100% (8/8), done. Writing objects: 100% (9/9), 1.46 KiB | 0 bytes/s, done. Total 9 (delta 3), reused 0 (delta 0) remote: Compressing source files... done. remote: Building source: remote: remote: -----> Using set buildpack heroku/nodejs remote: -----> Node.js app detected remote: remote: -----> Creating runtime environment remote: remote: NPM_CONFIG_LOGLEVEL=error remote: NPM_CONFIG_PRODUCTION=true remote: NODE_ENV=production remote: NODE_MODULES_CACHE=true remote: remote: -----> Installing binaries remote: engines.node (package.json): unspecified remote: engines.npm (package.json): unspecified (use default) remote: remote: Resolving node version (latest stable) via semver.io... remote: Downloading and installing node 5.0.0... remote: Using default npm version: 3.3.6 remote: remote: -----> Restoring cache remote: Loading 2 from cacheDirectories (default): remote: - node_modules remote: - bower_components (not cached - skipping) remote: remote: -----> Building dependencies remote: Pruning any extraneous modules remote: Installing node modules (package.json) remote: remote: > ws@0.4.31 install /tmp/build_6743bca8e3c2a254bfb4c2a248673bb9/node_modules/ws remote: > (node-gyp rebuild 2> builderror.log) || (exit 0) remote: remote: make: Entering directory `/tmp/build_6743bca8e3c2a254bfb4c2a248673bb9/node_modules/ws/build' remote: CXX(target) Release/obj.target/bufferutil/src/bufferutil.o remote: make: Leaving directory `/tmp/build_6743bca8e3c2a254bfb4c2a248673bb9/node_modules/ws/build' remote: remote: -----> Caching build remote: Clearing previous node cache remote: Saving 2 cacheDirectories (default): remote: - node_modules remote: - bower_components (nothing to cache) remote: remote: -----> Build succeeded! remote: ├── express@4.13.3 remote: └── slack-client@1.4.1 remote: remote: remote: -----> Discovering process types remote: Procfile declares types -> web remote: remote: -----> Compressing... done, 11.8MB remote: -----> Launching... done, v5 remote: https://fendersbot.herokuapp.com/ deployed to Heroku remote: remote: Verifying deploy.... done. To https://git.heroku.com/fendersbot.git + 74decd7...50763f8 heroku -> master (forced update)
:+1:
This adds some simple Heroku configuration and setup to allow us to deploy to
http://fendersbot.herokuapp.com
. Although this may change, this is a simple solution for something we need sooner rather than later.