(Cross post from my Google+)
I have always been a die-hard paper book lover. Nothing to me smells better than a old used book store. But I have recently finally given in to the eReader boom. I have had a Viewsonic gTablet I hacked with Android Honeycomb for about 6 months. On it I have Kindle and started playing with it, downloading sample chapters and a few full books. It quickly grew on me. Then with the release of the Amazon Cloud Reader it has put me over the top.
I enjoy being able to highlight and notate things in the mostly non-fiction books I read. Along with being able to access the books from my phone, tablet, and desktop. Most books I read are technical or startup/business related so my notes come in very handy with the research I do.
Some things that won me over:
- Notations in-line of the books with notes
- The ability to make black on white text and vice versa (big plus when reading in bed)
- Ability to make multiple bookmarks to reference things previous
- Access to books from many devices at once
- Saving a tree or two
- Lightening my load when it comes time to move to another residence
My biggest complaint about Kindle books is the disproportionate pricing compared to hardback or paperback books. Many times the price is only a few dollars less.
I am a big fan of using Subversion for things other than just versioning code. In the past I have used SVN to manage configuration files across many servers. Making it easy to deploy and (if needed) roll back changes. It is also a big help on development servers for PHP developers to commit changes and see them live on the development server. This is easily accomplished using SVN hooks. There are plenty of HowTos on this topic if seeking that information.
Now that I am up to my eyeballs in Amazon Web Services I am looking to use SVN to help me leverage the new found power of the cloud. Now I am not saying it is a good thing to use SVN for things other than code versioning. But it has always worked for me in many other ways as well.
Some of the things I am thinking of using SVN:
- Update DEV web server using hook scripts for devs to see changes to trunk.
- Maintain Apache and other config files for AMIs.
- Maintain code repository for versioning along with take advantage of S3 for backup and processing power of EC2.
This is a work in progress so I am looking to perfect the design to my liking soon.
I have been working on some new projects since leaving my last job about 6 months ago. One is to build an entire infrastructure that is highly available and redundant. With Amazon Web Services this is a snap and almost makes my job obsolete. With EC2, S3, EBS, and CloudFront you can build a scalable solution with dependable backups with ease. My goal now is to also use AWS to create an intranet for the company. I have not found much on this topic so I ma taking the time to document it here. My ideas so far:
- Use Fedora Directory Server as main LDAP solution. This can be used with EBS (Elastic Block Storage) with striped volumes to store the LDAP data. Along with having redundant multi-master replication geographically depending on where the EC2 instance is set.
- Subversion server using EBS for storage. Using EC2 for something along the lines of SVN is a good use since it speeds up performance. Along with having the backup ability of EBS and EBS Snapshots
- Twiki as documentation for intranet.
- SugarCRM for customer relationship management which will include project management and bug tracking.
- S3 for backing up users data automatically. This is helpful since it is a telecommuting company. Using a tool like JungleDisk or similar.
- The DEV and Staging environments will also be on AWS with same Amazon Machine Images (AMIs) as the production environment.
That is all I have so far I will update as the project comes along.