Easy way to prevent Heroku idling?

You can install the free New Relic add-on. It has an availability monitor feature that will ping your site twice per minute, thus preventing the dyno from idling. More or less the same solution as Jesse but maybe more integrated to Heroku… And with a few perks (performance monitoring is just great). Note: to all … Read more

Should I check in folder “node_modules” to Git when creating a Node.js app on Heroku?

Second Update The FAQ is not available anymore. From the documentation of shrinkwrap: If you wish to lock down the specific bytes included in a package, for example to have 100% confidence in being able to reproduce a deployment or build, then you ought to check your dependencies into source control, or pursue some other … Read more

heroku – how to see all the logs

Update (thanks to dawmail333): heroku logs -n 1500 or, to tail the logs live heroku logs -t Heroku log documentation If you need more than a few thousand lines you can Use heroku’s Syslog Drains Alternatively (old method): $ heroku run rails c File.open(‘log/production.log’, ‘r’).each_line { |line| puts line }

Permission denied (publickey) when deploying heroku code. fatal: The remote end hung up unexpectedly

You have to upload your public key to Heroku: heroku keys:add ~/.ssh/id_rsa.pub If you don’t have a public key, Heroku will prompt you to add one automatically which works seamlessly. Just use: heroku keys:add To clear all your previous keys do : heroku keys:clear To display all your existing keys do : heroku keys EDIT: … Read more

How to link a folder with an existing Heroku app

Heroku links your projects based on the heroku git remote (and a few other options, see the update below). To add your Heroku remote as a remote in your current repository, use the following command: git remote add heroku git@heroku.com:project.git where project is the name of your Heroku project (the same as the project.heroku.com subdomain). … Read more

Hata!: SQLSTATE[HY000] [1045] Access denied for user 'divattrend_liink'@'localhost' (using password: YES)