it takes a little time for these things to propagate across the internet.
Sometimes up to 3 days.
And to make it worse, your computer, your router, and possibly your hosting
provider all cache the records. So it is tricky to know once you got it right.
I tried the url and got the parked
If you have it, I prefer to use dig, it gives you rather more
information
$ dig razzledazzle.it
; DiG 9.6.0-APPLE-P2 razzledazzle.it
;; global options: +cmd
;; Got answer:
;; -HEADER- opcode: QUERY, status: NOERROR, id: 61546
;; flags: qr rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 3, ADDITIONAL:
Hey Chaz,
for rails apps,
config/initializers/session_store.rb usually has a secret key
ActionController::Base.session = {
:key = '_charles_session',
:secret = 'XX'
}
you can get a good session key by running:
rake secret
Create the file and see how it goes.
--Keenan
On
I noticed that the documentation recommends using Solr for search:
http://docs.heroku.com/full-text-search
However, Postgres has a built-in full text search capability that is
not discussed at all. I was wondering what the rationale is for the
recommendation of Solr?
Would the performance
Because you don't have access to the DB directly, many of the built in
search solutions aren't available on Heroku. Using built in FTS or things
like tsearch will break taps for example, and are not supported. A few
people have reports of getting them running, but it's not production
quality.
On Tue, Feb 9, 2010 at 01:21, Mike mikel...@gmail.com wrote:
I noticed that the documentation recommends using Solr for search:
http://docs.heroku.com/full-text-search
However, Postgres has a built-in full text search capability that is
not discussed at all. I was wondering what the
On Wed, Feb 10, 2010 at 9:41 AM, Oren Teich o...@heroku.com wrote:
Because you don't have access to the DB directly, many of the built in
search solutions aren't available on Heroku. Using built in FTS or things
like tsearch will break taps for example, and are not supported. A few
people
