We live in the age of remote resources. It's pretty rare to store uploaded files on the same machine as your server process.these days is almost completely remote, and for very good reasons.
Using file storage services like S3 is awesome, but not having your files accessible locally can complicate the performance of file-oriented operations. In these cases, use Ruby's Tempfile to create local files that live just long enough to satisfy your processing needs.
…to the output script wrapped in an appropriate .parse call. CarrierWave-uploaded S3 files proved pretty difficult to work with in this approach. Getting a path or url is simple enough, but when you create an object on the other side of your Rails migration that also has a CarrierWave uploader, it expects a file. In our case, the S3 url's included quickly expiring tokens that would be invalid by the time our deployment would complete. With destructive migrations, we decided this was …
I'm playing around with Nanoc - a static site generator. Basically, nanoc allows you you write your blog posts offline, and then generates your entire site in raw . This allows you to host a site with out needing a database. In other words, it's dead quick. You can also forgo a web server, and just host your site from S3 if you want.
That's pretty cool, but it seems to be a little more work then I really want. Since know my way around git and other command line tools, I decided that I could do better.
All theseresources - EC2 instances, S3 buckets - are distributed across a few different AWS accounts. Before , there was no way to have …
Thank you to Amazon for S3.
Thank you to Dropbox for hosting large design assets and important files.
Thank you to Hoefler & Frere-Jones for their typography, which we're using on this very blog.
Thank you to Typekit for serving up fonts for us and our clients.
…they're venturing into terra incognita — just think of every smartphone that came before the Galaxy S3 — they need help. As Theput it in their review of the :
As with industrial design, software engineering isn't among's strengths, and the results on the Gear are a painful mix of unreliability and inadequacy.
Rails Assets - between and Bower to make it easy to pull Bower components into projects.
Why You Should Never Use MongoDB - A look based on experience with the project.
Ruby on Rails' Inside: - A look at some Rails internals. and Rack
Duplicity + S3: easy, cheap, encrypted, automated full-disk backups for your servers - Definitely worth thinking about.
On the storage side, Amazon has consistently lowered the prices of S3 over the past few years. The current price for the US-west-2 region is only $ 0.09 per GB per month.
Bandwidth costs have also lowered tremendously. Many hosting providers these days allow more than 1 TB of traffic per month per server.
This makes Duplicity and S3 the perfect combination for backing up my servers. Using encryption …
…EBS-Optimized IO throughput of your c1.xlarge cluster? How about the size limit of an S3 object on a single PUT? awsnow.info is the answer to all of your AWS-resource metadata questions. Interested in integrating awsnow.info with your application? You're in luck. There's now a REST API , as well!
Note: These are default soft limits and will vary by account.
2) Tame your S3 buckets
Delete an entire S3 bucket with a singlecommand:
(cross posted from the HPCloud Blog . With 75% more typos!)
One of the most basic problems with systems that need to persist data, is making sure that you can recover those systems in the case of a critical error. I've used and written backup systems for more time then I'd like to admit ( for example ). With the advent of cloud storage systems such as S3, moving your data offsite has become much easier, and much easier to recover data from your offsite storage system.