Re: memcached servers
Thanks guys. I *think* we've got things installed correctly now.
Is there an easy way to see the stats for our memcache? I tried what
the docs say, and got this:
>> mc = Memcached.new
NameError: uninitialized constant Memcached
/usr/local/lib/ruby/gems/1.8/gems/activesupport-2.3.5/lib/
active_support/dependencies.rb:443:in `load_missing_constant'
/usr/local/lib/ruby/gems/1.8/gems/activesupport-2.3.5/lib/
active_support/dependencies.rb:80:in
`const_missing_not_from_s3_library'
/usr/local/lib/ruby/gems/1.8/gems/aws-s3-0.6.2/lib/aws/s3/
extensions.rb:206:in `const_missing'
/usr/local/lib/ruby/gems/1.8/gems/activesupport-2.3.5/lib/
active_support/dependencies.rb:92:in `const_missing'
Is there some web UI somewhere I can see?
Thanks again for everyones help,
Carson
On Dec 20, 11:12 am, chris wrote:
> FYI, dalli will detect that ENV variable automatically -- you shouldn't need
> to specify the server(s) at all. Here's our dalli configuration (rails3 app,
> yours may vary):
>
> config.cache_store = :dalli_store, { :namespace => 'll', :expires_in
> => 30.minutes, :compress => true, :compress_threshold => 64*1024 }
--
You received this message because you are subscribed to the Google Groups
"Heroku" group.
To post to this group, send email to her...@googlegroups.com.
To unsubscribe from this group, send email to
heroku+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/heroku?hl=en.
Re: No joy with Rails 3: no such file to load -- dispatcher (LoadError)
I had to add config.ru to the repository. Rails 3 has some new components which must be included in your git push. One way to figure out what's missing is to compare your app with a new, empty Rails 3 app. "git ls-files" lists the files in your git repository. A commit with nothing changed produces a list of untracked files. If any untracked file matches one in a new, empty app, or git ls-files doesn't include every filename in an empty app, then you have to add something to your tracked file set. Use "git add". Thanks to those who helped out. -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
Re: Rails3 + AmazonRDS addon: "missing the mysql2 gem" error
I came across this error as well. For the time being, I've reverted to the 'mysql' gem. -Chris On Dec 15, 6:08 pm, vovayartsev wrote: > Hi all. > > There seem to be a bug in Amazon RDS addon (or I'm doing something > wrong?). > Here are the steps to reproduce: > > 1. Create an empty rails-3.0.3 app with a single scaffolded resource. > 2. Add the "gem 'mysql2'" line to Gemfile; then execute `bundle > install`. Make sure the command 'bundle show mysql2' can find the gem. > 3. Push the app to Heroku (using the default bamboo-ree-1.8.7 stack). > 4. Make sure the 'db:migrate" task and the application itself run as > expected using the shared 5MB database. > 5. Launch an Amazon RDS instance in us-east-1a zone, then follow > thehttp://docs.heroku.com/amazon_rdsguidelines: > 5.1 rds-authorize-db-security-group-ingress ... # ok > 5.2 heroku db:pull mysql://user:p...@rdshostname.amazonaws.com/databasename > # ok > 5.3 heroku addons:add amazon_rds url=mysql:// > user:p...@rdshostname.amazonaws.com/databasename # ok > 5.4 heroku rake db:migrate # this FAILS > > The last step fails with the following error: > !!! Missing the mysql2 gem. Add it to your Gemfile: gem > 'mysql2' > > Note: I used the same url in 5.2 and 5.3 steps (I copy-pasted it to > avoid spelling errors). > > HERE'S WHAT I'd LIKE TO KNOW > > 1. Is this a know issue? Does anyone knows a workaround? > 2. If anyone was able to reproduce the issue? > 3. Are there Heroku techs reading this group? Or should I better post > a ticket tohttp://support.heroku.com/? -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
Re: Heroku and custom domain with Dreamhost
Thanks Oren, This was exactly the case, though it took a few hours longer than 24 hours which is why I started questioning what I did. Most other times I had to wait for DNS propagation, it only needed 6 hours or so. On Mon, Dec 20, 2010 at 14:35, Oren Teich wrote: > Wait 24 hours, and check again. DNS by its nature takes a while to > get all around the internet. > > > On Sun, Dec 19, 2010 at 7:29 PM, Braxo wrote: > > Hello, > > > > I register my domains at Dreamhost. I have an application on Heroku > > and I am trying to use a custom domain. > > > > I have added the domain, both root and www to the application and also > > added the three A type records and the www CNAME record at Dreamhost. > > > > My NS type records still point to ns#.dreamhost.com. > > > > The domain still does not direct to the application and I get a server > > cannot be found in my browser. > > > > Has anybody successfully pointed a Dreamhost domain to their Heroku > > application? > > > > - Braxo > > > > -- > > You received this message because you are subscribed to the Google Groups > "Heroku" group. > > To post to this group, send email to her...@googlegroups.com. > > To unsubscribe from this group, send email to > heroku+unsubscr...@googlegroups.com > . > > For more options, visit this group at > http://groups.google.com/group/heroku?hl=en. > > > > > > -- > You received this message because you are subscribed to the Google Groups > "Heroku" group. > To post to this group, send email to her...@googlegroups.com. > To unsubscribe from this group, send email to > heroku+unsubscr...@googlegroups.com > . > For more options, visit this group at > http://groups.google.com/group/heroku?hl=en. > > -- *Jesse Thomson* signed Location: GMT -5 -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
Re: Wildcard subdomains with GoDaddy
Hello Barry, I like having a single url for my address. So I setup a redirect that bounced www.mydomain.com to http://mydomain.com/ I remember godaddy was a little tricky on this one. Think they were able to redirect www.mydomain.com to mydomain.com but able to redirect mydomain.com to www.mydomain.com But Orien's solution for using wild cards works as well. --Keenan On Dec 20, 2010, at 2:15 PM, Barry Welch wrote: > I am also having trouble with GoDaddy + Heroku with wildcard > subdomains > > In my setup, since GoDaddy apparently doesn't allow wildcard CNAMES, I > currently have 3 A-records that look like this: > > A-Record * 75.101.163.44 > A-Record * 75.101.163.44 > A-Record * 75.101.163.44 > > .. with no CNAMES. > > Of course, this means 'http://www.mydomain.com' will load just fine, > but 'http://mydomain.com' will not. > Aside from changing registrars or using the Zerigo add-on, I am at a > loss as to how to set this up. > > The Heroku documentation about wildcard domains is vague, stating: > > "To use with a custom domain, configure your registrar to point > *.yourdomain.com at heroku.com. If things are set up correctly you > should be able to look up any arbitrary subdomain:" > > ... which seems like a cop-out statement. > > Any ideas on this? > > On Nov 15, 11:57 am, Keenan Brock wrote: >> Hi Jeff, >> >> I had it working before I switched everything over tohttp://namecheap.com/ >> >> 2 things to try: >> 1) try an @ instead of a * >> 2) try using A records instead of a CNAME (3 of them) >> >> dns numbers are athttp://docs.heroku.com/custom-domains >> 75.101.163.44 >> 75.101.145.87 >> 174.129.212.2 >> >> --Keenan >> >> On Nov 14, 2010, at 12:48 AM, Jeff wrote: >> >> >> >>> Having trouble setting up GoDaddy for wildcard subdomains. I have one >>> domain registered with Dreamhost, and it works fine. Not sure what's >>> different with GD. >> >>> I have the three A records: >> >>> A @ 174.129.212.2 >>> A @ 75.101.145.87 >>> A @ 75.101.163.44 >> >>> But I can't set up a CNAME like this: >> >>> * CNAME proxy.heroku.com. >> >>> With DH, this works. But with GD, I can't find the right way to >>> handle. Any ideas? >> >>> -- >>> You received this message because you are subscribed to the Google Groups >>> "Heroku" group. >>> To post to this group, send email to her...@googlegroups.com. >>> To unsubscribe from this group, send email to >>> heroku+unsubscr...@googlegroups.com. >>> For more options, visit this group >>> athttp://groups.google.com/group/heroku?hl=en.- Hide quoted text - >> >> - Show quoted text - > > -- > You received this message because you are subscribed to the Google Groups > "Heroku" group. > To post to this group, send email to her...@googlegroups.com. > To unsubscribe from this group, send email to > heroku+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/heroku?hl=en. > -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
Re: Wildcard subdomains with GoDaddy
Thanks Oren. If this is true for all registrars, I would definitely point this out in your custom domains documentation. On Dec 20, 1:34 pm, Oren Teich wrote: > Add three more records for . or yourdomain.com. you need 6 if you're > using wildcard - three for the wildcard, three for the root domain. > > Oren > > > > On Mon, Dec 20, 2010 at 11:15 AM, Barry Welch wrote: > > I am also having trouble with GoDaddy + Heroku with wildcard > > subdomains > > > In my setup, since GoDaddy apparently doesn't allow wildcard CNAMES, I > > currently have 3 A-records that look like this: > > > A-Record * 75.101.163.44 > > A-Record * 75.101.163.44 > > A-Record * 75.101.163.44 > > > .. with no CNAMES. > > > Of course, this means 'http://www.mydomain.com'will load just fine, > > but 'http://mydomain.com'will not. > > Aside from changing registrars or using the Zerigo add-on, I am at a > > loss as to how to set this up. > > > The Heroku documentation about wildcard domains is vague, stating: > > > "To use with a custom domain, configure your registrar to point > > *.yourdomain.com at heroku.com. If things are set up correctly you > > should be able to look up any arbitrary subdomain:" > > > ... which seems like a cop-out statement. > > > Any ideas on this? > > > On Nov 15, 11:57 am, Keenan Brock wrote: > >> Hi Jeff, > > >> I had it working before I switched everything over tohttp://namecheap.com/ > > >> 2 things to try: > >> 1) try an @ instead of a * > >> 2) try using A records instead of a CNAME (3 of them) > > >> dns numbers are athttp://docs.heroku.com/custom-domains > >> 75.101.163.44 > >> 75.101.145.87 > >> 174.129.212.2 > > >> --Keenan > > >> On Nov 14, 2010, at 12:48 AM, Jeff wrote: > > >> > Having trouble setting up GoDaddy for wildcard subdomains. I have one > >> > domain registered with Dreamhost, and it works fine. Not sure what's > >> > different with GD. > > >> > I have the three A records: > > >> > A @ 174.129.212.2 > >> > A @ 75.101.145.87 > >> > A @ 75.101.163.44 > > >> > But I can't set up a CNAME like this: > > >> > * CNAME proxy.heroku.com. > > >> > With DH, this works. But with GD, I can't find the right way to > >> > handle. Any ideas? > > >> > -- > >> > You received this message because you are subscribed to the Google > >> > Groups "Heroku" group. > >> > To post to this group, send email to her...@googlegroups.com. > >> > To unsubscribe from this group, send email to > >> > heroku+unsubscr...@googlegroups.com. > >> > For more options, visit this group > >> > athttp://groups.google.com/group/heroku?hl=en.-Hide quoted text - > > >> - Show quoted text - > > > -- > > You received this message because you are subscribed to the Google Groups > > "Heroku" group. > > To post to this group, send email to her...@googlegroups.com. > > To unsubscribe from this group, send email to > > heroku+unsubscr...@googlegroups.com. > > For more options, visit this group > > athttp://groups.google.com/group/heroku?hl=en.- Hide quoted text - > > - Show quoted text - -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
Re: Heroku and custom domain with Dreamhost
Wait 24 hours, and check again. DNS by its nature takes a while to get all around the internet. On Sun, Dec 19, 2010 at 7:29 PM, Braxo wrote: > Hello, > > I register my domains at Dreamhost. I have an application on Heroku > and I am trying to use a custom domain. > > I have added the domain, both root and www to the application and also > added the three A type records and the www CNAME record at Dreamhost. > > My NS type records still point to ns#.dreamhost.com. > > The domain still does not direct to the application and I get a server > cannot be found in my browser. > > Has anybody successfully pointed a Dreamhost domain to their Heroku > application? > > - Braxo > > -- > You received this message because you are subscribed to the Google Groups > "Heroku" group. > To post to this group, send email to her...@googlegroups.com. > To unsubscribe from this group, send email to > heroku+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/heroku?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
Re: Wildcard subdomains with GoDaddy
Add three more records for . or yourdomain.com. you need 6 if you're using wildcard - three for the wildcard, three for the root domain. Oren On Mon, Dec 20, 2010 at 11:15 AM, Barry Welch wrote: > I am also having trouble with GoDaddy + Heroku with wildcard > subdomains > > In my setup, since GoDaddy apparently doesn't allow wildcard CNAMES, I > currently have 3 A-records that look like this: > > A-Record * 75.101.163.44 > A-Record * 75.101.163.44 > A-Record * 75.101.163.44 > > .. with no CNAMES. > > Of course, this means 'http://www.mydomain.com' will load just fine, > but 'http://mydomain.com' will not. > Aside from changing registrars or using the Zerigo add-on, I am at a > loss as to how to set this up. > > The Heroku documentation about wildcard domains is vague, stating: > > "To use with a custom domain, configure your registrar to point > *.yourdomain.com at heroku.com. If things are set up correctly you > should be able to look up any arbitrary subdomain:" > > ... which seems like a cop-out statement. > > Any ideas on this? > > On Nov 15, 11:57 am, Keenan Brock wrote: >> Hi Jeff, >> >> I had it working before I switched everything over tohttp://namecheap.com/ >> >> 2 things to try: >> 1) try an @ instead of a * >> 2) try using A records instead of a CNAME (3 of them) >> >> dns numbers are athttp://docs.heroku.com/custom-domains >> 75.101.163.44 >> 75.101.145.87 >> 174.129.212.2 >> >> --Keenan >> >> On Nov 14, 2010, at 12:48 AM, Jeff wrote: >> >> >> >> > Having trouble setting up GoDaddy for wildcard subdomains. I have one >> > domain registered with Dreamhost, and it works fine. Not sure what's >> > different with GD. >> >> > I have the three A records: >> >> > A @ 174.129.212.2 >> > A @ 75.101.145.87 >> > A @ 75.101.163.44 >> >> > But I can't set up a CNAME like this: >> >> > * CNAME proxy.heroku.com. >> >> > With DH, this works. But with GD, I can't find the right way to >> > handle. Any ideas? >> >> > -- >> > You received this message because you are subscribed to the Google Groups >> > "Heroku" group. >> > To post to this group, send email to her...@googlegroups.com. >> > To unsubscribe from this group, send email to >> > heroku+unsubscr...@googlegroups.com. >> > For more options, visit this group >> > athttp://groups.google.com/group/heroku?hl=en.- Hide quoted text - >> >> - Show quoted text - > > -- > You received this message because you are subscribed to the Google Groups > "Heroku" group. > To post to this group, send email to her...@googlegroups.com. > To unsubscribe from this group, send email to > heroku+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/heroku?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
OpenSSL::Random::RandomError: PRNG not seeded
Does anyone have any idea why I might be seeing the exception in the subject of this post? The stack trace is as follows :- /usr/ruby1.8.7/lib/ruby/1.8/securerandom.rb:53:in `random_bytes' /usr/ruby1.8.7/lib/ruby/1.8/securerandom.rb:53:in `random_bytes' /usr/ruby1.8.7/lib/ruby/1.8/securerandom.rb:91:in `hex' .bundle/gems/ruby/1.8/gems/activesupport-3.0.1/lib/active_support/ notifications/instrumenter.rb:32:in `unique_id' .bundle/gems/ruby/1.8/gems/activesupport-3.0.1/lib/active_support/ notifications/instrumenter.rb:10:in `initialize' .bundle/gems/ruby/1.8/gems/activesupport-3.0.1/lib/active_support/ notifications.rb:74:in `new' .bundle/gems/ruby/1.8/gems/activesupport-3.0.1/lib/active_support/ notifications.rb:74:in `instrumenter' .bundle/gems/ruby/1.8/gems/activerecord-3.0.1/lib/active_record/ connection_adapters/abstract_adapter.rb:44:in `initialize' .bundle/gems/ruby/1.8/gems/activerecord-3.0.1/lib/active_record/ connection_adapters/postgresql_adapter.rb:220:in `initialize' .bundle/gems/ruby/1.8/gems/activerecord-3.0.1/lib/active_record/ connection_adapters/postgresql_adapter.rb:25:in `new' .bundle/gems/ruby/1.8/gems/activerecord-3.0.1/lib/active_record/ connection_adapters/postgresql_adapter.rb:25:in `postgresql_connection' .bundle/gems/ruby/1.8/gems/activerecord-3.0.1/lib/active_record/ connection_adapters/abstract/connection_pool.rb:230:in `send' .bundle/gems/ruby/1.8/gems/activerecord-3.0.1/lib/active_record/ connection_adapters/abstract/connection_pool.rb:230:in `new_connection' .bundle/gems/ruby/1.8/gems/activerecord-3.0.1/lib/active_record/ connection_adapters/abstract/connection_pool.rb:238:in `checkout_new_connection' .bundle/gems/ruby/1.8/gems/activerecord-3.0.1/lib/active_record/ connection_adapters/abstract/connection_pool.rb:194:in `checkout' .bundle/gems/ruby/1.8/gems/activerecord-3.0.1/lib/active_record/ connection_adapters/abstract/connection_pool.rb:190:in `loop' .bundle/gems/ruby/1.8/gems/activerecord-3.0.1/lib/active_record/ connection_adapters/abstract/connection_pool.rb:190:in `checkout' /usr/ruby1.8.7/lib/ruby/1.8/monitor.rb:242:in `synchronize' .bundle/gems/ruby/1.8/gems/activerecord-3.0.1/lib/active_record/ connection_adapters/abstract/connection_pool.rb:189:in `checkout' .bundle/gems/ruby/1.8/gems/activerecord-3.0.1/lib/active_record/ connection_adapters/abstract/connection_pool.rb:96:in `connection' .bundle/gems/ruby/1.8/gems/activerecord-3.0.1/lib/active_record/ connection_adapters/abstract/connection_pool.rb:318:in `retrieve_connection' .bundle/gems/ruby/1.8/gems/activerecord-3.0.1/lib/active_record/ connection_adapters/abstract/connection_specification.rb:97:in `retrieve_connection' .bundle/gems/ruby/1.8/gems/activerecord-3.0.1/lib/active_record/ connection_adapters/abstract/connection_specification.rb:89:in `connection' .bundle/gems/ruby/1.8/gems/activerecord-3.0.1/lib/active_record/ base.rb:679:in `columns' .bundle/gems/ruby/1.8/gems/activerecord-3.0.1/lib/active_record/ base.rb:692:in `column_names' .bundle/gems/ruby/1.8/gems/activerecord-3.0.1/lib/active_record/ base.rb:705:in `column_methods_hash' .bundle/gems/ruby/1.8/gems/activerecord-3.0.1/lib/active_record/ base.rb:1043:in `all_attributes_exists?' .bundle/gems/ruby/1.8/gems/activesupport-3.0.1/lib/active_support/ dependencies.rb:239:in `all?' .bundle/gems/ruby/1.8/gems/activerecord-3.0.1/lib/active_record/ base.rb:1043:in `each' .bundle/gems/ruby/1.8/gems/activerecord-3.0.1/lib/active_record/ base.rb:1043:in `all?' .bundle/gems/ruby/1.8/gems/activerecord-3.0.1/lib/active_record/ base.rb:1043:in `all_attributes_exists?' .bundle/gems/ruby/1.8/gems/activerecord-3.0.1/lib/active_record/ base.rb:991:in `method_missing' Thanks, James. -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
Heroku and custom domain with Dreamhost
Hello, I register my domains at Dreamhost. I have an application on Heroku and I am trying to use a custom domain. I have added the domain, both root and www to the application and also added the three A type records and the www CNAME record at Dreamhost. My NS type records still point to ns#.dreamhost.com. The domain still does not direct to the application and I get a server cannot be found in my browser. Has anybody successfully pointed a Dreamhost domain to their Heroku application? - Braxo -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
Re: What is this output from "heroku create"
I've got the the same problem. Were you able to fix the problem? On Dec 10, 2:59 pm, SWEngineer wrote: > Hi, > > I'm trying to create a Heroku place using "heroku create", and get the > following: (What is the problem?) > > C:\Users\Software Engineer>heroku create > Creating cold-flower-61... done > Createdhttp://cold-flower-61.heroku.com/| g...@heroku.com:cold- > flower-61.git > C:/Ruby192/lib/ruby/gems/1.9.1/gems/heroku-1.14.8/lib/heroku/ > helpers.rb:75:in > ': No such file or directory - git remote (Errno::ENOENT) > from C:/Ruby192/lib/ruby/gems/1.9.1/gems/heroku-1.14.8/lib/ > heroku/help > s.rb:75:in `block in shell' > from C:/Ruby192/lib/ruby/1.9.1/fileutils.rb:121:in `chdir' > from C:/Ruby192/lib/ruby/1.9.1/fileutils.rb:121:in `cd' > from C:/Ruby192/lib/ruby/gems/1.9.1/gems/heroku-1.14.8/lib/ > heroku/help > s.rb:75:in `shell' > from C:/Ruby192/lib/ruby/gems/1.9.1/gems/heroku-1.14.8/lib/ > heroku/comm > ds/app.rb:265:in `create_git_remote' > from C:/Ruby192/lib/ruby/gems/1.9.1/gems/heroku-1.14.8/lib/ > heroku/comm > ds/app.rb:49:in `create' > from C:/Ruby192/lib/ruby/gems/1.9.1/gems/heroku-1.14.8/lib/ > heroku/comm > d.rb:48:in `run_internal' > from C:/Ruby192/lib/ruby/gems/1.9.1/gems/heroku-1.14.8/lib/ > heroku/comm > d.rb:20:in `run' > from C:/Ruby192/lib/ruby/gems/1.9.1/gems/heroku-1.14.8/bin/ > heroku:13:i > `' > from C:/Ruby192/bin/heroku:19:in `load' > from C:/Ruby192/bin/heroku:19:in `' > > Thanks a lot. -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
Re: What is this output from "heroku create"
I have the same problem. Were you able to fix it? On Dec 10, 2:59 pm, SWEngineer wrote: > Hi, > > I'm trying to create a Heroku place using "heroku create", and get the > following: (What is the problem?) > > C:\Users\Software Engineer>heroku create > Creating cold-flower-61... done > Createdhttp://cold-flower-61.heroku.com/| g...@heroku.com:cold- > flower-61.git > C:/Ruby192/lib/ruby/gems/1.9.1/gems/heroku-1.14.8/lib/heroku/ > helpers.rb:75:in > ': No such file or directory - git remote (Errno::ENOENT) > from C:/Ruby192/lib/ruby/gems/1.9.1/gems/heroku-1.14.8/lib/ > heroku/help > s.rb:75:in `block in shell' > from C:/Ruby192/lib/ruby/1.9.1/fileutils.rb:121:in `chdir' > from C:/Ruby192/lib/ruby/1.9.1/fileutils.rb:121:in `cd' > from C:/Ruby192/lib/ruby/gems/1.9.1/gems/heroku-1.14.8/lib/ > heroku/help > s.rb:75:in `shell' > from C:/Ruby192/lib/ruby/gems/1.9.1/gems/heroku-1.14.8/lib/ > heroku/comm > ds/app.rb:265:in `create_git_remote' > from C:/Ruby192/lib/ruby/gems/1.9.1/gems/heroku-1.14.8/lib/ > heroku/comm > ds/app.rb:49:in `create' > from C:/Ruby192/lib/ruby/gems/1.9.1/gems/heroku-1.14.8/lib/ > heroku/comm > d.rb:48:in `run_internal' > from C:/Ruby192/lib/ruby/gems/1.9.1/gems/heroku-1.14.8/lib/ > heroku/comm > d.rb:20:in `run' > from C:/Ruby192/lib/ruby/gems/1.9.1/gems/heroku-1.14.8/bin/ > heroku:13:i > `' > from C:/Ruby192/bin/heroku:19:in `load' > from C:/Ruby192/bin/heroku:19:in `' > > Thanks a lot. -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
Re: Wildcard subdomains with GoDaddy
I am also having trouble with GoDaddy + Heroku with wildcard subdomains In my setup, since GoDaddy apparently doesn't allow wildcard CNAMES, I currently have 3 A-records that look like this: A-Record * 75.101.163.44 A-Record * 75.101.163.44 A-Record * 75.101.163.44 .. with no CNAMES. Of course, this means 'http://www.mydomain.com' will load just fine, but 'http://mydomain.com' will not. Aside from changing registrars or using the Zerigo add-on, I am at a loss as to how to set this up. The Heroku documentation about wildcard domains is vague, stating: "To use with a custom domain, configure your registrar to point *.yourdomain.com at heroku.com. If things are set up correctly you should be able to look up any arbitrary subdomain:" ... which seems like a cop-out statement. Any ideas on this? On Nov 15, 11:57 am, Keenan Brock wrote: > Hi Jeff, > > I had it working before I switched everything over tohttp://namecheap.com/ > > 2 things to try: > 1) try an @ instead of a * > 2) try using A records instead of a CNAME (3 of them) > > dns numbers are athttp://docs.heroku.com/custom-domains > 75.101.163.44 > 75.101.145.87 > 174.129.212.2 > > --Keenan > > On Nov 14, 2010, at 12:48 AM, Jeff wrote: > > > > > Having trouble setting up GoDaddy for wildcard subdomains. I have one > > domain registered with Dreamhost, and it works fine. Not sure what's > > different with GD. > > > I have the three A records: > > > A @ 174.129.212.2 > > A @ 75.101.145.87 > > A @ 75.101.163.44 > > > But I can't set up a CNAME like this: > > > * CNAME proxy.heroku.com. > > > With DH, this works. But with GD, I can't find the right way to > > handle. Any ideas? > > > -- > > You received this message because you are subscribed to the Google Groups > > "Heroku" group. > > To post to this group, send email to her...@googlegroups.com. > > To unsubscribe from this group, send email to > > heroku+unsubscr...@googlegroups.com. > > For more options, visit this group > > athttp://groups.google.com/group/heroku?hl=en.- Hide quoted text - > > - Show quoted text - -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
cron to request a page
Hi, I'm using http caching and I want to run a daily cron to request a page in order to update the cache. I learnt how to make a cron at: http://docs.heroku.com/cron Could you tell me how to request a page? -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
Re: memcached servers
FYI, dalli will detect that ENV variable automatically -- you shouldn't need
to specify the server(s) at all. Here's our dalli configuration (rails3 app,
yours may vary):
config.cache_store = :dalli_store, { :namespace => 'll', :expires_in
=> 30.minutes, :compress => true, :compress_threshold => 64*1024 }
--
You received this message because you are subscribed to the Google Groups
"Heroku" group.
To post to this group, send email to her...@googlegroups.com.
To unsubscribe from this group, send email to
heroku+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/heroku?hl=en.
Watir on heroku
Hi, guys. I want to scrap an HTML site which is using javascript to generate the contents. So, I can't use mechanize gem or similar ones. I've tried rdom and taka with johnson, but still some problems (I could give you more details). The best and easiest option I have at the moment is to use watir (or selenium or celerity for jruby). I've selected watir, it's simple, the watir gem or even the watir-webdriver gem. I like them. But I have two problems: - I want to deploy the app in heroku but I get the error: "Could not find Firefox binary (os=linux)". - I don't know if it's possible to access to the watir logic without the need of the browser binary (and without open it in background). I currently have an answer here: http://stackoverflow.com/questions/3597118/can-you-deploy-watir-on-heroku-to-generate-html-snapshots-if-so-how, but I just wanted to confirm the options I have. I write a watir-webdriver example, working well in local, to ilustrate the simple process (in this case html is not dynamically generated, of course, it's only an example): require "rubygems" require "watir-webdriver" require "watir-webdriver/extensions/wait" browser = Watir::Browser.new :firefox browser.goto "http://google.com"; browser.text_field(:name, 'q').set "watir-webdriver" browser.button(:name, 'btnG').click Maybe the only option I have is to use EC2, but it's a pitty because I only need to scrap javascript-generated HTML and I want to keep on using heroku, I love it!!! What do you think is the best gem for me to do it on heroku? Or there's no option and I have to use EC2 just to open a browser, losing the heroku goodness? Thanks in advance -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
