Re: Renaming the Hosting URL for a Facebook App
After I remove it, I can add it back. Let me know if that doesn't work. -- Richard Schneeman http://heroku.com @schneems (http://twitter.com/schneems) On Saturday, April 21, 2012 at 6:31 AM, nK0de wrote: > given is to remove it. No option to edit/change. Is that setting in > -- You received this message because you are subscribed to the Google Groups "Heroku" group. 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_US?hl=en
Re: git tagging heroku releases
Something that tagged your Git repo with release information prior to a deploy would definitely be helpful to some people. Neil On Monday, 23 April 2012 at 16:07, david ignacio wrote: > Well that's embarrassing. Looks like when I found the need for this, > I had several issues in my repo/app running in concert. This made me > think that when the hashes listed in `heroku releases` differed from > both `git log heroku/master` and `git log master` that I was perhaps > seeing an alternate hash generated by the slug compilation. > > Don't mind me I guess, at least I only spent a day or so on this > script, although I think that perhaps then converting the idea into a > heroku cli plugin that just took the versions in releases and created > the tags as scraped could still have value? > > Thoughts? > > On Mon, Apr 23, 2012 at 09:10, Neil Middleton (mailto:neil.middle...@gmail.com)> wrote: > > You've lost me a little here. `heroku releases` gives you all the deployed > > git versions and other changes. For instance: > > > > Rel Change ByWhen > > -- ---- > > v214 Deploy 5f3f619 neil.middle...@gmail.com > > (mailto:neil.middle...@gmail.com)2012-04-18 > > 17:28:41 +0100 > > v213 Deploy b71ce95 neil.middle...@gmail.com > > (mailto:neil.middle...@gmail.com)2012-04-12 > > 15:04:45 +0100 > > v212 Deploy d27f151 neil.middle...@gmail.com > > (mailto:neil.middle...@gmail.com)2012-04-12 > > 13:20:53 +0100 > > v211 Deploy 6b81eef neil.middle...@gmail.com > > (mailto:neil.middle...@gmail.com)2012-04-12 > > 12:59:28 +0100 > > v210 Config add FACEBOOK_APP_SECR.. neil.middle...@gmail.com > > (mailto:neil.middle...@gmail.com)2012-04-12 > > 12:56:11 +0100 > > v209 Deploy 2f54f24 neil.middle...@gmail.com > > (mailto:neil.middle...@gmail.com)2012-04-12 > > 11:43:28 +0100 > > v208 Deploy 19b486d neil.middle...@gmail.com > > (mailto:neil.middle...@gmail.com)2012-04-12 > > 11:36:34 +0100 > > v207 Deploy efdd6ef neil.middle...@gmail.com > > (mailto:neil.middle...@gmail.com)2012-04-12 > > 11:22:40 +0100 > > > > Each of those deploy hashes under 'Change' match commits in my Git repo on > > Github (and everywhere else). > > > > By rolling back to say v208 I know I'm going to end up with 19b486d, or am I > > missing something obvious here? > > > > N > > > > > > Neil > > > > On Monday, 23 April 2012 at 02:08, david ignacio wrote: > > > > Hey- > > > > So one thing that has got me about heroku is that there isn't > > necessarily a good link between the git repo and heroku releases. By > > this I mean that it isn't entirely obvious what is deployed and > > running at the moment. There are two current tools we have: > > * the heroku remote in the git repo > > * heroku releases > > > > This gives me the current release and what is working right now, but > > nothing more. If I deploy something broken, there isn't a clear way > > to find what I'd be rolling back to. The hashes displayed in heroku > > releases are of the compiled slugs. > > > > I have gone through a few back and forths as to what would be a good > > way to fill this gap. I realized that you'd really need two different > > scripts since releases are created in multiple places, one in the > > heroku cli and one in git. The config/addon changes trigger a new > > release to be created, but I think that those changes are well > > documented in heroku releases. It was the git-push triggered releases > > that I wanted to track. > > > > This led me to write: https://github.com/deignacio/gthr > > > > What I'm wondering from you guys is: > > * is there any other way in heroku that I can get the information I'm > > scraping so that I'm not just scraping stderr of git push? > > * am I thinking about this problem in the right way that this > > solution seems okay? > > * are there any other precedents that I didn't find in my sanity > > check google search? > > * assuming that the previous questions are positive, can anyone think > > of any other things they'd want? > > > > Thanks for your input > > Dave > > > > -- > > You received this message because you are subscribed to the Google > > Groups "Heroku" group. > > > > To unsubscribe from this group, send email to > > heroku+unsubscr...@googlegroups.com > > (mailto:heroku+unsubscr...@googlegroups.com) > > For more options, visit this group at > > http://groups.google.com/group/heroku?hl=en_US?hl=en > > > > > > -- > > You received this message because you are subscribed to the Google > > Groups "Heroku" group. > > > > To unsubscribe from this group, send email to > > heroku+unsubscr...@googlegroups.com > > (mailto:heroku+unsubscr...@googlegroups.com) > > For more options, visit this group at > > http://groups.google.com/group/heroku?hl=en_US?hl
Re: git tagging heroku releases
Well that's embarrassing. Looks like when I found the need for this, I had several issues in my repo/app running in concert. This made me think that when the hashes listed in `heroku releases` differed from both `git log heroku/master` and `git log master` that I was perhaps seeing an alternate hash generated by the slug compilation. Don't mind me I guess, at least I only spent a day or so on this script, although I think that perhaps then converting the idea into a heroku cli plugin that just took the versions in releases and created the tags as scraped could still have value? Thoughts? On Mon, Apr 23, 2012 at 09:10, Neil Middleton wrote: > You've lost me a little here. `heroku releases` gives you all the deployed > git versions and other changes. For instance: > > Rel Change By When > -- -- -- > v214 Deploy 5f3f619 neil.middle...@gmail.com 2012-04-18 > 17:28:41 +0100 > v213 Deploy b71ce95 neil.middle...@gmail.com 2012-04-12 > 15:04:45 +0100 > v212 Deploy d27f151 neil.middle...@gmail.com 2012-04-12 > 13:20:53 +0100 > v211 Deploy 6b81eef neil.middle...@gmail.com 2012-04-12 > 12:59:28 +0100 > v210 Config add FACEBOOK_APP_SECR.. neil.middle...@gmail.com 2012-04-12 > 12:56:11 +0100 > v209 Deploy 2f54f24 neil.middle...@gmail.com 2012-04-12 > 11:43:28 +0100 > v208 Deploy 19b486d neil.middle...@gmail.com 2012-04-12 > 11:36:34 +0100 > v207 Deploy efdd6ef neil.middle...@gmail.com 2012-04-12 > 11:22:40 +0100 > > Each of those deploy hashes under 'Change' match commits in my Git repo on > Github (and everywhere else). > > By rolling back to say v208 I know I'm going to end up with 19b486d, or am I > missing something obvious here? > > N > > > Neil > > On Monday, 23 April 2012 at 02:08, david ignacio wrote: > > Hey- > > So one thing that has got me about heroku is that there isn't > necessarily a good link between the git repo and heroku releases. By > this I mean that it isn't entirely obvious what is deployed and > running at the moment. There are two current tools we have: > * the heroku remote in the git repo > * heroku releases > > This gives me the current release and what is working right now, but > nothing more. If I deploy something broken, there isn't a clear way > to find what I'd be rolling back to. The hashes displayed in heroku > releases are of the compiled slugs. > > I have gone through a few back and forths as to what would be a good > way to fill this gap. I realized that you'd really need two different > scripts since releases are created in multiple places, one in the > heroku cli and one in git. The config/addon changes trigger a new > release to be created, but I think that those changes are well > documented in heroku releases. It was the git-push triggered releases > that I wanted to track. > > This led me to write: https://github.com/deignacio/gthr > > What I'm wondering from you guys is: > * is there any other way in heroku that I can get the information I'm > scraping so that I'm not just scraping stderr of git push? > * am I thinking about this problem in the right way that this > solution seems okay? > * are there any other precedents that I didn't find in my sanity > check google search? > * assuming that the previous questions are positive, can anyone think > of any other things they'd want? > > Thanks for your input > Dave > > -- > You received this message because you are subscribed to the Google > Groups "Heroku" group. > > 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_US?hl=en > > > -- > You received this message because you are subscribed to the Google > Groups "Heroku" group. > > 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_US?hl=en -- You received this message because you are subscribed to the Google Groups "Heroku" group. 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_US?hl=en
Re: heroku run console
I solved this by adding a console.rb file to my Sinatra App that loaded active record, my models and connected to the DB. I guess with great power comes responsibility... almost got this cedar and Ruby 1.9.3 thing going... perfect... On Apr 23, 10:26 am, Dave wrote: > Hi, > > In all my old Apps running Bamboo stack, I can just type heroku > console and have a nice interactive session that knows my database. > > When I do the same on cedar, and I use the heroku run console command, > I now get an IRB like prompt that has no idea my database exists? > > What's the secret sauce to getting at my models etc from the new style > console? > > Please? > > Thanks! -- You received this message because you are subscribed to the Google Groups "Heroku" group. 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_US?hl=en
heroku run console
Hi, In all my old Apps running Bamboo stack, I can just type heroku console and have a nice interactive session that knows my database. When I do the same on cedar, and I use the heroku run console command, I now get an IRB like prompt that has no idea my database exists? What's the secret sauce to getting at my models etc from the new style console? Please? Thanks! -- You received this message because you are subscribed to the Google Groups "Heroku" group. 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_US?hl=en
Re: ruby 1.9.3, Sinatra and Yaml problems
Hi, Seems to be solved. Heroku rewrites the config/database.yml and so whatever it does there does not compile to nice YAML. To get around that problem I changed my configure pattern in Sinatra to read the DATABASE_URL to setup my Active Record connection, bypassing the process I was so used to of reading the config/database.yml and I am back in business. Awkward moment sure, but whatever. I am kinda scared of using YAML now in my 1.9.3 cedar stack.. but we'll see.. maybe that actually does work... too.. On Apr 22, 2:30 pm, Dave wrote: > Hi, > > Moved to cedar stack to try out 1.9.3-p125 and a very simple Sinatra > App. The attempt to read the config/database.yml file is always > failing as Psych complains about the YAML. > > I ran it through Yaml Lint and have no idea how something so simple > could be farking Psych. This is frustrating. The backtrace is > complaining about a non-existent line in the YAML file too.. I have a > feeling this is some sort of heroku issue. > > Does anyone have any experience getting a simple 1.9.3 Sinatra App to > work with Psych properly??? -- You received this message because you are subscribed to the Google Groups "Heroku" group. 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_US?hl=en
Re: git tagging heroku releases
You've lost me a little here. `heroku releases` gives you all the deployed git versions and other changes. For instance: Rel Change ByWhen -- ---- v214 Deploy 5f3f619 neil.middle...@gmail.com2012-04-18 17:28:41 +0100 v213 Deploy b71ce95 neil.middle...@gmail.com2012-04-12 15:04:45 +0100 v212 Deploy d27f151 neil.middle...@gmail.com2012-04-12 13:20:53 +0100 v211 Deploy 6b81eef neil.middle...@gmail.com2012-04-12 12:59:28 +0100 v210 Config add FACEBOOK_APP_SECR.. neil.middle...@gmail.com2012-04-12 12:56:11 +0100 v209 Deploy 2f54f24 neil.middle...@gmail.com2012-04-12 11:43:28 +0100 v208 Deploy 19b486d neil.middle...@gmail.com2012-04-12 11:36:34 +0100 v207 Deploy efdd6ef neil.middle...@gmail.com2012-04-12 11:22:40 +0100 Each of those deploy hashes under 'Change' match commits in my Git repo on Github (and everywhere else). By rolling back to say v208 I know I'm going to end up with 19b486d, or am I missing something obvious here? N Neil On Monday, 23 April 2012 at 02:08, david ignacio wrote: > Hey- > > So one thing that has got me about heroku is that there isn't > necessarily a good link between the git repo and heroku releases. By > this I mean that it isn't entirely obvious what is deployed and > running at the moment. There are two current tools we have: > * the heroku remote in the git repo > * heroku releases > > This gives me the current release and what is working right now, but > nothing more. If I deploy something broken, there isn't a clear way > to find what I'd be rolling back to. The hashes displayed in heroku > releases are of the compiled slugs. > > I have gone through a few back and forths as to what would be a good > way to fill this gap. I realized that you'd really need two different > scripts since releases are created in multiple places, one in the > heroku cli and one in git. The config/addon changes trigger a new > release to be created, but I think that those changes are well > documented in heroku releases. It was the git-push triggered releases > that I wanted to track. > > This led me to write: https://github.com/deignacio/gthr > > What I'm wondering from you guys is: > * is there any other way in heroku that I can get the information I'm > scraping so that I'm not just scraping stderr of git push? > * am I thinking about this problem in the right way that this > solution seems okay? > * are there any other precedents that I didn't find in my sanity > check google search? > * assuming that the previous questions are positive, can anyone think > of any other things they'd want? > > Thanks for your input > Dave > > -- > You received this message because you are subscribed to the Google > Groups "Heroku" group. > > To unsubscribe from this group, send email to > heroku+unsubscr...@googlegroups.com > (mailto:heroku+unsubscr...@googlegroups.com) > For more options, visit this group at > http://groups.google.com/group/heroku?hl=en_US?hl=en > > -- You received this message because you are subscribed to the Google Groups "Heroku" group. 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_US?hl=en
Re: Renaming the Hosting URL for a Facebook App
Hi Richard, How can I change it? As shown in my 2nd image above, the only option given is to remove it. No option to edit/change. Is that setting in somewhere I'm overlooking? Thanks for the response. On Apr 21, 2:36 am, Richard Schneeman wrote: > You need to change your hosting urlhttp://stark-river-7862.herokuapp.comno > longer exists > > -- > Richard Schneemanhttp://heroku.com > > @schneems (http://twitter.com/schneems) > > > > > > > > On Friday, April 20, 2012 at 12:44 PM, nK0de wrote: > > I just started developing a Facebook App. I'm having trouble understanding > > some things working with Heroku, the free hosting platform for the apps. > > > So I created the App on Facebook. And from Heroku, I renamed the App. > > > And from Facebook under App on Facebook, I changed Canvas URL and Secure > > Canvas URL accordingly. But the Hosting URL still has the old URL which was > > given when I created the app. The only option given is to remove it. How > > can I edit this and give the new URL? > > > When I navigate to my app using the Canvas URL which is given there, it > > shows me this error page. > > > What am I missing here? What am I supposed to do now? Any guidance would be > > greatly appreciated as I'm really confused with this. > > Thank you. > > > -- > > You received this message because you are subscribed to the Google > > Groups "Heroku" group. > > > To unsubscribe from this group, send email to > > heroku+unsubscr...@googlegroups.com > > (mailto:heroku+unsubscr...@googlegroups.com) > > For more options, visit this group at > >http://groups.google.com/group/heroku?hl=en_US?hl=en -- You received this message because you are subscribed to the Google Groups "Heroku" group. 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_US?hl=en
RoutingError
I have deployed my rails app to heroku, then, I got an error:
The page you were looking for doesn't exist.
You may have mistyped the address or the page may have moved.
but, it works perfect locally at development mode, it seems there is
configuration error between `devise` and `routing-filter` gem
if I visit: `http://dcaclab.herokuapp.com`
my app will routed to: `http://dcaclab.herokuapp.com/en/users/sign_in`
so, why devise worked fine with routing-filter in development mode, but not
in production ?
any idea please ?
The home controller:
class HomeController < ApplicationController
def welcome
end
def set_lang
locale = params[:id]
I18n.locale = locale
raise 'unsupported locale' unless ['ar', 'en' ].include?(locale)
redirect_to :back
end
end
Here is my routes.rb:
devise_for :users
resources :experiments
Rails.application.routes.draw do
filter :locale, :pagination, :uuid
end
match 'lang' => 'home#set_lang'
root :to => 'home#welcome'
2012-04-21T13:01:31+00:00 app[web.1]: Started GET "/en/users/sign_in"
for 94.249.67.204 at 2012-04-21 13:01:31 +
2012-04-21T13:01:31+00:00 app[web.1]: ActionController::RoutingError
(No route matches {:controller=>"devise/home", :action=>"set_lang",
:id=>"ar"}):
2012-04-21T13:01:31+00:00 app[web.1]:
2012-04-21T13:01:31+00:00 app[web.1]: Parameters: {"locale"=>"en"}
2012-04-21T13:01:31+00:00 app[web.1]: Processing by
Devise::SessionsController#new as HTML
2012-04-21T13:01:31+00:00 app[web.1]: Rendered
vendor/bundle/ruby/1.9.1/gems/devise-2.0.4/app/views/devise/_links.erb
(0.4ms)
2012-04-21T13:01:31+00:00 app[web.1]:
app/views/layouts/application.html.haml:17:in
`_app_views_layouts_application_html_haml___1664922202454615355_30206680'
2012-04-21T13:01:31+00:00 app[web.1]:
2012-04-21T13:01:31+00:00 app[web.1]:
2012-04-21T13:01:31+00:00 app[web.1]: Completed 500 Internal Server
Error in 6ms
2012-04-21T13:01:31+00:00 app[web.1]: Rendered
vendor/bundle/ruby/1.9.1/gems/devise-2.0.4/app/views/devise/sessions/new.html.erb
within layouts/application (3.2ms)
2012-04-21T13:01:31+00:00 heroku[router]: GET
dcaclab.herokuapp.com/en/users/sign_in dyno=web.1 queue=0 wait=0ms
service=14ms status=404 bytes=728
--
You received this message because you are subscribed to the Google
Groups "Heroku" group.
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_US?hl=en
git tagging heroku releases
Hey- So one thing that has got me about heroku is that there isn't necessarily a good link between the git repo and heroku releases. By this I mean that it isn't entirely obvious what is deployed and running at the moment. There are two current tools we have: * the heroku remote in the git repo * heroku releases This gives me the current release and what is working right now, but nothing more. If I deploy something broken, there isn't a clear way to find what I'd be rolling back to. The hashes displayed in heroku releases are of the compiled slugs. I have gone through a few back and forths as to what would be a good way to fill this gap. I realized that you'd really need two different scripts since releases are created in multiple places, one in the heroku cli and one in git. The config/addon changes trigger a new release to be created, but I think that those changes are well documented in heroku releases. It was the git-push triggered releases that I wanted to track. This led me to write: https://github.com/deignacio/gthr What I'm wondering from you guys is: * is there any other way in heroku that I can get the information I'm scraping so that I'm not just scraping stderr of git push? * am I thinking about this problem in the right way that this solution seems okay? * are there any other precedents that I didn't find in my sanity check google search? * assuming that the previous questions are positive, can anyone think of any other things they'd want? Thanks for your input Dave -- You received this message because you are subscribed to the Google Groups "Heroku" group. 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_US?hl=en
