heroku-toolbelt

So I've read the documentation on pg:pull , but can't seem to get it to work. When I run the command with the correct parameters, my Heroku DB is fetched and a local database is created, but the schema is not filled in locally; e.g., no tables are created, no triggers are set up, no constraints, no data, etc. Here's the heroku pg:info log for my database: === HEROKU_POSTGRESQL_ORANGE_URL (DATABASE_URL) Plan: Hobby-dev Status: Available Connections: 1 PG Version: 9.3.3 Created: 2014-04-02 19:24 UTC Data Size: 7.4 MB Tables: 6 Rows: 1376/10000 (In compliance) Fork/Follow: Unsupported Rollback:

I am using Postgres on Heroku and am needing to dump one table from my production DB and dump it into my staging DB. I have the heroku tool belt installed, but am not sure how to dump a single db table to import into my staging db. catsby You can dump a single table of data like so: $ pg_dump --no-acl --no-owner -h [host ip].compute-1.amazonaws.com -U [user name] -t [table name] --data-only [database name] > table.dump You can get all of the values needed with this: $ heroku pg:credentials:url [DATABASE] -a [app_name] Connection info string: "dbname=[database name] host=[host ip].compute-1

I was trying to run heroku run rake db:migrate And was getting the error Cannot run more than 1 Free size dynos. See below for how to fix... The answer is to look for any open heroku sessions (you can use 'heroku ps' as john points out below), in my case I already had a started a heroku console session 30mins earlier and just forgot about it. So if you see the "Cannot run more than 1 Free size dynos" error just close any existing console or other heroku sessions you have open. Hopefully this saves someone the ten minutes it took me to come to my senses. Most Efective in console run: heroku ps

I launched a node.js server with the following line to set the port: app.set('port', process.env.PORT || 8080); This means that, it should either read the PORT env variable or default to 8080, as it does when it's run locally. Neither of them is happening on Heroku, and the server always uses the default port 80. Any idea how to change it? heroku config PORT: 8080 You can't. Heroku sets the PORT variable that you are supposed to bind, and listens on tcp/80. Heroku treats web apps just like any other app and doesn't allow you to assign listening ports directly. Your web server will be assigned

I want to host my source on bitbucket using git because I obviously get a free private repo and I want to host my app on heroku using the source code from bitbucket. Can i do it using the github client and heroku toolbelt. Will it work? Github is great but i dont want everyone seeing my code and I dont want to pay for a private repo because its a small project. Deploying to Heroku should work regardless of where you host your code as the Heroku CLI adds it's own git remote for the sake of deployments. In fact, you can even git pull from Heroku, so you could technically use Heroku as a private

MongoDB just forced an update on my Heroku server today from 2.6 to 3.0 Now my app crashes shortly after startup with the error: 2015-10-01T10:22:27.405579+00:00 heroku[web.1]: State changed from crashed to starting 2015-10-01T10:22:42.457971+00:00 heroku[web.1]: Starting process with command `node server` 2015-10-01T10:22:46.278159+00:00 app[web.1]: memory, and will not scale past a single process. 2015-10-01T10:22:46.278136+00:00 app[web.1]: Warning: connect.session() MemoryStore is not 2015-10-01T10:22:46.278157+00:00 app[web.1]: designed for a production environment, as it will leak 2015

I have executed: $ heroku login But when I try to push, I'm still asked for authentication: $ git push heroku master Username for 'https://git.heroku.com': <email> Password for 'https://<email>@git.heroku.com': Then I get a WARNING: Do not authenticate with username and password using Git. I ran heroku login again and authenticated successfully but I still get the same failure. I've checked the remote: $ git remote -v heroku https://git@heroku.com/appname.git (fetch) heroku https://git@heroku.com/appname.git (push) I've also generated a new public key, passed it to Heroku, and validated it: