Content-Transfer-Encoding: BASE64
Repeat this step for every file. For every instance of this boilerplate code, paste in the .b64 version of your file below it. In the case of the logo image, it looks like this:
--new-boundary
Content-Location: CID:cafe_trade_logo.jpg ;
Content-ID:
Content-Type: IMAGE/ JPEG
Content-Transfer-Encoding: BASE64
/ 9j/4AAQSkZJRgABAgAAZABkAAD/7AARRHVja3kAAQAEAAAAZAAA/+4ADkFkb2Jl
AGTAAAAAAf/bAIQAAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEB…
- Travis Dunn: Posting Multipart File Uploads on the iPhone
- a timocracy of one: Testing a rackup (config.ru) file with Rack::Test
- Developing with Style: Replicating Rails RJS in CakePHP
- Engine Yard Ruby on Rails Blog: Rails and Merb Merge: Performance (Part 2 of 6)
These public and private keys are just big ol' Base64 encoded strings, so plop them in your code as configuration string resources that you can retrieve later.
Next, add some DNS records. You'll need two new TXT records.
_domainkey . example.com
"o=~\; r=contact@example.com"
selector. domainkey . example.com
"k=rsa\; p={private-key-base64-string-here}"
The first TXT DNS record is the global DomainKeys policy and contact email.
The …
- Jason Seifer: Receiving Email with Rails
- Heroku: Heroku Casts - Setting up custom domains
- High Scalability: GEO-aware traffic load balancing and caching at CNBC.com
- Mike Perham: Asynchronous DNS Resolution
- : How To Resell Rackspace Cloud Sites
- DigitalHobbit: Building a Twitter Filter With Sinatra, Redis, and TweetStream