StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
8541877
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2011-12-17T01:10:43.537
FavoriteCount
0
LastActivityDate
2011-12-17T01:10:43.537
LastEditDate
LastEditorUserId
0
OwnerUserId
293898
ParentId
8539822
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
A good pattern to use is to upload the file directly to Amazon s3 and then add it into your app with Carrierwave from that location. If you store the file in a temporary bucket/location on s3, you can then have carrierwave effectively process then move it. After it is directly uploaded to s3, and assuming you have available the bucket and address you uploaded it to, you can use code like this to have Carrierwave pick it up, process it, and "move" it: <pre><code> def add_file_from_URL(bucket, object_address) s3 = AWS::S3::new bucket = s3.buckets[bucket] object = bucket.objects[object_address] object_url = object.url_for(:read, :expires => 60*60, :secure => true) #expires in 1 hour self.remote_attachment_url = object_url.to_s self.save object.delete() end </code></pre> This code would go in your model that has the file within it. I have left out the code to process (resize) the file, as you should be able to find that within the Carrierwave docs easily if you don't already have that part done. To keep track of meta data for the file I would suggest use a :before_save callback to store this information in fields along side the file. You would have a method like this: <pre><code> private def update_file_attributes if file.present? self.file_content_type = attachment.file.content_type self.file_size = attachment.file.size end end </code></pre> In this example, I am saving the actual file size, but you could tweak this for dimensions instead. This goes in the model that you save the file in.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POImage manipulation Rails Carrierwave to Amazon S3
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USJoel Friedlaender
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POImage manipulation Rails Carrierwave to Amazon S3
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.