RedMallorca LAB|Blog LAB para pruebas

[download#2]

http://tantannoodles.com/toolkit/wordpress-s3/

• SmartFTP - Cliente FTP
• net2ftp - a web based FTP client
• FlashFXP by iniCom Networks - FTP Client Software
• InfiniteBits.info :: Web and FTP access to Amazon S3 :: FTP Server for S3
• Google Analytics

• Using Amazon S3 as an Image Hosting Service Coding Horror:
• JungleDisk - Reliable online storage powered by Amazon S3 ™ - Jungle Disk
• S3 Firefox Organizer
• http://gigaom.com/2006/07/13/startups-embracing-amazon-s3/
• Amazon.com Sign In
• The Lightbox Clones Matrix « planetOzh
• http://opendns.com/
• aNieto2K | Desarrollo web, Wordpress, y alguna cosilla más
• CodePlex.SpaceBlock - Home
• CodePlex - Open Source Project Hosting
• Online Status Indicator | for AIM, ICQ, IRC, Jabber, MSN, Skype and Yahoo
• Announcing Bungee Application Server « Bungee Connect Developer Network
• Bungee Grid now running on Amazon EC2 and accessible to Bungee Developers. « Bungee Connect Developer Network
• WideLens™ Calendar :: Home
• Bungee Connect :: Platform-as-a-Service
• Ayuda WordPress en Español
• WordPress Themes, Plugins, Hacks, Guides, and More! | Hack WordPress
• Automatic MySQL Backup
• Edublogs - education blogs
• Off-loading wpmu theme files to Amazon-S3 | Ring Of Blogs
• WPMUDEV.ORG
• Como migrar de Joomla a Wordpress | Ayuda WordPress
• » Joomla2Wordpress Import Wizard v.3
• Como enviar spam a un Blog | Ayuda WordPress
• Automatic Blog Comment Poster Software - Post Comments Automatically
• Permalink Redirect WordPress Plugin | SYP
• | BackUpWordPress | WordPress Designpraxis

http://tantannoodles.com/toolkit/wordpress-s3/

Wordpress.com Powered by Amazon S3, Varnish, and Pound

http://www.quickonlinetips.com/archives/2007/10/wordpresscom-powered-by-amazon-s3-varnish-and-pound/

Many people have told me that they have used the ElasticFox extension for Firefox to get started with Amazon EC2. ElasticFox makes it easy to see the list of available AMIs (Amazon Machine Images), to launch any number of instances of those AMIs, and to monitor and manage the running instances:

We just released version 1.4 of this powerful tool. In addition to wiping out some bugs related to security groups and key management, ElasticFox now supports all of the features of the newest version of the EC2 API - Availability Zones, Elastic IPs, and user-selectable kernels. There are new tabs for kernels and ramdisks, Elastic IPs, and Availability Zones:

An IP address can be allocated and then attached to a running EC2 instance with a couple of clicks:

New instances can be launched in any availability zone, with full control of the kernel (AKI) and ramdisk (ARI):

Finally, you can now filter the AMI list using the box at the top right:

I added this feature myself because I had been spending too much time scrolling through the ever-expanding list of available AMIs during my conference and user group demos.

And that brings me to my last point: ElasticFox is an open source project hosted on SourceForge. It was easy to download the code to my desktop machine (I used TortoiseSVN), install FireBug, figure out how the code worked, and to make and test my changes.

We’ve got ideas for even more features, but there’s no reason to wait for us. If you have some ideas of your own, grab the code, do your thing, and send us your code for review and checkin.

– Jeff;

PS - We are planning to release a version of this extension which is compatible with version 3 of Firefox. This version is well under way, but we didn’t want to hold up release of these great new features in anticipation of the production release of Firefox 3.

Update: If you are brave and somewhat fault-tolerant, you can download and try out the Firefox 3 version here. This version is reportedly faster, and also more responsive — the UI doesn’t freeze when the extension makes background calls to EC2. Please file bugs as you find them (you will need a SourceForge account in order to do so).

Time for an Inbox cleanup…

I met developer Chris Richardson in Philadelphia last month. Chris is a seasoned Java developer and the author of POJOs in Action.

He told me that he had just released CloudTools. This is a set of tools for deploying and testing Java EE applications on Amazon EC2. It consists of AMIs that are configured to work with Apache Tomcat and to work with EC2Deploy, the EC2Deploy core framework (described here), and a Maven plugin which uses EC2Deploy. Once the plugin has been configured, one command will launch the appropriate number of EC2 instances, configure a master MySQL database, populate it with data, configure zero or more MySQL slaves, configure one or more Tomcat servers, deploy the actual web application, and then configure an Apache instance which will load balance across all of the Tomcat instances (whew!).

Tarzan is an set of PHP 5 modules which provide straightforward, object-oriented access to Amazon S3, EC2, SQS, and the Amazon Associates Web Service, with planned support for SimpleDB as well. Currently in late-beta, most of the code is accompanied by unit tests. It requires access to a few common PHP extensions such as SimpleXML and PEAR HTTP Request. Tarzan was used to build Warpshare. The author is seeking patches, new code, and bug reports from the community.

We have just published the code for a Javascript-powered EC2 scratchpad in our Resource Center.

You can load this code on to the server of your choice, or you can simply unpack it into a directory on your desktop machine. Once loaded, simply open up index.html, enter your AWS keys, and start exploring the EC2 APIs.

The scratchpad provides a form-based interface to each of the function calls. It also computes and displays the complete signed URLs needed to actually make the calls into the EC2 cloud. The scratchpad can be used to learn about how to make calls to EC2 or as a cross-check for your own service invocation and request signing code. The return value from each call is displayed in raw XML form.

In a new Business Week cover story, Amazon.com founder and CEO Jeff Bezos discusses his approach to innovation, thinking for the long term, our focus on the needs of customers, and our company culture.

This focus on the needs of our customers is very real and permeates everything that we do at. The information that we gather from meeting with developers, from reading commentary on blog posts (many of which show up on the AWS Buzz), and from our interaction on our developer forums is an intrinsic part of our product planning process.

Speaking of customers, we’ve been adding a lot of new customer-generated content to our Resource Center. Mitch Garnaat wrote about his Son of Monster Muck Mash Mashup, and also contributed an EC2 AMI. A guy named Mark contributed an S3 library for the Runtime Revolution language. Brenton Simpson wrote an ActionScript 3 library for SimpleDB. I’ve been tracking all of this content by simply watching the RSS feed for the Documents section of the Resource Center.

That’s about all I have time for right now!

– Jeff;

I saw a few people looking for solutions to off-load wpmu files to Amazon-S3 service. This is something we wanted to try on our installation (just a few thousand blogs) so I wrote a plugin that will serve themes css and image files from S3.

The plugin uses the ‘stylesheet_directory_uri‘ filter to set the stylesheet uri (css file). In turn, the stylesheet uses the ‘url‘ method to call the image files of the theme so they get the same base url as the stylesheet. Most themes uses the ‘stylesheet_directory‘ call correctly so you will not run into trouble but if a theme uses it to call a php file you should change the call to use ‘template_directory‘.

Download: themes-s3.zip

Usage:

1. Signup for an Amazon-S3 account.
2. Create a bucket for your files. Since you have to select a globally unique name for your buckets I call it s3.domain.com were domain.com is my wpmu installation.
3. To point s3 to your bucket setup a CNAME record: s3 -> s3.domain.com.s3.amazonaws.com. (don’t forget that extra dot at the end).
4. Load your themes css and image files to your bucket keeping the exact directory structure for each theme (/wp-contents/themes/… ). You can use the excellent S3 FireFox Organizer to mange your files.
5. Edit the plugin to include your bucket name.
6. Place the plugin in the mu-plugins directory.
7. Test, test and test all your themes!

Whats next? The next step I’m planning is to off-load the Java Scripts in the wp-includes folder. Also planned is an option to serve the users files from S3. If you are interested in helping in any way please leave a comment and we can take it from there.