Re: What version of PostgreSQL does Heroku use?
From your app's Heroku console you should be able to do the following: `psql --version` = psql (PostgreSQL) 8.3.14\ncontains support for command-line editing\n On Sep 23, 2011, at 9:36 AM, ebdb wrote: Hi. I'm just setting up my account and dev machine. I'd like to try to get my PostgreSQL version on my dev machine as close as possible to what's on Heroku. What version would that be? Thanks! E -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to heroku@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 heroku@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: Forcing traffic to www.
Thanks, but like I said, the traffic is never making it to my app server,
leaving any Rack middleware option unusable.
On Jun 2, 2011, at 12:36 AM, Hemal Kuntawala wrote:
I've got a before hook in my Sinatra app:
before do
if request.env['HTTP_HOST'] == APP_NAME.heroku.com ||
request.env['HTTP_HOST'] == APP_NAME.com
redirect http://www.APP_NAME.com#{request.fullpath};, 301
end
end
My rails knowledge is zero, but I'm guessing* you can write a before_filter
method in the ApplicationController to do something smiliar? Not sure if my
method is the best way either.
*I'm literally making this up.
On 2 June 2011 04:12, Aaron Brethorst aa...@brethorsting.com wrote:
I remember a couple weeks back we were strongly advised to send all traffic
to www. instead of a bare domain. What is the best way to ensure this
happens? I would do this at the Rack middleware level, but I'm getting
frequent reports of 'server not responding' errors from users when they try
accessing the site, which means the Rack option is right out.
Thanks,
Aaron
--
You received this message because you are subscribed to the Google Groups
Heroku group.
To post to this group, send email to heroku@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 heroku@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 heroku@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.
Forcing traffic to www.
I remember a couple weeks back we were strongly advised to send all traffic to www. instead of a bare domain. What is the best way to ensure this happens? I would do this at the Rack middleware level, but I'm getting frequent reports of 'server not responding' errors from users when they try accessing the site, which means the Rack option is right out. Thanks, Aaron -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to heroku@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: pg:reset with shared database failing
Thanks, Peter. Can you send out an email to the mailing list when it's solved?
Cheers,
Aaron
On Jan 26, 2011, at 1:22 PM, Peter van Hardenberg wrote:
We're working on that bug right now. Hope to have it released shortly. If the
matter is urgent, please open a support ticket and we'll run it manually.
Peter
On Wed, Jan 26, 2011 at 12:57 PM, Brian bburr...@gmail.com wrote:
I just had the exact same problem. Would really like to clear my
staging db to test a production migration.
Brian
On Jan 25, 4:57 pm, Aaron Brethorst aa...@brethorsting.com wrote:
I'm getting a rather unhelpful error message when I try resetting my shared
database. I'm using v1.17.10 of the gem.
heroku pg:reset --db SHARED_DATABASE_URL --app (my app name)
... ! Internal server error
I know that the post to /apps/#{app_name}/database_reset in
Heroku::Client#database_reset is returning a 500 error with no body, so I'm
a bit stuck.
Has anyone seen this, or know what's up?
--
You received this message because you are subscribed to the Google Groups
Heroku group.
To post to this group, send email to heroku@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 heroku@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 heroku@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.
pg:reset with shared database failing
I'm getting a rather unhelpful error message when I try resetting my shared
database. I'm using v1.17.10 of the gem.
heroku pg:reset --db SHARED_DATABASE_URL --app (my app name)
... ! Internal server error
I know that the post to /apps/#{app_name}/database_reset in
Heroku::Client#database_reset is returning a 500 error with no body, so I'm a
bit stuck.
Has anyone seen this, or know what's up?
--
You received this message because you are subscribed to the Google Groups
Heroku group.
To post to this group, send email to heroku@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: User White Label
I've actually been trying to do the same thing, and have run into the same roadblocks. Anyone? I'd hate to have to deploy this site on AWS instead of Heroku. On Nov 17, 2010, at 8:04 PM, Alfie wrote: I'd like to be able to offer my users a white label version of our product, meaning that their account page can be accessed from their personal domain rather than from our site so... www.myapp.com/users/account/1 can be accessed directly at... www.myusersdomain.com _without_ an iframe or generic forwarding. My first thought was to give users a subdomain and then have them use a CNAME to point their personal domain to their subdomain on my app but that doesn't seem to work (I get a Heroku error page that says Heroku No Such App). There has to be an easier way to do what I want to do right? -- 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: User White Label
Is there an upper bound on the number of domains that can be supported by Heroku for a single app? On Nov 19, 2010, at 12:22 PM, Oren Teich wrote: you need to register the domain with Heroku, and have the user setup their DNS to point to Heroku. e.g. either run heroku domains:add www.mydomain.com for each domain, or do that via api (look at the source to the gem to see the API call). You need to tell Heroku about each and every domain so we know how to route the traffic. Many sites do this - for example getcloudapp.com has this feature. Oren On Wed, Nov 17, 2010 at 8:04 PM, Alfie cityb...@gmail.com wrote: I'd like to be able to offer my users a white label version of our product, meaning that their account page can be accessed from their personal domain rather than from our site so... www.myapp.com/users/account/1 can be accessed directly at... www.myusersdomain.com _without_ an iframe or generic forwarding. My first thought was to give users a subdomain and then have them use a CNAME to point their personal domain to their subdomain on my app but that doesn't seem to work (I get a Heroku error page that says Heroku No Such App). There has to be an easier way to do what I want to do right? -- 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. -- 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: Calling all forks
Try out this fork of Delayed Job: http://github.com/pedro/delayed_job I've been using it for a week or two now, and it works beautifully. On Sep 2, 2010, at 12:40 PM, chris wrote: 2. Is there a better way that doesn't involve having a Worker running all the time? I've seen people mention that Workers can be spun up and deleted programmatically but I've yet to see what the API for doing so looks like. -- 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.
