cobyism / ghost-on-heroku Goto Github PK

Just tested the button this morning, and it rejected the push. Here’s the build output I got:

-----> Node.js app detected
-----> Reading application state
       package.json...
       build directory...
       cache directory...
       environment variables...
       Node engine:         ~0.10.0
       Npm engine:          unspecified
       Start mechanism:     Procfile
       node_modules source: package.json
       node_modules cached: false
       NPM_CONFIG_PRODUCTION=true
       NODE_MODULES_CACHE=true
-----> Installing binaries
       Resolving node version ~0.10.0 via semver.io...
       Downloading and installing node 0.10.38...
       Using default npm version: 1.4.28
-----> Building dependencies
       No cache available
       Installing node modules

       > [email protected] install /tmp/build_7e6a841bf3c97710d0889e6ecd64da46/cobyism-ghost-on-heroku-12e87ae/node_modules/ghost/node_modules/sqlite3
       > node-pre-gyp install --fallback-to-build

       [sqlite3] Success: "/tmp/build_7e6a841bf3c97710d0889e6ecd64da46/cobyism-ghost-on-heroku-12e87ae/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! If you can't find the issue in application code,
       please submit a ticket so we can help: https://help.heroku.com/
       You can also try reverting to our legacy Node.js buildpack:
       heroku config:set BUILDPACK_URL=https://github.com/heroku/heroku-buildpack-nodejs#v63

       Love,
       Heroku
 !     Push rejected, failed to compile Node.js app

I have followed all the steps to add the Custom Domain to Heroku #37 , but I get a "NET::ERR_CERT_COMMON_NAME_INVALID", you can see it on https://blog.lolagomezdebarros.es/
My local heroku app is: https://lolaghost.herokuapp.com/, which works fine.
I haven't seen any thing like that in any of the other issues. Any suggestion?
Thanks for your time and great resource.

Hi there,
I setup ghost on heroku and I have my heroku url working at https://tomiwaxyz.herokuapp.com

I have also setup a custom domain in heroku to https://tomiwa.xyz
That means I needed to update my Ghost heroku url to https://tomiwa.xyz
The root for https://tomiwa.xyz is pointed to https://tomiwaxyz.herokuapp.com using cloudflare

The result is a redirect loop, is there something I am not doing right?

Is anyone else receiving ERROR: ghost-s3 is not configured when trying to add an image?

I copied the repo and pushed it to heroku. Everything else seems to work except for S3 uploads.

Should storage/ghost-s3 be updated to storage/ghost-s3-storage-adapter to reflect the new dependency in package.json?

In recent times, Google cloud storage has emerged as a strong and price competitive option to AWS. Is there any way I can link my google cloud storage bucket instead of S3?

Sorry this isn't more specific, I don't really use Node in production, and so I'm not sure how to go about debugging this. It happens on seemingly random occasions - sometimes almost as soon as the application is restarted, other times it'll run for days at a time.

2015-06-23T16:32:28.319398+00:00 heroku[web.1]: Starting process with command `npm start --production`
2015-06-23T16:32:31.173840+00:00 app[web.1]: Detected 512 MB available memory, 512 MB limit per process (WEB_MEMORY)
2015-06-23T16:32:31.173866+00:00 app[web.1]: Recommending WEB_CONCURRENCY=1
2015-06-23T16:32:38.321230+00:00 app[web.1]: 
2015-06-23T16:32:38.321234+00:00 app[web.1]: > [email protected] start /app
2015-06-23T16:32:38.321236+00:00 app[web.1]: > node server.js
2015-06-23T16:32:38.321237+00:00 app[web.1]: 
2015-06-23T16:32:43.348030+00:00 app[web.1]: Migrations: Up to date at version 003
2015-06-23T16:32:44.103103+00:00 app[web.1]: Ghost is running... 
2015-06-23T16:32:44.103108+00:00 app[web.1]: Your blog is now available on http://52dishes.co.uk 
2015-06-23T16:32:44.103110+00:00 app[web.1]: Ctrl+C to shut down
2015-06-23T16:32:44.685499+00:00 heroku[web.1]: State changed from starting to up
2015-06-23T16:33:29.841782+00:00 app[web.1]: 
2015-06-23T16:33:29.842354+00:00 app[web.1]:         throw er; // Unhandled 'error' event
2015-06-23T16:33:29.842704+00:00 app[web.1]:               ^
2015-06-23T16:33:29.844019+00:00 app[web.1]: error: terminating connection due to administrator command
2015-06-23T16:33:29.844022+00:00 app[web.1]:     at Connection.parseE (/app/node_modules/ghost/node_modules/pg/lib/connection.js:534:11)
2015-06-23T16:33:29.844023+00:00 app[web.1]:     at Connection.parseMessage (/app/node_modules/ghost/node_modules/pg/lib/connection.js:361:17)
2015-06-23T16:33:29.844027+00:00 app[web.1]:     at Socket.emit (events.js:95:17)
2015-06-23T16:33:29.844029+00:00 app[web.1]:     at Socket.emit (events.js:92:17)
2015-06-23T16:33:29.842022+00:00 app[web.1]: events.js:72
2015-06-23T16:33:29.844028+00:00 app[web.1]:     at Socket.<anonymous> (_stream_readable.js:765:14)
2015-06-23T16:33:29.881234+00:00 app[web.1]: npm ERR! [email protected] start: `node server.js`
2015-06-23T16:33:29.844032+00:00 app[web.1]:     at emitReadable (_stream_readable.js:423:5)
2015-06-23T16:33:29.844025+00:00 app[web.1]:     at Socket.<anonymous> (/app/node_modules/ghost/node_modules/pg/lib/connection.js:105:22)
2015-06-23T16:33:29.844034+00:00 app[web.1]:     at readableAddChunk (_stream_readable.js:166:9)
2015-06-23T16:33:29.844031+00:00 app[web.1]:     at emitReadable_ (_stream_readable.js:427:10)
2015-06-23T16:33:29.881705+00:00 app[web.1]: npm ERR! Failed at the [email protected] start script.
2015-06-23T16:33:29.881444+00:00 app[web.1]: npm ERR! Exit status 8
2015-06-23T16:33:29.882201+00:00 app[web.1]: npm ERR! This is most likely a problem with the ghost-on-heroku package,
2015-06-23T16:33:29.882626+00:00 app[web.1]: npm ERR! You can get their info via:
2015-06-23T16:33:29.882523+00:00 app[web.1]: npm ERR!     node server.js
2015-06-23T16:33:29.883056+00:00 app[web.1]: npm ERR! System Linux 3.13.0-49-generic
2015-06-23T16:33:29.844035+00:00 app[web.1]:     at Socket.Readable.push (_stream_readable.js:128:10)
2015-06-23T16:33:29.872578+00:00 app[web.1]: 
2015-06-23T16:33:29.881599+00:00 app[web.1]: npm ERR! 
2015-06-23T16:33:29.882307+00:00 app[web.1]: npm ERR! not with npm itself.
2015-06-23T16:33:29.883780+00:00 app[web.1]: npm ERR! code ELIFECYCLE
2015-06-23T16:33:29.882414+00:00 app[web.1]: npm ERR! Tell the author that this fails on your system:
2015-06-23T16:33:29.882767+00:00 app[web.1]: npm ERR!     npm owner ls ghost-on-heroku
2015-06-23T16:33:29.883202+00:00 app[web.1]: npm ERR! command "/app/.heroku/node/bin/node" "/app/.heroku/node/bin/npm" "start" "--production"
2015-06-23T16:33:29.882877+00:00 app[web.1]: npm ERR! There is likely additional logging output above.
2015-06-23T16:33:29.886787+00:00 app[web.1]: npm ERR! Additional logging details can be found in:
2015-06-23T16:33:29.886897+00:00 app[web.1]: npm ERR!     /app/npm-debug.log
2015-06-23T16:33:29.887282+00:00 app[web.1]: npm ERR! not ok code 0
2015-06-23T16:33:29.883340+00:00 app[web.1]: npm ERR! cwd /app
2015-06-23T16:33:29.883509+00:00 app[web.1]: npm ERR! node -v v0.10.38
2015-06-23T16:33:29.883647+00:00 app[web.1]: npm ERR! npm -v 1.4.28
2015-06-23T16:33:29.886671+00:00 app[web.1]: npm ERR! 
2015-06-23T16:33:30.678203+00:00 heroku[web.1]: Process exited with status 1
2015-06-23T16:33:30.691157+00:00 heroku[web.1]: State changed from up to crashed

After creating and testing the live app, I cloned the source to my workstation with heroku git:clone appname. In return I get an empty repo. Then I tried to ssh to the app and create a git repo manually. The ssh terminal simply freezed, and the app crashed.

Ran through two setups and I can't figure out where it's gone wrong. Set up a new bucket and new IAM user (no groups or permissions attached). Included all config vars correctly, as far as I can tell. Here is the bucket policy:

{
    "Id": "Policy1465054892694",
    "Version": "2012-10-17",
    "Statement": [
        {
            "Sid": "Stmt1465054801755",
            "Action": [
                "s3:ListBucket"
            ],
            "Effect": "Allow",
            "Resource": "arn:aws:s3:::<bucketname>",
            "Principal": {
                "AWS": [
                    "arn:aws:iam::<awsID>:user/<iamusername>"
                ]
            }
        },
        {
            "Sid": "Stmt1465054845550",
            "Action": [
                "s3:DeleteObject",
                "s3:GetObject",
                "s3:PutObject"
            ],
            "Effect": "Allow",
            "Resource": "arn:aws:s3:::<bucketname>/*",
            "Principal": {
                "AWS": [
                    "arn:aws:iam::363628483589:user/<iamusername>"
                ]
            }
        },
        {
            "Sid": "Stmt1465054887900",
            "Action": [
                "s3:GetObject"
            ],
            "Effect": "Allow",
            "Resource": "arn:aws:s3:::<bucketname>/*",
            "Principal": "*"
        }
    ]
}

I even tried adding a grantee of "Everyone" to the bucket with access, but still got Access Denied. Here's a log record:

27f33dcde6266001f37a6e5328c7c6343419b6ea6acb1310e176d2af426c959f <bucketname> [04/Jun/2016:01:45:57 +0000] 54.163.103.165 arn:aws:iam::<awsID>:user/<iamuser> DA10333234650546 REST.PUT.OBJECT 2016/Jun/1424443_174755136058674_264701358_n-1465004757600.png "PUT /2016/Jun/1424443_174755136058674_264701358_n-1465004757600.png HTTP/1.1" 403 AccessDenied 243 13308 24 - "-" "aws-sdk-nodejs/2.3.17 linux/v0.10.45" -

I installed on Heroku using the Deploy to Heroku, and out-of-the-box it does not allow uploading images.

During uploading a blue progress bar appears, but then turns read and the ghost message "Something went wrong" appears.

I am using a pure out of box install on Heroku, with the stock casper 1.2.5 theme.

Details:

Wordpress import actually worked fairly well. The imported blog posts with (already uploaded) images looks fine.

What does not work is uploading any new image.

• Cannot upload into a new blog post.
• Cannot upload blog cover
• Cannot upload blog logo

I tried jpeg and png, file sizes of 6LB up to 300kb, using Safari 9.01 and Chrome Version 46.0.2490.71 (64-bit) running on a Mac with El Capitan 10.11.1

In my Heroku ENV vars I have defined: S3_ACCESS_KEY_ID, S3_ACCESS_SECRET_KEY, S3_BUCKET_NAME, and S3_BUCKET_REGION (us-east-1)

How can I use Google Drive / Dropbox as Ghost Storage instead of Amazon S3?

Getting an issue when I upload a blog cover or logo where the image is uploaded to Amazon S3 but the UI never completes. It simply displays the wiggly cat indefinitely. Is there anyway to view the logs for ghost-on-heroku or does this issue sound familiar?

Cheers,
James

Mailgun has a free tier and might be better for trialling Ghost on Heroku without a cost commitment.

Ghost released a new version 0.7.0
https://github.com/TryGhost/Ghost/releases/tag/0.7.0

The image attached is no show. I checked with s3 the files already there.
Check with browser inspect or copy paste the content look ok for me but the app just not display image. Don't know what missing

Is this not possible? We'd like to run ghost on a subdirectory basically and according to this

https://www.allaboutghost.com/how-to-install-ghost-in-a-subdirectory/

we just need to change the config.js to refer to the new path.

the config.js in this project already has that value specified as HEROKU_URL. Hooray!

But when I edit the variable to https://our-url.com/cms it doesn't seem to work.

Am I doing something wrong or is this not possible with this implementation?

The Node engine specified in package.json is 0.10.0, specifying a newer version like 4.1.1 causes the build to fail by attempting a compile of the sqlite module. I think this is related to #15 and #29

Hi,

I got an issue when I click on the button to deploy ghost platform.

       > [email protected] install /tmp/build_d1a373006d5305dee38ad451a2944f9c/cobyism-ghost-on-heroku-a11a874/node_modules/ghost/node_modules/sqlite3
       > node-pre-gyp install --fallback-to-build

       [sqlite3] Success: "/tmp/build_d1a373006d5305dee38ad451a2944f9c/cobyism-ghost-on-heroku-a11a874/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.0)
         https://devcenter.heroku.com/articles/nodejs-support#specifying-an-npm-version

       Love,
       Heroku

 !     Push rejected, failed to compile Node.js app

Can you help me?

Thanks

My app is up and running on heroku just fine, but when I try to download it locally using
heroku git:clone --app MYAPPNAME

Its creates the folder and the git init, but it's an empty folder and in the console:
warning: You appear to have cloned an empty repository.

And when using a client to create a new repo locally it complains about not having a master branch:
fatal: Couldn't find remote ref master

Having deployed Ghost 0.9.0 successfully to Heroku in the past, I noticed your package.json node version does not match the current recommendation for running Ghost 0.9.0 here.
I am a total beginner to Node, but I am unsure if this would cause an issue when launching the Ghost server? I mean, I'm guessing Ghost server would not be running on the 4.2+ version of node, would it?

Anyways, after upgrading my own blog to Ghost 0.9.0 and Node 4.2+, I noticed a bunch of R14 Memory errors on the Heroku metrics console for my blog app. These errors cause my dyno to use swap space, making response time a bit slower and causing ocassional restarts of the app. Turns out Garbage Collection is a bit lazy in Node 4.2 +, as disscussed here.

The discussion leads to a solution of this problem with this package, but I was unable to make it work swiftly on my installation. Essentially it is just a bash script to query the amount of memory allocated to your dyno, which then adjusts three memory usage flags you can pass to node to avoid this error. I ended up setting up the flags directly on the call to node on the start command of Ghost's own package.json. Dirty, dirty, and hardcoded to match my current dyno size.

Perhaps we can take both the upgrade to Node 4.2+ and the memory management issue into consideration? I'd be glad to help.

..................

Any idea when that will be handled?

Tried deploying to Heroku using the one click deploy. Here is the following log from Heroku:

`/tmp/build_dadeff5abd5dc88602a0c2bd31d52b42/cobyism-ghost-on-heroku-2581f67
> ncp node_modules/Casper content/themes/casper

   There were errors during the copy.
   Error: ENOENT, lstat '/tmp/build_dadeff5abd5dc88602a0c2bd31d52b42/cobyism-ghost-on-heroku-2581f67/node_modules/Casper'

   npm ERR! Linux 3.13.0-95-generic
   npm ERR! argv "/tmp/build_dadeff5abd5dc88602a0c2bd31d52b42/cobyism-ghost-on-heroku-2581f67/.heroku/node/bin/node" "/tmp/build_dadeff5abd5dc88602a0c2bd31d52b42/cobyism-ghost-on-heroku-2581f67/.heroku/node/bin/npm" "install" "--unsafe-perm" "--userconfig" "/tmp/build_dadeff5abd5dc88602a0c2bd31d52b42/cobyism-ghost-on-heroku-2581f67/.npmrc"
   npm ERR! node v0.10.47
   npm ERR! npm  v2.15.1
   npm ERR! code ELIFECYCLE
   npm ERR! [email protected] postinstall: `ncp node_modules/Casper content/themes/casper`
   npm ERR! Exit status 1
   npm ERR!
   npm ERR! Failed at the [email protected] postinstall script 'ncp node_modules/Casper content/themes/casper'.
   npm ERR! This is most likely a problem with the ghost-on-heroku package,
   npm ERR! not with npm itself.
   npm ERR! Tell the author that this fails on your system:
   npm ERR!     ncp node_modules/Casper content/themes/casper
   npm ERR! You can get information on how to open an issue for this project with:
   npm ERR!     npm bugs ghost-on-heroku
   npm ERR! Or if that isn't available, you can get their info via:
   npm ERR!
   npm ERR!     npm owner ls ghost-on-heroku
   npm ERR! There is likely additional logging output above.

   npm ERR! Please include the following file with any support request:
   npm ERR!     /tmp/build_dadeff5abd5dc88602a0c2bd31d52b42/cobyism-ghost-on-heroku-2581f67/npm-debug.log

-----> Build failed`

This line in the README doesn't actually work:

To make changes to your Ghost blog (like adding a theme to the /content directory, for instance), clone your blog locally using the Heroku Toolbelt:

 heroku git:clone --app YOURAPPNAME

See #62 and #67 for context. From Heroku support:

Recent changes are such that heroku git:clone is only useful for applications that are deployed with Heroku's hosted git service. In effect this means that applications deployed via GitHub, DropBox or "Deploy to Heroku" buttons will result in an empty repo when cloned.

In that case, you'll need to download the source repository and add the heroku remote to that repo. Once you've done that you can push with git (git push heroku master) and you'll be able to clone the repo after that.

Pretty bad/inconsistent user experience, but out of our control. We should update the docs to explain a working approach.

Hi, Just take a look. It's a first time run.

Peace,
Vladimir Minkin

I am wondering how I can install a custom theme.

First, just want to say this script to get up and running on heroku with Ghost works great, thanks for making it so easy.

The issue I'm having now is configuring my DNS to add my blog to a custom subdomain. It seems that adding a Custom Resource Record CNAME, supplying it with the heroku url, and then navigating to the subdomain results in the browser forwarding to the url of the app hosted on heroku. This behavior doesn't seem to happen for other apps hosted on heroku that I have successfully added to subdomains on my custom domain and seem to be integrated properly (I'm using Google Domains to manage DNS).

I was wondering if anyone was able to successfully add a custom sub-domain (NOT just subdomain forwarding) for your Ghost app hosted on heroku, or if this is a known issue.

I just installed today, completely clean installation. I've never used ghost before and am looking forward to using it. I can replicate this bug on my macbook (chrome, safari), iphone (safari), and my windows 10 desktop (chrome). The bug is non-existent in the edge browser on win10. It happens both on the "post preview" view and once you navigate to the post.

In the "Welcome to Ghost" post, I noticed a bug in the following segment of text.

Writing in Markdown is really easy. In the left hand panel of Ghost, you simply write as you normally would. Where appropriate, you can use shortcuts to style your content. For example, a list:

• Item number one
• Item number two
  • A nested item
• A final item

Specifically, the word "final" shows up as "inal".

First off, let me say that all of these strings are being correctly written to the DOM. They are, however, being displayed incorrectly in the browser. I did some cursory tests and found that it's not exclusive this post either. I made a second post combining the letters "f" and "i" in various ways. Additionally, the casing of the letters matters. For instance,

• "Fi"
• "FI"
• "fI"

all of these combinations are displayed correctly.

• "fi" --> "i"

is the first example of a combination displayed incorrectly.

• "ffi" will be displayed correctly.
• "ffii" will be displayed correctly.
• "fa" will be displayed correctly.
• "fii" will be displayed incorrectly. --> "ii"
• "ifi" will be displayed incorrectly. --> "ii"
• "Ffi" will be displayed incorrectly. --> "Fi"

I'm sure there are other combinations that are able to break, but I have no idea what would be

A live example can be found at that link.

If you would like access to https://bug-demonstration.herokuapp.com/ghost/editor/2/ so you can drill into the examples for yourself, PM me for the login credentials. This is a demo site and as such it has no sensitive data.

I've added my custom domain in the console, the 301 forward works fine but once in on the app the name changes back, I've changed my HEROKU_URL env but that didn't change a thing :(

Hi guys, i have a problem and its only happening with ghost, when i configure the app and click to deploy, a message error appear:
Could not communicate with vendor, please try again later

Is a configuration error or somebody else have the same problem?.
Thanks.

Everything on Amazon S3 is fine because I tested it with another application but when I try to upload something (like the blog cover or the blog logo), I get this error in the JavaScript console:

Failed to load resource: the server responded with a status of 503 (Service Unavailable)
https://name-of-my-app.herokuapp.com/ghost/api/v0.1/uploads/

TryGhost/Ghost#4600 has been closed.

🚀

Firstly I'm sorry if this is my bad.
I started my blog with this handy tool but after that I wanted to change some code.
So I cloned heroku repo with command heroku git:clone -a appname as it's suggested in heroku docs.
What was my wondering when git told me warning: You appear to have cloned an empty repository.
Maybe you have some ideas? Would be great. Thanks a lot.

Hello,

In the past, I have been using Ghost with DigitalOcean and I had access to the "core" folder. It had two files that interested me to change the language of the blog into Arabic. A CSS file and moment.js file.

Now I am moving to heroku and after I clone I seem to not find the folder and not even casper theme folder. I looked into the .gitignore file and made it empty and committed my work and tried to re-clone again. Still I don't get the core folder nor the casper.

Can you please help me?
Thank you.

I did a clean ghost-on-heroku install and then cloned the repo using heroku git:clone -a MYAPP. I then did a cd to that directory and ran npm install --production. I expected to be able to run npm start after that, but instead got this error:

> [email protected] start /Users/willhitch26/Projects/Development/outside-found-ghost
> node server.js


module.js:340
    throw err;
          ^
Error: Cannot find module './lib/express'
    at Function.Module._resolveFilename (module.js:338:15)
    at Function.Module._load (module.js:280:25)
    at Module.require (module.js:364:17)
    at require (module.js:380:17)
    at Object.<anonymous> (/Users/willhitch26/Projects/Development/outside-found-ghost/node_modules/ghost/node_modules/express/index.js:2:18)
    at Module._compile (module.js:456:26)
    at Object.Module._extensions..js (module.js:474:10)
    at Module.load (module.js:356:32)
    at Function.Module._load (module.js:312:12)
    at Module.require (module.js:364:17)

npm ERR! [email protected] start: `node server.js`
npm ERR! Exit status 8
npm ERR!
npm ERR! Failed at the [email protected] start script.
npm ERR! This is most likely a problem with the ghost-on-heroku package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node server.js
npm ERR! You can get their info via:
npm ERR!     npm owner ls ghost-on-heroku
npm ERR! There is likely additional logging output above.
npm ERR! System Darwin 14.3.0
npm ERR! command "/Users/willhitch26/.nvm/v0.10.33/bin/node" "/Users/willhitch26/.nvm/v0.10.33/bin/npm" "start"
npm ERR! cwd /Users/willhitch26/Projects/Development/outside-found-ghost
npm ERR! node -v v0.10.33
npm ERR! npm -v 1.4.28
npm ERR! code ELIFECYCLE
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR!     /Users/willhitch26/Projects/Development/outside-found-ghost/npm-debug.log
npm ERR! not ok code 0

Simply followed the instructions in the README. I did set a name for the app and changed YOURAPPNAME in HEROKU URL box. This where the problems start:

> ncp node_modules/Casper content/themes/casper

       There were errors during the copy.
       Error: ENOENT, lstat '/tmp/build_775a4825961df60db5a3b868394b3806/cobyism-ghost-on-heroku-2581f67/node_modules/Casper'

       npm ERR! Linux 3.13.0-100-generic
       npm ERR! argv "/tmp/build_775a4825961df60db5a3b868394b3806/cobyism-ghost-on-heroku-2581f67/.heroku/node/bin/node" "/tmp/build_775a4825961df60db5a3b868394b3806/cobyism-ghost-on-heroku-2581f67/.heroku/node/bin/npm" "install" "--unsafe-perm" "--userconfig" "/tmp/build_775a4825961df60db5a3b868394b3806/cobyism-ghost-on-heroku-2581f67/.npmrc"
       npm ERR! node v0.10.48
       npm ERR! npm  v2.15.1
       npm ERR! code ELIFECYCLE
       npm ERR! [email protected] postinstall: `ncp node_modules/Casper content/themes/casper`
       npm ERR! Exit status 1
       npm ERR!
       npm ERR! Failed at the [email protected] postinstall script 'ncp node_modules/Casper content/themes/casper'.
       npm ERR! This is most likely a problem with the ghost-on-heroku package,
       npm ERR! not with npm itself.
       npm ERR! Tell the author that this fails on your system:
       npm ERR!     ncp node_modules/Casper content/themes/casper
       npm ERR! You can get information on how to open an issue for this project with:
       npm ERR!     npm bugs ghost-on-heroku
       npm ERR! Or if that isn't available, you can get their info via:
       npm ERR!
       npm ERR!     npm owner ls ghost-on-heroku
       npm ERR! There is likely additional logging output above.

       npm ERR! Please include the following file with any support request:
       npm ERR!     /tmp/build_775a4825961df60db5a3b868394b3806/cobyism-ghost-on-heroku-2581f67/npm-debug.log
-----> Build failed

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

       If you're stuck, please submit a ticket so we can help:
       https://help.heroku.com/

       Love,
       Heroku

 !     Push rejected, failed to compile Node.js app.
 !     Push failed

Hey there,

After I clicked the purple "Deploy on Heroku" button, I set the app name etc and when I click the "Deploy for free" button, while it is configuring environment, it asks me to fill my payment information to verify my identity. Is it necessary to do that? is it gonna charge me?

Thanks,
Harry

I would like to let you know that I tried my fork to support GMail instead of Mandrill for SMTP transport.
Thanks.
https://github.com/dai-shi/ghost-on-heroku

Hey,

I installed ghost some month ago on heroku with your one-click installer and still using 0.5.8. What is the suggested / easiest way to update to the latest Version? Maybe you could also add that description to the Readme.

Hi guys,

Apparently, I can't upload images through dashboard although S3 on Heroku is set up correctly

Thanks

Cuando subo un tema en la carpeta de temas y reinicio el "Dyno" el tema no hacia efecto el area de administración de ghost; la carpeta que uso es esta: MYAPP/content/themes

También intente instalarlo desde el navegador (area de administración) pero el problema persiste, no se cual sea el problema. espero que me ayuden. gracias.

I think I have S3 uploads set up correctly, but none of the files I try to add to posts finish uploading successfully. I'm getting an error in my browser console that says "Failed to load resource: the server responded with a status of 503 (Service Unavailable)" with a url of (myherokuapp.com) "/ghost/api/v0.1/uploads/"

Images never actually make it to the bucket, so I suppose there's could be something happening there. But the error seems like there's a misconfiguration inside the app. What am I missing here?

this may be a dumb question but why isn't Casper inside the themes directory?

Check https://github.com/TryGhost/Ghost/commits/master/config.example.js for detail.

That means we cannot run node server.js to load config.js just like before?

First of all, thank you guys for doing that!
My issue is rather a question - how do I update default(casper) theme?
Le'ts say i want to change some css in index.hbs file?

Thanks in advance.

Check this https://dev.ghost.org/dropping-support-for-postgresql/

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)

       > [email protected] 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
       [email protected] node_modules/pg
       ├── [email protected]
       ├── [email protected]
       ├── [email protected]
       ├── [email protected]
       ├── [email protected]
       ├── [email protected] ([email protected], [email protected], [email protected], [email protected], [email protected])
       └── [email protected] ([email protected])

       [email protected] node_modules/ghost-s3-storage
       ├── [email protected]
       └── [email protected] ([email protected], [email protected], [email protected])

       [email protected] node_modules/ghost
       ├── [email protected]
       ├── [email protected]
       ├── [email protected]
       ├── [email protected] ([email protected])
       ├── [email protected]
       ├── [email protected] ([email protected])
       ├── [email protected]
       ├── [email protected] ([email protected], [email protected])
       ├── [email protected]
       ├── [email protected] ([email protected], [email protected], [email protected], [email protected], [email protected])
       ├── [email protected] ([email protected], [email protected])
       ├── [email protected] ([email protected], [email protected], [email protected])
       ├── [email protected] ([email protected], [email protected], [email protected])
       ├── [email protected] ([email protected], [email protected], [email protected], [email protected])
       ├── [email protected] ([email protected])
       ├── [email protected] ([email protected])
       ├── [email protected]
       ├── [email protected] ([email protected], [email protected], [email protected], [email protected])
       ├── [email protected] ([email protected], [email protected], [email protected], [email protected])
       ├── [email protected]
       ├── [email protected] ([email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected])
       ├── [email protected]
       ├── [email protected]
       ├── [email protected] ([email protected], [email protected], [email protected])
       ├── [email protected] ([email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected])
       ├── [email protected] ([email protected], [email protected], [email protected], [email protected], [email protected], [email protected])
       ├── [email protected] ([email protected], [email protected], [email protected], [email protected], [email protected], [email protected])
       ├── [email protected] ([email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected])
       ├── [email protected] ([email protected], [email protected])
       ├── [email protected] ([email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected])
       ├── [email protected] ([email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected])
       ├── [email protected] ([email protected], [email protected], [email protected], [email protected])
       ├── [email protected] ([email protected], [email protected], [email protected], [email protected], [email protected], [email protected])
       ├── [email protected] ([email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected])
       ├── [email protected]
       ├── [email protected] ([email protected], [email protected], [email protected])
       ├── [email protected] ([email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected])
       ├── [email protected] ([email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected])
       ├── [email protected] ([email protected], [email protected], [email protected])
       └── [email protected] ([email protected])
-----> Caching build
       Clearing previous node cache
       Saving 1 cacheDirectories (default):
       - node_modules
-----> Build succeeded!
       ├── [email protected]
       ├── [email protected]
       └── [email protected]

-----> 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?

please upgrade ,thanks

Where is this App actually saving the Themes when you import then via the Admin page?