search

cobyism / ghost-on-heroku

One-button Heroku deploy for the Ghost blogging platform.
MIT License
743 stars 686 forks source link

Can't see my blog after successful deploy #34

Closed Elinos closed 9 years ago

Elinos commented 9 years ago

I've deployed my app and everything seems to complete as expected. Here is the deploy log: 

-----> Node.js app detected
-----> Creating runtime environment

       NPM_CONFIG_LOGLEVEL=error
       NPM_CONFIG_PRODUCTION=true
       NODE_ENV=production
       NODE_MODULES_CACHE=true
-----> Installing binaries
       engines.node (package.json):  ~0.10.0
       engines.npm (package.json):   unspecified (use default)

       Resolving node version ~0.10.0 via semver.io...
       Downloading and installing node 0.10.40...
       Using default npm version: 1.4.28
-----> Restoring cache
       Skipping cache (new runtime signature)
-----> Building dependencies
       Pruning any extraneous modules
       Installing node modules (package.json)

       > sqlite3@3.0.8 install /tmp/build_32e2eeb804660c7b40897991e2ac4202/cobyism-ghost-on-heroku-a11a874/node_modules/ghost/node_modules/sqlite3
       > node-pre-gyp install --fallback-to-build

       [sqlite3] Success: "/tmp/build_32e2eeb804660c7b40897991e2ac4202/cobyism-ghost-on-heroku-a11a874/node_modules/ghost/node_modules/sqlite3/lib/binding/node-v11-linux-x64/node_sqlite3.node" is installed via remote
       pg@4.4.1 node_modules/pg
       ├── packet-reader@0.2.0
       ├── pg-connection-string@0.1.3
       ├── buffer-writer@1.0.0
       ├── generic-pool@2.1.1
       ├── semver@4.3.6
       ├── pg-types@1.10.0 (postgres-bytea@1.0.0, postgres-date@1.0.0, postgres-array@1.0.0, ap@0.2.0, postgres-interval@1.0.0)
       └── pgpass@0.0.3 (split@0.3.3)

       ghost-s3-storage@0.2.1 node_modules/ghost-s3-storage
       ├── when@3.7.3
       └── aws-sdk@2.2.0 (xmlbuilder@0.4.2, xml2js@0.2.8, sax@0.5.3)

       ghost@0.6.4 node_modules/ghost
       ├── connect-slashes@1.3.0
       ├── xml@1.0.0
       ├── node-uuid@1.4.2
       ├── passport-oauth2-client-password@0.1.2 (passport-strategy@1.0.0)
       ├── validator@3.39.0
       ├── passport-http-bearer@1.0.1 (passport-strategy@1.0.0)
       ├── semver@4.3.3
       ├── passport@0.2.1 (pause@0.0.1, passport-strategy@1.0.0)
       ├── bcryptjs@2.1.0
       ├── chalk@1.0.0 (escape-string-regexp@1.0.3, ansi-styles@2.0.1, supports-color@1.3.1, strip-ansi@2.0.1, has-ansi@1.0.3)
       ├── path-match@1.2.2 (path-to-regexp@1.2.0, http-errors@1.2.8)
       ├── oauth2orize@1.0.1 (uid2@0.0.3, utils-merge@1.0.0, debug@0.7.4)
       ├── cookie-session@1.1.0 (on-headers@1.0.0, cookies@0.5.0, debug@2.1.3)
       ├── morgan@1.5.0 (basic-auth@1.0.0, depd@1.0.1, on-finished@2.1.1, debug@2.1.3)
       ├── downsize@0.0.8 (xregexp@2.0.0)
       ├── rss@1.1.1 (mime-types@2.0.12)
       ├── bluebird@2.9.25
       ├── glob@4.3.2 (inherits@2.0.1, once@1.3.2, inflight@1.0.4, minimatch@2.0.8)
       ├── html-to-text@1.3.0 (underscore.string@2.4.0, underscore@1.8.3, htmlparser@1.7.7, optimist@0.6.1)
       ├── showdown-ghost@0.3.6
       ├── extract-zip@1.0.3 (debug@0.7.4, minimist@0.1.0, async@0.9.0, yauzl@2.3.1, mkdirp@0.5.0, through2@0.6.3, concat-stream@1.4.8)
       ├── lodash@2.4.1
       ├── unidecode@0.1.3
       ├── fs-extra@0.13.0 (jsonfile@2.0.0, ncp@1.0.1, rimraf@2.3.4)
       ├── express@4.12.3 (merge-descriptors@1.0.0, utils-merge@1.0.0, cookie-signature@1.0.6, methods@1.1.1, fresh@0.2.4, cookie@0.1.2, escape-html@1.0.1, range-parser@1.0.2, vary@1.0.0, finalhandler@0.3.4, content-type@1.0.1, parseurl@1.3.0, content-disposition@0.5.0, path-to-regexp@0.1.3, depd@1.0.1, qs@2.4.1, on-finished@2.2.1, debug@2.1.3, send@0.12.2, proxy-addr@1.0.8, etag@1.5.1, type-is@1.6.2, serve-static@1.9.3, accepts@1.2.7)
       ├── pg@4.1.1 (packet-reader@0.2.0, pg-connection-string@0.1.3, buffer-writer@1.0.0, generic-pool@2.1.1, pg-types@1.6.0, pgpass@0.0.3)
       ├── compression@1.2.2 (vary@1.0.0, bytes@1.0.0, on-headers@1.0.0, debug@2.1.3, compressible@2.0.2, accepts@1.1.4)
       ├── body-parser@1.10.0 (bytes@1.0.0, media-typer@0.3.0, raw-body@1.3.1, depd@1.0.1, qs@2.3.3, on-finished@2.1.1, iconv-lite@0.4.5, type-is@1.5.7)
       ├── busboy@0.2.9 (readable-stream@1.1.13, dicer@0.2.3)
       ├── mocha@2.2.5 (escape-string-regexp@1.0.2, supports-color@1.2.1, growl@1.8.1, commander@2.3.0, diff@1.4.0, debug@2.0.0, mkdirp@0.5.0, glob@3.2.3, jade@0.26.3)
       ├── request@2.55.0 (caseless@0.9.0, aws-sign2@0.5.0, forever-agent@0.6.1, stringstream@0.0.4, oauth-sign@0.6.0, tunnel-agent@0.4.0, isstream@0.1.2, json-stringify-safe@5.0.1, qs@2.4.2, combined-stream@0.0.7, form-data@0.2.0, bl@0.9.4, http-signature@0.10.1, tough-cookie@1.1.0, mime-types@2.0.12, hawk@2.3.1, har-validator@1.7.0)
       ├── cheerio@0.18.0 (dom-serializer@0.0.1, entities@1.1.1, htmlparser2@3.8.2, CSSselect@0.4.1)
       ├── bookshelf@0.7.9 (trigger-then@0.3.0, simple-extend@0.1.0, create-error@0.3.1, inherits@2.0.1, inflection@1.7.1, backbone@1.1.0)
       ├── knex@0.7.3 (inherits@2.0.1, interpret@0.3.10, generic-pool-redux@0.1.0, minimist@1.1.1, tildify@1.0.0, commander@2.8.1, chalk@0.5.1, readable-stream@1.1.13, mkdirp@0.5.1, liftoff@0.13.6)
       ├── moment@2.10.2
       ├── express-hbs@0.8.4 (readdirp@1.3.0, js-beautify@1.5.4, handlebars@3.0.3)
       ├── istanbul@0.3.14 (supports-color@1.3.1, abbrev@1.0.6, which@1.0.9, nopt@3.0.2, wordwrap@0.0.3, once@1.3.2, async@0.9.2, esprima@2.1.0, mkdirp@0.5.1, resolve@1.1.6, fileset@0.1.5, escodegen@1.6.1, handlebars@3.0.0, js-yaml@3.3.1)
       ├── nodemailer@0.7.1 (public-address@0.1.1, directmail@0.1.8, he@0.3.6, readable-stream@1.1.13, simplesmtp@0.3.35, mailcomposer@0.2.12, aws-sdk@2.0.5)
       ├── mysql@2.1.1 (require-all@0.0.3, readable-stream@1.1.13, bignumber.js@1.0.1)
       └── sqlite3@3.0.8 (nan@1.8.4)
-----> Caching build
       Clearing previous node cache
       Saving 1 cacheDirectories (default):
       - node_modules
-----> Build succeeded!
       ├── ghost@0.6.4
       ├── ghost-s3-storage@0.2.1
       └── pg@4.4.1

-----> Discovering process types
       Procfile declares types -> web
-----> Compressing... done, 22.6MB
-----> Launching... done, v6
       https://tsarnakliyski-ghost.herokuapp.com/ deployed to Heroku

But when i go to my app webpage it just states "Heroku | Welcome to your new app!" and i can't access my blog admin panel?

cobyism commented 9 years ago

Thanks for opening an issue. That’s odd to say the least. Did you use the deploy button? or did you create the app via the command line and git push manually?

I just used the button then to do a successful deploy, so at this stage I’m thinking it might just be Heroku having a senior moment. Have you tried running through this a second time (using a new app URL) to see if you can reproduce the issue?

Elinos commented 9 years ago

Yes, I'm using deploy button. I've tried it one more time and it failed :( Here is the deploy log:

-----> Node.js app detected
-----> Creating runtime environment

       NPM_CONFIG_LOGLEVEL=error
       NPM_CONFIG_PRODUCTION=true
       NODE_ENV=production
       NODE_MODULES_CACHE=true
-----> Installing binaries
       engines.node (package.json):  ~0.10.0
       engines.npm (package.json):   unspecified (use default)

       Resolving node version ~0.10.0 via semver.io...
       Downloading and installing node 0.10.40...
       Using default npm version: 1.4.28
-----> Restoring cache
       Skipping cache (new runtime signature)
-----> Building dependencies
       Pruning any extraneous modules
       Installing node modules (package.json)

       > sqlite3@3.0.8 install /tmp/build_2a0f02d167a848f5754e0196a2717245/cobyism-ghost-on-heroku-f3f5247/node_modules/ghost/node_modules/sqlite3
       > node-pre-gyp install --fallback-to-build

       [sqlite3] Success: "/tmp/build_2a0f02d167a848f5754e0196a2717245/cobyism-ghost-on-heroku-f3f5247/node_modules/ghost/node_modules/sqlite3/lib/binding/node-v11-linux-x64/node_sqlite3.node" is installed via remote
       npm ERR! cb() never called!
       npm ERR! not ok code 0
-----> Build failed

       We're sorry this build is failing! You can troubleshoot common issues here:
       https://devcenter.heroku.com/articles/troubleshooting-node-deploys

       Some possible problems:

       - This version of npm (1.4.28) has several known issues - consider upgrading to the latest release (2.14.3)
         https://devcenter.heroku.com/articles/nodejs-support#specifying-an-npm-version

       Love,
       Heroku

 !     Push rejected, failed to compile Node.js app
cobyism commented 9 years ago

Considering you’ve received two separate, very different results from deploying, I’m fairly sure this is just Heroku’s build process being inconsistent, rather than something that’s actually wrong with this project/repo. I’ve experienced times (as recently as last week) when I’ve had to try deploying something to Heroku three or four times before it built and launched successfully.

Until we can determine an issue is predictably reproducible, I’m afraid the best answer is simply to try it again :persevere:. If you end up being able to predictably reproduce a certain issue, please let us know, but until then I’m going to close this issue for now. Don’t let that stop conversation though!