Re: Upload from Rails app to S3 bucket upload failing with No such file or directory
You still need to use the S3 API to manipulate your buckets.
As Richard mentioned, Paperclip is a good tool for attaching image
attachments to Ruby/Rails model classes.
If you want to post images to S3 without and associated model, take a
look at the official amazon web services sdk for Ruby:
http://aws.amazon.com/articles/8621639827664165
-Jesse
On Mar 30, 1:30 pm, Anil Punjabi an...@hotmail.com wrote:
Hello,
I am trying to upload a file from a HTML form, to a Rails app to finally go
to S3 but I keep getting this No such file or directory error.
My S3 policy is very generic with permissions for anonymous
uploads/downloads.
Any suggestions would be greatly appreciated.
Here's a snippet of the rails code that receives the web form and posts to
S3.
def uploadpic
uploaded_io = params[:pic]
File.open(('http://s3.amazonaws.com/heroku-rails-bucket/'+
uploaded_io.original_filename), 'wb') do |file|
file.write(uploaded_io.read)
end
end
Here's the generic web form code: /uploadfile.html
html
head
title/title
/head
body
form method=post action=/uploadpic enctype=multipart/form-data
input type=hidden name=id value=12345 /
input type=file name=pic /
input type=submit /
/form
/body
/html
I've added: require 'open-uri' at the beginning of this file and in the
Gemfile (as per another Stackoverflow post).
Is there any other gem that will make the S3 import work correctly?
Here's the heroku log file:
GET clearslide.heroku.com/fileupload.html dyno=web.1 queue=0 wait=0ms
service=7423ms status=200 bytes=371
2012-03-30T18:03:45+00:00 app[web.1]: cache: [GET /fileupload.html] miss
2012-03-30T18:03:45+00:00 heroku[nginx]: 67.164.91.9 - -
[30/Mar/2012:18:03:45 +] GET /fileupload.html HTTP/1.1 200 371 -
Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7_3) AppleWebKit/535.11 (KHTML,
like Gecko) Chrome/17.0.963.83 Safari/535.11 clearslide.heroku.com
2012-03-30T18:03:57+00:00 app[web.1]:
2012-03-30T18:03:57+00:00 app[web.1]: Started POST /uploadpic for
67.164.91.9 at 2012-03-30 11:03:57 -0700
2012-03-30T18:03:57+00:00 app[web.1]:
2012-03-30T18:03:57+00:00 app[web.1]: Parameters: {id=12345,
pic=#ActionDispatch::Http::UploadedFile:0x0002d00460
@original_filename=Kabam3.png, @content_type=image/png,
@headers=Content-Disposition: form-data; name=\pic\;
filename=\Kabam3.png\\r\nContent-Type: image/png\r\n,
@tempfile=#File:/app/tmp/RackMultipart20120330-1-1k697hr}
2012-03-30T18:03:57+00:00 app[web.1]: Processing by
MessagesController#uploadpic as HTML
2012-03-30T18:03:57+00:00 app[web.1]: Completed 500 Internal Server Error
in 1ms
2012-03-30T18:03:57+00:00 app[web.1]: *Errno::ENOENT (No such file or
directory -http://s3.amazonaws.com/heroku-rails-bucket/Kabam3.png):*
2012-03-30T18:03:57+00:00 app[web.1]:
2012-03-30T18:03:57+00:00 app[web.1]:
app/controllers/messages_controller.rb:89:in `uploadpic'
--
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: uninitialized constant Rake::DSL
On the cedar stack i think you need 'run'
http://devcenter.heroku.com/articles/rails3#rake
heroku run rake db:migrate
Similar to running
bundle exec rake db:migrate
On Jul 8, 4:02 pm, Francois fhar...@gmail.com wrote:
I have rake 0.9.2 on my local machine. When i type rake --version, I
get:
rake, version 0.9.2
and my rails 3.0.9 app does not specify a version of rake in the
Gemfile. When I do bundle list |grep rake
I see:
* rake (0.9.2)
Anyway, rake seems to work just fine on my local machine with a rails
3.0.9 app. However, when I push that app to heroku I run into the
following error whenever I try to do heroku rake
rake aborted!
uninitialized constant Rake::DSL
/app/.bundle/gems/ruby/1.9.1/gems/rake-0.9.2/lib/rake/tasklib.rb:8:in
`class:TaskLib'
Anyone know why rake 0.9.2 fails on heroku but works just fine on my
local machine?
- Thanks
Francois
On Jun 21, 10:21 am, Alex Chaffee ale...@gmail.com wrote:
YMMV, but I'm pretty sure Rake 0.9.2 fixes this.
Another solution is to add the following to your Rakefile, right after
require 'rake'
class Rails::Application
includeRake::DSL
end
(from memory; please let me know if it doesn't work and I'll look it
up for you)
On Jun 17, 7:01 pm, Daniel Myasnikov myasnikovdan...@gmail.com
wrote:
Hey
I had the same issue, and the whole yesterday to solve it.
First of all, if you are using Rake 0.8.7 and put require 'rake/
dsl_definition' it won't work for you. This feature was introduced
for Rake 0.9.x.
I strongly recommend to use Rake 0.8.7
and get rid out of everything that you put for rake 0.9.x, such as
'includeRake:dsl' and extend Rake::FileUtilsExt
So your RakeFile file should look like:
require File.expand_path('../config/application', __FILE__)
require 'rake'
MyApplicationName::Application.load_tasks
2. Secondly check if you have installed Rake 0.9.x and remove it from
your computer and use Rake 0.8.7, which you have to install before
using
3. Use gem rake, 0.8.7 in your GemFile just after source 'http://
rubygems.org'
4. Make sure your gem for rails is '3.0.9'
5. Some said that this gem also helped them gem 'sqlite3',
'1.3.3', :group = :development
Also don't forget about debugging your Heroku application using
'heroku logs'
Daniel Myasnikov
On Jun 18, 11:43 am, Karl threadh...@gmail.com wrote:
Using Rails 3.0.9 (3.0.7 too), which load rake 0.9.2 with bamboo-
mri-1.9.2, causes:
$ heroku rake db:migrate
rake aborted!
uninitializedconstantRake::DSL
/app/.bundle/gems/ruby/1.9.1/gems/rake-0.9.2/lib/rake/tasklib.rb:8:in
`class:TaskLib'
/app/.bundle/gems/ruby/1.9.1/gems/rake-0.9.2/lib/rake/tasklib.rb:6:in
`module:Rake'
/app/.bundle/gems/ruby/1.9.1/gems/rake-0.9.2/lib/rake/tasklib.rb:3:in
`top (required)'
/app/.bundle/gems/ruby/1.9.1/gems/rdoc-3.6.1/lib/rdoc/task.rb:37:in
`top (required)'
/app/.bundle/gems/ruby/1.9.1/gems/railties-3.0.9/lib/rails/tasks/
documentation.rake:2:in `top (required)'
/app/.bundle/gems/ruby/1.9.1/gems/railties-3.0.9/lib/rails/tasks.rb:
15:in `block in top (required)'
/app/.bundle/gems/ruby/1.9.1/gems/railties-3.0.9/lib/rails/tasks.rb:
6:in `each'
/app/.bundle/gems/ruby/1.9.1/gems/railties-3.0.9/lib/rails/tasks.rb:
6:in `top (required)'
/app/.bundle/gems/ruby/1.9.1/gems/railties-3.0.9/lib/rails/
application.rb:215:in `initialize_tasks'
/app/.bundle/gems/ruby/1.9.1/gems/railties-3.0.9/lib/rails/
application.rb:139:in `load_tasks'
/app/.bundle/gems/ruby/1.9.1/gems/railties-3.0.9/lib/rails/
application.rb:77:in `method_missing'
/app/Rakefile:7:in `top (required)'
/usr/ruby1.9.2/lib/ruby/1.9.1/rake.rb:2373:in `load'
/usr/ruby1.9.2/lib/ruby/1.9.1/rake.rb:2373:in `raw_load_rakefile'
/usr/ruby1.9.2/lib/ruby/1.9.1/rake.rb:2007:in `block in load_rakefile'
/usr/ruby1.9.2/lib/ruby/1.9.1/rake.rb:2058:in
`standard_exception_handling'
/usr/ruby1.9.2/lib/ruby/1.9.1/rake.rb:2006:in `load_rakefile'
/usr/ruby1.9.2/lib/ruby/1.9.1/rake.rb:1991:in `run'
/usr/ruby1.9.2/bin/rake:31:in `main'
(in /app)
I had to add, before require 'rake':
# Rakefile
require 'rake/dsl_definition'
But I don't get this on my development machine. Why?
--
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: Could an admin add a subject prefix to this list, like [heroku]
I use the Abridged Email (Once per day... setting 1 email a day from the group with the subject Abridged summary of heroku@googlegroups.com - x Messages in x Topics this works great for me, I guess it comes down to personal preference? On May 12, 1:49 am, Albert Chou hotfusion...@gmail.com wrote: I wish there was at least an option to get the subject line label, because it makes it much easier to distinguish list messages in the iPhone's Mail.app. Al -- Sent from an iPhone -- please excuse any autocorrection-induced wording oddities. On May 11, 2011, at 3:39 PM, Miles Smith wed...@gmail.com wrote: I think what Richard is saying is there is no reason to force a change on every user, when a less intrusive (filters) method exists. On May 11, 2011 3:36 PM, Travis Reeder tree...@gmail.com wrote: I get the filter thing can work, but how about not making everyone on the list create a filter when one person can do it once for the entire list. I don't think the reasons you present are very compelling reasons to not do it. Subject line noise is most welcome when it tells me what list it's from (like your labels) and how does it prevent you from identifying old messages visually? Not meaning to start a big discussion here, just seems like an odd response to a request for something so common. On Wed, May 11, 2011 at 3:20 PM, Richard Conroy richard.con...@gmail.com wrote: There is usually good reason why lists don't prefix. Line noise on the subject line being one of them, also the availability of advanced e-mail clients that can do powerful filtering. For instance, in GMail, which both of you use, I can set a filter to label all my Heroku posts. Hence, subject prefixing becomes redundant, and also very irritating when you are trying to identify old messages visually. regards, Richard On Wed, May 11, 2011 at 11:07 PM, Miles Smith wed...@gmail.com wrote: I second this. On May 11, 2011 10:54 AM, Travis Reeder tree...@gmail.com wrote: So we can know what list it is without having to open the email. Cheers. -- 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. -- http://richardconroy.blogspot.com|http://twitter.com/RichardConroy -- 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 athttp://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: PDF Generation on Heroku
besides prawn you might want to look at pdfkit, it does html/css conversion to pdf, you don't have as much control over the rendered output as with prawn but for some scenarios it works great https://github.com/jdpace/PDFKit http://blog.mattgornick.com/using-pdfkit-on-heroku also you need to be careful, if your image/css references are http you can deadlock your dyno if you don't have multiple running - or you need to reference your resources using local file:/// during pdf generation http://jguimont.com/post/2627758108/pdfkit-and-its-middleware-on-heroku On Feb 25, 4:36 pm, Josh Coffman joshcoff...@gmail.com wrote: I've used Prawn/Prawnto to generate pdf's on heroku, which were then either downloaded or attached to an email. Worked well for me. On Fri, Feb 25, 2011 at 10:13 AM, kumari s kumari...@gmail.com wrote: http://www.PaisaLive.com/register.asp?2024379-5217218 On 2/25/11, John Beynon j...@beynon.org.uk wrote: We're faced with having to generate PDFs on Heroku - we've been looking at wickedPDF and taken a look at the new heroku addon DocRaptor. I'm curious with DocRaptor - with their Ruby example athttp://docraptor.com/examples(Rails tab) - where does Heroku's involvement end - is a dyno 'busy' throughout? For example a pdf link is clicked which is then passed over to DocRaptor via a post (consuming a Dyno) and then waits for the response to be generated and then streamed back to the same dyno which then sends the data to the client browser - so a dyno is essentially busy throughout this process from when the link is clicked, waiting for the response and then returning the data to the client browser? What we're looking at is being able to generate PDFs without consuming precious dynos - I've seen mentions of using DJ for background processing but we want the user to able to click a button which kicks of the PDF generation and shows them 'Generating' and then when the doc is ready send it to the client but I'm thinking that may need writing to tmp to then serve back? Any one done anything similar? Any ideas? John. -- 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.
Re: quick question re PostgreSQL and string case searching
not sure if this is what you are asking, but...
I usually do something like this for queries that I want to be case
insensitive
# force both to upper
:conditions = ['UPPER(email) = ?', params[:search][:email].upcase]
# use postgres ILIKE which is case insensitive
:conditions = ['email ILIKE ?', %#{params[:search][:email]}%]
that way I can leave the data alone
however this is not portable across all databases, there might be a
better way
- Jesse
On Feb 18, 11:32 am, Lille lille.pengu...@gmail.com wrote:
Hi,
I'm new to PostgreSQL and I've read in a few places that it may treat
string case sensitivity particularly when searching. Thus, I'm
wondering if I should consider scrubbing my string data any particular
way in advance of deployment on Heroku?
Lille
--
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: App is Crashing with a meaningless Error
I have a rails app that referenced aws-s3. last time I uploaded my code the gems were re-imported and I ended up with builder 3.0.0 (aws- s3 depends on builder); this caused a lot of other code to start failing. I had to specify builder -v 2.1.2, I am only bringing this up since I see errors in builder in your stacktrace, in my case it was a local gem not part of the heroku stack try to specify builder -v 2.1.2 in .gem or bundler? On Feb 12, 11:38 am, Jeffrey Aylesworth j...@aylesworth.ca wrote: I have a Sinatra app working on my local computer, but when I send it to heroku, it crashes. The error log says: 2011-02-12T11:36:50-08:00 app[web.1]: from /home/heroku_rack/ heroku.ru:18 2011-02-12T11:36:50-08:00 app[web.1]: from /usr/ruby1.8.7/lib/ruby/ gems/1.8/gems/rack-1.0.1/lib/rack/builder.rb:29:in `instance_eval' 2011-02-12T11:36:50-08:00 app[web.1]: from /usr/ruby1.8.7/lib/ruby/ gems/1.8/gems/rack-1.0.1/lib/rack/builder.rb:29:in `initialize' 2011-02-12T11:36:50-08:00 app[web.1]: from /home/heroku_rack/ heroku.ru:11:in `new' 2011-02-12T11:36:50-08:00 app[web.1]: from /home/heroku_rack/ heroku.ru:11 2011-02-12T11:36:50-08:00 app[web.1]: from /usr/ruby1.8.7/lib/ruby/ gems/1.8/gems/rack-1.0.1/lib/rack/builder.rb:29:in `instance_eval' 2011-02-12T11:36:50-08:00 app[web.1]: from /usr/ruby1.8.7/lib/ruby/ gems/1.8/gems/rack-1.0.1/lib/rack/builder.rb:29:in `initialize' 2011-02-12T11:36:50-08:00 app[web.1]: from /home/heroku_rack/ heroku.ru:1:in `new' 2011-02-12T11:36:50-08:00 app[web.1]: from /home/heroku_rack/ heroku.ru:1 2011-02-12T11:36:50-08:00 heroku[web.1]: State changed from starting to crashed 2011-02-12T11:36:55-08:00 heroku[router]: Error H10 (App crashed) - GET deep-ice-593.heroku.com/ dyno=none queue=0 wait=0ms service=0ms bytes=0 2011-02-12T11:36:55-08:00 heroku[router]: Error H10 (App crashed) - GET deep-ice-593.heroku.com/favicon.ico dyno=none queue=0 wait=0ms service=0ms bytes=0 2011-02-12T11:36:55-08:00 heroku[nginx]: GET /favicon.ico HTTP/1.1 | 24.57.83.182 | 3310 | http | 500 2011-02-12T11:36:55-08:00 heroku[nginx]: GET / HTTP/1.1 | 24.57.83.182 | 3310 | http | 500 2011-02-12T11:36:55-08:00 heroku[router]: Error H10 (App crashed) - GET deep-ice-593.heroku.com/favicon.ico dyno=none queue=0 wait=0ms service=0ms bytes=0 2011-02-12T11:36:55-08:00 heroku[nginx]: GET /favicon.ico HTTP/1.1 | 24.57.83.182 | 3310 | http | 500 2011-02-12T11:36:58-08:00 heroku[router]: Error H10 (App crashed) - GET deep-ice-593.heroku.com/ dyno=none queue=0 wait=0ms service=0ms bytes=0 2011-02-12T11:36:58-08:00 heroku[nginx]: GET / HTTP/1.1 | 24.57.83.182 | 3310 | http | 500 2011-02-12T11:36:58-08:00 heroku[router]: Error H10 (App crashed) - GET deep-ice-593.heroku.com/favicon.ico dyno=none queue=0 wait=0ms service=0ms bytes=0 2011-02-12T11:36:58-08:00 heroku[nginx]: GET /favicon.ico HTTP/1.1 | 24.57.83.182 | 3310 | http | 500 Which means nothing to me because it does not mention any of my own files, as far as I can see. Has anyone had this before, and know what might be causing the problem? Thanks. -- 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: Change to Heroku rake db:migrate output freaked me out
I think this has to do with the new logging going to STDOUT, I didn't see this until I upgraded to the new logging addon On Feb 9, 6:44 am, chris mcclellan...@gmail.com wrote: When I run rake db:migrate locally, I get all of the migrations listed out: chris@goldfish$ rake db:migrate (in /Users/cmcclelland/workspace/XXX) SQL (30.0ms) SHOW client_min_messages SQL (0.2ms) SET client_min_messages TO 'panic' SQL (0.3ms) SET standard_conforming_strings = on SQL (0.1ms) SET client_min_messages TO 'notice' SQL (94.2ms) SET time zone 'UTC' SQL (0.1ms) SHOW TIME ZONE SQL (45.1ms) SELECT schema_migrations.version FROM schema_migrations Migrating to CreateInitialTables (20100329164816) Migrating to AddManchesterAndWorcester (20100329180447) Migrating to MaxmindGeolocation (20100330200706) Migrating to CreateTransactions (20100401145908) Migrating to AddRoleMaskToUsers (20100407204815) Migrating to CreateCreditCards (20100413144222) Migrating to CreateDelayedJobs (20100414192906) Migrating to AddRedemptionInstructionsToDeals (20100416155743) Migrating to AddDefaultToCreditCards (20100416172408) ... So, I am seeing the same behavior as on heroku. -- 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.
Logging - STDOUT ignores log_level
just installed the logging addon
http://docs.heroku.com/logging
I am running a rails 2.2.2 app, maybe this occurs with other versions
as well
if you use
config.logger= Logger.new(STDOUT)
then you basically end up with debug output, request, sql, partials
rendered
seems like overkill for production?
- I did not notice any difference when adjusting the config.level ?
config.log_level = :info
the behavior was the same on both localhost and deployed to heroku
if you don't use the STDOUT, then you end up with no app logging, just
the nginx
2011-02-05T13:04:40-08:00 heroku[nginx]: GET /login?testing4 HTTP/1.1
| 10.116.147.148 | 3265 | https | 200
I like the standard rails :info level logging; for each request -
includes the parameters but not much else
Processing SessionsController#new (for 127.0.0.1 at 2011-02-05
13:07:30) [GET]
Parameters: {action=new, testing5=nil,
controller=sessions}
Rendering template within layouts/application_full_width
Rendering sessions/new
Completed in 79ms (View: 18, DB: 6) | 200 OK [http://localhost/login?
testing5]
maybe this is an issue related to older versions of rails only?
has anyone else noticed this behavior or know of a workaround?
for now I am just removing the addon
Thanks,
- Jesse
--
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: 1 hour inactivity idling and http caching
I set up http://pingdom.com/ to monitor my site, you can set it up to hit it every 5 minutes this will keep it 'up and running' on heroku as well as inform you of down time you get 1 url for free not sure if this will solve your problem as you have only 1 cached page, but something to consider? - Jesse On Jan 7, 3:44 am, Martin Petrov m.p.pet...@gmail.com wrote: Well, you must be right. I don't have a very good understanding of how it works. Thank you Smith! On Jan 7, 1:08 pm, Steve Smith st...@scsworld.co.uk wrote: Perhaps as the routing engine shuts down the app it also empties varnish. That would actually seem quite likely? On 7 Jan 2011, at 11:03, Martin Petrov wrote: If this is the case then I should remove http caching in order to prevent the app from shutting down as much as possible. But... why requesting a cached page starts the app if the request is never handled by the app? On Jan 7, 11:18 am, Steve Smith st...@scsworld.co.uk wrote: I'm not an expert on this so I would double check, however I think this is all the case, If you only have one dyno then the app will shutdown when there are no requests for a certain time period. I believe this isn't the case once you have more than one dyno but in my experience at that point you have enough concurrent connections to keep things alive anyway. If you are caching the page it will be stored in varnish so the request will never be handed out to the app and will therefore allow the app to shutdown. Steve On 7 Jan 2011, at 09:02, Martin Petrov wrote: Hi, Looking at my logs I see that if my application is not used for 1 hour its state is changed from up to down. Next time a request comes it takes several seconds to start again. Does requesting an http cached page keeps the application alive? My app has only one page, which is http cached. -- 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. -- 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. -- 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 o...@heroku.com 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 thoms...@gmail.com 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.comheroku%2bunsubscr...@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.comheroku%2bunsubscr...@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.
Vendored gems specified in Gemfile with :path not deploying
Hi All, I recently committed a change to my site which involved bumping a version number on a gem in my Gemfile. When I try to deploy to heroku I get the following errors: You have added to the Gemfile: * source: source at /disk1/tmp/build_3155_23685892989800/vendor/ gems/wand * source: source at /disk1/tmp/build_3155_23685892989800/vendor/ gems/joint You have deleted from the Gemfile: * source: source at vendor/gems/joint * source: source at vendor/gems/wand You have changed in the Gemfile: * joint from `source at /disk1/tmp/build_3155_23685892989800/ vendor/gems/joint` to `no specified source` * wand from `source at /disk1/tmp/build_3155_23685892989800/ vendor/gems/wand` to `no specified source` joint and wand are specified in my gemfile using the :path option like so: gem 'joint',:path = File.join( File.dirname(__FILE__), '/ vendor/gems/joint' ) gem 'wand', :path = File.join( File.dirname(__FILE__), '/vendor/gems/ wand' ) Neither of these two lines nor the files in vendor have changed since my last successful deploy. If I remove the Gemfile.lock from my repository and then deploy Heroku runs builder for me and installs everything just fine. At some point lock files will be required though and I need to figure out how to resolve this. Has anyone else run in to this issue? I'm running Rails 2.3.8 on bamboo-mri-1.9.1. Thanks, -Jesse -- 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.
where is the support?
My site is stuck in maintenance mode I submitted a ticket to Heroku 18 hours ago - it is still unassigned I don't see any issues listed at http://status.heroku.com/ Heroku support where are you? - Jesse -- 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: where is the support?
not a browser cache issue; tried from multiple machines with multiple browsers and also using curl - Thanks anyway On Aug 25, 1:20 pm, Jeff Schmitz jeffrey.j.schm...@gmail.com wrote: Hate to ask the obvious Did you clear your browser cache? -- 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: where is the support?
David, I finally got a chance to reply on the support ticket; was away from computer until now tried both suggested options but not working Thank you for reply On Aug 25, 1:11 pm, David Dollar da...@heroku.com wrote: Your slug compile might have gotten stuck. Try pushing another trivial commit or changing a config var to trigger another compile. Cheers, David On Aug 25, 2010, at 3:57 PM, Jesse wrote: I have executed heroku restart heroku maintenace:off multiple times both run without failure I can even heroku console and execute commands at that level, it is just that all web requests hit the maintenance page nothing is written to the logs, seems like maybe some type of caching issue on the Heroku web servers? doesn't seem like anything that can be solved without intervention from heroku? On Aug 25, 12:48 pm, Daniel Spangenberg daniel.spangenb...@googlemail.com wrote: Have you tried to restart your app or push again oder change an config variable? Daniel Am 25.08.2010 um 21:41 schrieb Jesse: My site is stuck in maintenance mode I submitted a ticket to Heroku 18 hours ago - it is still unassigned I don't see any issues listed athttp://status.heroku.com/ Heroku support where are you? - Jesse -- 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. -- 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. -- 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: Force https?
I guess you would say this is the 'manual' way to do it :) I use ssl_requirement gem .gems file specifies ssl_requirement in app/controllers/application.rb (still on rails 2.2.2) ... require 'ssl_requirement' class ApplicationController ActionController::Base helper :all # include all helpers, all the time # force ssl for all requests in production and staging include SslRequirement unless (Rails.env.development? or Rails.env.test?) ... in any controllers that do not need ssl override the ssl_required? method def ssl_required? return false end On Jul 30, 1:52 pm, Phil phil.a.mcdonn...@gmail.com wrote: Does anyone know how I can force all connections to myapp.heroku.com to run over https instead of http? I think there are ways to configure this manually, but I'm wondering if it's possible with Heroku. I have the ssl connection enabled for my app, but I want to make sure people typing inhttp://myapp.heroku.comget redirected to https. Thanks, Phil -- 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.
Please help on rack-rewrite
j...@home ~/work/voteforpoetry $ heroku config
SITE_URL = voteforpoetry.com
j...@home ~/work/voteforpoetry $ heroku domains
Domain names for voteforpoetry.heroku.com:
voteforpoetry.com
www.voteforpoetry.com
http://github.com/jtrupiano/rack-rewrite/issues/#issue/7
## Gemfile
gem 'rack-rewrite', '1.0.0'
## config/environments/production.rb (fails)
config.gem 'rack-rewrite', '1.0.0'
require 'rack/rewrite'
config.middleware.insert_before(Rack::Lock, Rack::Rewrite) do
r301 %r{.*}, http://#{ENV['SITE_URL']}$, :if = Proc.new { |
rack_env|
rack_env['SERVER_NAME'] != ENV['SITE_URL']
}
end
--
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: sharing app on multiple machines
Assembla also has Free Git and SVN hosting - http://www.assembla.com/plans A great resource for learning git is - the Pro Git book - I happen to own the book, but they have also made the entire thing available online for Free! (which is totally awesome) - http://progit.org/book/ On May 11, 12:07 pm, dan mr.dan.ma...@gmail.com wrote: i was originally going to use github when someone suggested gitosis, since its free it felt a little funny having to pay for something that im really only using for me, not a team or anything ... -- 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: Foreign Keys
I believe you are right db:push and db:pull don't touch FKs; I also agree that FK are a good thing. If you create a migration file that generates your FKs it will create them when you run rake db:migrate on your heroku application as far as backups go the other option is the single bundle add on I found this gist (i think maybe someone posted it here before?) it downloads the bundle and then uploads it to s3 for back up https://gist.github.com/1d2853b0a349768a8884 (some nice stuff, learned a few things from this code) the only problem with the bundles is all of your code comes with it and most of us probably have that in our own source control system already; I branched that gist above to extract the pgdump.sql file, it needs some additional cleanup; right now the s3 upload is commented out and needs a task to move the pgdump.sql https://gist.github.com/ccfce988fdbc172febc3 The pgdump.sql file from the bundle will contain the FK Alter statements (if the FKs exists on the heroku db) Usually when I use the db:pull; first I'll run rake db:drop and rake db:create - which will DROP my local development database then run heroku db:pull and then run a script to apply all FKs; getting the pgdump file from the bundle is probably going to be better in most cases. -- 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.
daily cron scheduled time?
I am adding the daily cron addon to my app it seems to schedule the daily cron to run each day, but at the time of day the addon was enabled is there a way to set a specific time of day? enable the addon at 2010-03-17 09:32 PDT heroku addons:add cron:daily check the scheduling heroku info ... Stack: bamboo-ree-1.8.7 Data size: ... tables Next cron: 2010-03-18 09:32 PDT (scheduled) Last cron: 2010-03-16 17:54 PDT (finished) Addons: Daily Cron, New Rel... ideally I would like to run my cron job at say 10:00pm my plan right now is to be on my computer at 10:00pm, remove the addon and then add it back, is there an easier way? http://docs.heroku.com/cron Thanks, - Jesse -- 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.
Rails 2.1
How do I upgrade to Rails 2.1 on my Heroku app? Thanks! --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/heroku?hl=en -~--~~~~--~~--~--~---
