Heroku - Latest Comments

Re: Heroku | Railslab Interview

Andy Croll — Thu, 02 Jul 2009 11:03:00 -0000

I did a quick rough transcription of the video as well. Interesting to hear about you're development environment being totally in the cloud!

http://andycroll.com/writing/adam-wiggins-and-r...

Re: Heroku | API and External Git Access

ph0rque — Mon, 22 Jun 2009 23:32:36 -0000

so git push/git pull resulted in the same problem as mentioned by Rob Roland; but git (push|pull) heroku master worked.

I solved the problem by adding the following to .git/config:

[branch "master"]
remote = heroku
merge = refs/heads/master

Re: Heroku | RSpec

Tiago Albineli Motta — Sat, 20 Jun 2009 15:16:57 -0000

On Generator:

Generate
Couldn't find 'rspec' generator

Re: Heroku | Gem Manifests

brianjp — Thu, 18 Jun 2009 14:42:06 -0000

One possible reason - that I encountered - is the manifest is a .gem.txt file.

If on XP, go to notepad and create a new gem manifest file (don't use the old one). Then select under "Save as type:" "All Files". This allows for creation of a file named ".gems" instead of .gems.txt (which, for me, gave the error you mentioned).
Hope that might help. Once I got past that glitch the gems loaded in response to push (noting I had to add a "/" i.e., ---source . . . rubyforge.org/, For some reason, I still can't get my app to run in heroku w/gems (runs w/o the gems just fine) - w/gems it runs just fine on my local machine. I'll continue debugging . . . .

Re: Heroku | Pimp Your Cart: Shopify Apps on Heroku

jtarchie — Fri, 12 Jun 2009 19:52:54 -0000

It would be interesting to see more about their integrated infrastructure including services used, scalability issues, costs, etc. Like one of those profiles on highscalability.com.

Re: Heroku | Pimp Your Cart: Shopify Apps on Heroku

mortenheroku — Fri, 12 Jun 2009 19:31:29 -0000

I believe they're currently running the website here, and some components related to this developer platform. We're super excited to have them, and hope to work even more closely together in the future.

Re: Heroku | Pimp Your Cart: Shopify Apps on Heroku

jtarchie — Fri, 12 Jun 2009 19:21:41 -0000

Does this mean that the entire shopify infrastructure is on the heroku.com platform? Or does it mean they are just running their website of it? Either would be an interesting case study for heroku to analyze.

Re: Heroku | Pimp Your Cart: Shopify Apps on Heroku

Jay Godse — Fri, 12 Jun 2009 17:30:01 -0000

Absolutely amazing! Well done.

Re: Heroku | Push and Pull Databases To and From Heroku

Jonas Elfström — Fri, 05 Jun 2009 08:08:49 -0000

I'm using DataMapper and a local MySQL. I've hade some problem to db:push to Heroku but I found a workaround:
* git push heroku
* auto_migrate! in the heroku console.
* heroku db:pull mysql://root:mypass@localhost/mydb
after that I can make changes in the local db and push them back to Heroku.

Also it seems to be some kind of problem with MySQL Decimals getting converted to Postgres Integers with a db:push (or maybe the auto_migrate! is the problem). Double works fine so I will stay away from decimals for now.

Re: Heroku | Radiant CMS in 5 Minutes Or Less

Dinooz — Mon, 01 Jun 2009 21:06:22 -0000

Question can you specify where is the ".gems" files need to be located.... I try in config/.gems but did not worked for me, later move it to the root of the application and that seems to have better results, however still have an error....

-----> Installing gem radiant 0.7.1 from http://gems.rubyforge.org
ERROR: Error installing radiant:
rspec-rails requires rspec (= 1.2.6, runtime)

error: hooks/pre-receive exited with error code 1
ng refs/heads/master pre-receive hook declined
error: failed to push to 'git@heroku.com:young-stream-99.git'

Re: Heroku | Add-on: Wildcard Domains

Brian — Thu, 28 May 2009 13:48:16 -0000

Thanks guys for the great service, I have been learning Rails 2.x for the past three months and Heroku has been there for me every step of the way!.

Re: Heroku | Commercial Launch

Mukund — Thu, 28 May 2009 03:12:43 -0000

Can't the dyno pricing be based on CPU time and dynamically scaled to handle concurrent requests? (Google App engine for example). In the current scenario, a single dyno = single mongrel equivalent = wait time for more than one concurrent user. If I want to avoid that, 36$ a month is steep for 2 dynos.

Re: Heroku | Radiant CMS in 5 Minutes Or Less

charlesroper — Sun, 24 May 2009 08:00:05 -0000

Yes, I just discovered this. It would be good if the post could be updated to avoid confusing beginners.

Re: Heroku | Radiant CMS in 5 Minutes Or Less

mortenheroku — Fri, 22 May 2009 12:08:22 -0000

You should ignore log, tmp, config/database.yml and probably also any db/*.sqlite3 files. While it's technically possible to use sqlite3 in the tmp/ dir on Heroku it is most decidedly *not* recommended. The tmp/ is for temporary storage only, so you should always use the provided PostgreSQL db for persistent data storage.

Re: Heroku | Radiant CMS in 5 Minutes Or Less

don — Fri, 22 May 2009 09:25:58 -0000

Should we also gitignore the log and and db or does heroku do some magic there?
Also, how is it possible to use sqlite3 on a readonly file system?

Re: Heroku | Gem Manifests

Patrick Leahy — Wed, 20 May 2009 03:25:18 -0000

Hey folks,
Just whipped out a simple scaffold. Called $ git add .gems...threw the follow error. Any clues? Thanks.

pathspec '.gems' did not match any files

Re: Heroku | Radiant CMS in 5 Minutes Or Less

marcelcorso — Sun, 17 May 2009 09:00:34 -0000

I tried
rspec --version 1.2.2
on the .gems file but I got an error saying that the radiant gem requires version 1.2.6.
I changed that and everything went ok.

Re: Heroku | Railsconf Schedule

Francois — Wed, 13 May 2009 13:55:29 -0000

The railsconf presentations were great. I look forward to trying out heroku. The concept is a wonderful time saver.

Re: Heroku | Commercial Launch

EK — Thu, 07 May 2009 11:35:40 -0000

I am really glad for you guys getting to a new stage.
The only problem I see - your pricing model seems too greedy. Did you really look at your costs and comparable hosting prices? Did you estimate how different plans can leverage each other?
You are more than great for free account, but - anything else lead to looking around for less expensive solutions.
Suggestion: look at existing [stable] rails (and non-rails) hosting providers/resellers, and match their offerings. In this case you will retain most of your customer base.

Re: Heroku | Commercial Launch

matttthompson — Tue, 05 May 2009 19:37:01 -0000

Between a really intuitive deployment process and some truly awesome branding with the dynos system, I think you've completely demystified deployment—the least enjoyable part of Rails.

I think back on the times where I could only pray that I could figure out FCGI on Dreamhost. Kids today have it way too easy.

Re: Heroku | Commercial Launch

Thomas Balthazar — Mon, 04 May 2009 09:12:55 -0000

Hello,

That's really exciting, you did an amazing job!
Do you have an ETA for the paid features being available to everybody?
Can't wait.

Keep up the good work!
Thomas.

Re: Heroku | Railsconf Schedule

jc00ke — Sun, 03 May 2009 20:03:22 -0000

Wish I were there this year as I'm a bit more interested in Sinatra than Rails. Oh well, that's what I get for living in Portland and being spoiled for 2 years.

Re: Heroku | Radiant CMS in 5 Minutes Or Less

jbinfoman — Fri, 01 May 2009 02:40:43 -0000

I cannot seem to get the gem for heroku to install. I use the gem install and get error message on rmake. cl not recognized as an internatl or external command.....

Not sure why?

Also got:
Checking for ruby/st.h....no
Checking for ruby/st.h...no
checking for ruby/re.h...no

Whats up?

Re: Heroku | Commercial Launch

Matthew Savage — Thu, 30 Apr 2009 08:28:00 -0000

Or.... (this just came to me) use something like a UCC or SANs certificate? Similar to SNI, but word it is works right now :P

Re: Heroku | Commercial Launch

Matthew Savage — Thu, 30 Apr 2009 08:23:35 -0000

Maybe you guys might be able to (*sigh* one day) offer DNS control as well, so you can allocate IP addresses and we can just point A records at it...

Though I figure this would also be limited by Amazon Elastic IP which is 1-to-1 with instances :( (well, thats an assumption anyways)....