With my move to Heroku I felt bad about having Heroku’s app servers serve static content for me. It’s not really a problem, but I just like to use the best tool available for the job.
Because Ariejan.net is a rack app, it has a public directory with all static assets in once place. There are, however, a few problems that need adressing. ~
These are the problems I want to resolve:
Amazon S3 allows you to set per-file permissions to grant read and/or write access. This is nice, but sometimes you just want to share your whole bucket with the world.
Luckily, Amazon features bucket policies, which allow you to define permissions for an entire bucket. ~ This example will give read access to Everyone on all files in your bucket.
{ "Version":"2008-10-17", "Statement":[{ "Sid":"AllowPublicRead", "Effect":"Allow", "Principal": { "AWS": "*" }, "Action":["s3:GetObject"], "Resource":["arn:aws:s3:::bucket/*" ] } ] } Make sure you replace bucket in arn:aws:s3:::bucket/* with your bucket name.
I get a lot of questions about how I bought my Kindle and what it cost to get it shipped to the Netherlands. So, for all those Dutchmen (and Dutchwomen) who are considering a Kindle, here’s a short how-to in Dutch:
For some time I have been eyeballing Sony’s e-reader in the local bookstore. I tried it a few times, but I didn’t like it - actually I had serious doubts about e-books in general because of the experience. Sony’s e-reader was not really easy to use with only one next-page button in a not-so-easy to access place. It also had a slow e-ink screen. It took a second to a second-and-a-half to show the next page. I didn’t like it and had serious doubts about buying any e-reader at all.
But, reading about all the “epic win”-stories of the Kindle by @johnnybusca I just had to give it a try - I bought one.