We run a high-traffic content website at www.ehow.com. The site has a complex architecture with database servers, web servers, load balancing, etc. Periodically we experience planned and unplanned downtime. This project is to create a static replica of the website at [url removed, login to view] as it exists today that we can switch over to manually in the event of site downtime. Note while the site appears to be just html files, that is due to a mod_rewrite in Apache, the files are actually served from a database. It is important that the replica contain all of the static content as it appears on the website today, so users will find what they are looking for. It is important that the replica contain the same URL structure as the live site, so that users who are entering directly from search engines will find the pages they are seeking when the search engine directs them to a URL it detected when it crawled the main database-backed website. We will give you passwords to a dedicated server at Serverbeach for you to load the site onto. You job is to do everything to get the site live. When finished with the project the site should be live in ready-to-use condition. As part of your bid, please describe the architecture you will create for the site. We are assuming the content will just be stored in flat html files, one per page. Describe any software you intend to use and how you would set it up. We are assuming an architecture that can run the entire site off of one server. We are assuming you would gather the content just by crawling our site, though it's possible (but not preferred) that we could FTP the content. More simply, we can give you our google XML sitemap to facilitate the crawling of the site. Specifics of what exact features/content must be included are in the attached file. Thank you for your bid. Bids that include no specifics of how you would do the project will be ignored!
1) Complete and fully-functional working replica of the ehow website (minus the limitations specified in this bid). 2) complete set up and hosting onto our server.
Scalability will be important! The server you will be using will be underpowered compared to our standard setup. You will need to architect the site in such a way that it works very efficiently. Open-source software only, please, ideally common stuff such as apache, linux.