Daniel Grundel's List: Ruby on Rails

By the way, the warning message mentions performance degradation, but I have (on limited perusal) not really understood why aws prefers one calling convention or another, was performance specifically mentioned by the docs somewhere?

  

Sigh, as for bucket renames, the story is:

  

 

• Renaming a bucket: FFFFFFFUUUUUUUUUUUU

 

• Creating a lower-case bucket by the downcased name: FFFFFFFUUUUUUUUUUUU

 

• Deleting a bucket: FFFFFFFUUUUUUUUUUUU

 

Which means one has to change their buckets everywhere :P

 

 

 

 

  

 
<!-- /.avatar-bubble -->  
   
   
 
 
    geemus      commented     
 
  8 months ago 
 
   
 
 
 
@fdr I do not know why aws prefers one or the other per se (I don't really have any more insight into their internals than anybody else does). The docs from aws rarely if ever mention performance, I found this out from doing benchmarking and testing over time. If you write a script that does operations on two buckets, one with a dns-able name and one without, the results are pretty damning. Changing buckets is definitely a big pain in the butt, but it is also a pretty big performance difference (if I recall correctly, things were something like 3-4x faster with dns-able names).
 
 
 
 
  
 
<!-- /.avatar-bubble -->  
   

   

 

 

    pweldon      commented     

 

  8 months ago 

 

   

 

 

 

@fdr, @geemus the performance difference is most likely caused by the additional redirect for every request that happens when you use the generic end-point for non-dns names. Using virtual host style requests with dns names eliminates this redirect as aws has already pre-computed the redirect at the dns level. I think this page explains the basics:
 http://docs.amazonwebservices.com/AmazonS3/latest/dev/Redirects.html

@thiagobrandam (even if it is late) and everyone finding this in hope that it helps you getting nested resources working in active_admin:

ActiveAdmin.register Post do   index do     column :actions do |post|       link_to "Posts", [:admin, post, :comments]     end   end end  ActiveAdmin.register Comments do   belongs_to :post end 

This gives you a link to your nested resource (link_to) and registers the resource as nested (belongs_to)

Finally found the problem.

form do |f|

needs to become:

form(:html => { :multipart => true }) do |f|

1.4 Supported Types

 

Active Record supports the following database column types:

 
 
• :binary
 
• :boolean
 
• :date
 
• :datetime
 
• :decimal
 
• :float
 
• :integer
 
• :primary_key
 
• :string
 
• :text
 
• :time
 
• :timestamp