heroku

问题 I've inherited a repository that contains both a NodeJS part and a Python part. The project structure is such that the NodeJS is at the root of the repository, and the Python pieces are in a Python folder: root |- app |- some.js |- files.js |- Python |- other.py |- files.py I've set up a Heroku dyno to serve both a Python server and a NodeJS server, by doing this in my Procfile (based loosely on this older article): web: npm start python: sh -c 'cd ./Python/ && export PYTHONPATH=. && python

问题 I have an app running in Heroku; I'm using the Heroku scheduler to run a python script that scales the number of dynos at particular times of the day, using the python API (following this answer): import heroku cloud = heroku.from_key(os.environ.get('HEROKU_API_KEY')) app = cloud.apps['myapp'] webproc = app.processes['web'] webproc.scale(1) My question is: is there an API call to change Dyno types ? For instance to change it from "standard 1X" to "standard 2X" or to "hobby". Thanks 回答1: A

问题 why do we add this in static.json file at root => { "root": "dist/", "routes": { "/**": "index.html" } } 回答1: static.json file is used with heroku-buildpack-static during deployment with heroku for handling static sites and single page web apps. A number of options can be configured in static.json . Amongst them Root allows you to specify a different asset root for the directory of your application. By default it is public_html/ Custom Routes You can define custom routes that combine to a

问题 I think i am having a problem in my Procfile. The deploy is compiled successfully but the app does not start with this message -- 2014-03-27T14:17:06.465302+00:00 heroku[api]: Deploy ea0e14d by xxxx@gmail.com 2014-03-27T14:17:06.465378+00:00 heroku[api]: Release v10 created by xxxx@gmail.com 2014-03-27T14:17:14.091032+00:00 heroku[web.1]: Starting process with command `target/universal/stage/bin/enigmatic-dusk-7498 -Dhttp.port=32253` 2014-03-27T14:17:15.199466+00:00 app[web.1]: bash: target

问题 I incorrectly made a push to heroku and used heroku rollback to roll it back to a previous version. That worked fine in that my heroku app is now serving the rolled back version. But when a colleague who had pulled the "corrupted" push tried to checkout the "correct" version after the rollback, his git checkout from master branch is giving him the "corrupted" version and not the rolled back version. Any idea why Heroku rolled back the application but not the master git repo? 回答1: Ideally you

问题 I incorrectly made a push to heroku and used heroku rollback to roll it back to a previous version. That worked fine in that my heroku app is now serving the rolled back version. But when a colleague who had pulled the "corrupted" push tried to checkout the "correct" version after the rollback, his git checkout from master branch is giving him the "corrupted" version and not the rolled back version. Any idea why Heroku rolled back the application but not the master git repo? 回答1: Ideally you

问题 I'm trying to deploy a simple Geddyjs (node.js) app to Heroku. When I make a push a recive that error: git push heroku master Heroku receiving push Heroku push rejected, no Cedar-supported app detected What I have to do to that heroku detect the nodejs app? 回答1: couple of things did you do this for cedar you need to explicitly say this (I am sure you have done this but here for completeness) heroku create --stack cedar ensure that your package.json is at the root heroku have a good article on

问题 When pushing to Heroku, my db:migrate failed at the following: ! Heroku client internal error. Error: Unable to verify certificate, please set `Excon.defaults[:ssl_ca_path] = path_to_certs`, `Excon.defaults[:ssl_ca_file] = path_to_file`, or `Excon.defaults[:ssl_verify_peer] = false` (less secure). (Excon::Errors::SocketError) So, I added the following to the bottom of my production.rb file (my certs at in the root file) Excon.defaults[:ssl_ca_path] = Rails.root Same error. So I then tried the

问题 I am a ruby, ruby on rails and heroku greenhorn, which is trying to learn to code from Michael Hartl's Ruby on Rails 3.2 tutorial. Now at the very beginning of this chapter I failed to deployed all to Heroku. This error message I got (but I have no plan what to do to solve this problem): $ git push heroku master Counting objects: 69, done. Delta compression using up to 2 threads. Compressing objects: 100% (54/54), done. Writing objects: 100% (69/69), 27.34 KiB, done. Total 69 (delta 5),

问题 I've been using Heroku for over a year now to deploy my Django app. Suddenly though (without any major changes) everytime I push to Heroku, I'm getting the error, (Utils::TimeoutError) ! [remote rejected] master -> master (pre-receive hook declined) error: failed to push some refs to 'git@heroku.com:appname.git' It happens everytime, but at different stages of installing all the packages in my requirements.txt file. What could be causing this? 回答1: The docs for the python build pack talk