Javascript features work on localhost but not when deployed to Heroku
Manually precompiling worked for me. bundle exec rake assets:precompile before you push to heroku.
Manually precompiling worked for me. bundle exec rake assets:precompile before you push to heroku.
I had the same problem and I just now I found what was wrong. I first accidently called the file ProcFile instead of Procfile. Simply renaming that file did not get picked up by git. I had to do a git rm ProcFile -f first and then add a new (correctly named) Procfile. After that, … Read more
First, don’t use PWD. Just use __dirname. It works on Heroku exactly as it works anywhere else. Using PWD makes your app more brittle if you, for instance, execute a binary from a non-local directory. Second, the reason that file doesn’t exist on Heroku is likely because you’ve added it to your .gitignore file or … Read more
This may happen if your procfile is misspelt, such as “procfile” or “ProcFile” etc. The file name should be “Procfile” (with a capital P). sometimes changing the file name is not anough, because git wouldn’t spot the change. I had to delete the Procfile completely, then commit the change, than add it again with the … Read more
Wow…this took me forever, and a bunch of info on the web was wrong. Even Heroku’s docs didn’t seem to indicate this was possible. But Jesper J’s answer provides a hint in the right direction: it works with DNSimple’s ALIAS record which I guess is some new sort of DNS record they created. I had … Read more
You can use QuotaGuard Static Heroku add-on. QuotaGuard can be attached to a Heroku application via the command line: $ heroku addons:add quotaguardstatic After installing, the application should be configured to fully integrate with the add-on. When you sign up you will be provided with a unique username and password that you can use when … Read more
All processes must have unique names. Additionally, the names web and worker are insignificant and carry no special meaning. The only process that carries a significant name is the web process, as stated in the Heroku docs: The web process type is special as it’s the only process type that will receive HTTP traffic from … Read more
Heroku has a set of default buildpacks, used when it needs to detect the language of your app. In order to do that detection, it runs the bin/detect command of each of those default buildpacks, until one of them returns a 0 exit code. This is the command for the node buildpack. As you can … Read more
This is how you do it: heroku pg:psql –app YOUR_APP_NAME_HERE < updates.sql And if you want to restore your production into staging (assuming both are heroku postgres DBs): heroku pgbackups:restore YOUR_STAGING_DATABASE_NAME `heroku pgbackups:url –app YOUR_PRODUCTION_APP_NAME` –app YOUR_STAGING_APP_NAME –confirm YOUR_STAGING_APP_NAME Make sure to preserve the special single quotes around heroku pgbackups:url –app YOUR_PRODUCTION_APP_NAME. HEROKU TOOLBELT UPDATE … Read more
You shouldn’t use a postgres command to fully delete your database, as you will not have permissions to create a new one. Instead you should use the heroku command to clear out your database: heroku pg:reset DATABASE_URL