4343 </ div >
4444 </ div >
4545 < div class ="row ">
46- < div class ="span3 " id ="fsp-side-nav ">
46+ < div class ="span2 " id ="fsp-side-nav ">
4747 < ul class ="nav nav-list fsp-side-nav-ul affix ">
4848 < li > < a href ="#introduction "> Introduction</ a > </ li >
4949 < li > < a href ="#servers "> Servers</ a > </ li >
5252 < li > < a href ="#wsgi-server "> WSGI Server</ a > </ li >
5353 </ ul >
5454 </ div >
55- < div class ="span9 ">
55+ < div class ="span9 offset1 ">
5656 < section id ="introduction " class ="tech-section ">
5757 < h1 > Introduction</ h1 >
5858 < p > You're knee deep in learning the < a class ="reference external " href ="http://www.python.org/ "> Python</ a >
@@ -100,9 +100,16 @@ <h1>Servers</h1>
100100</ ol >
101101< div class ="section " id ="bare-metal ">
102102< h2 > Bare metal</ h2 >
103- < p > The most control and also the highest maintenance. Buy actual hardware
104- from a vendor either pre-built or as a collection of components that
105- you assemble yourself.</ p >
103+ < p > The term < em > bare metal</ em > refers to purchasing the actual hardware and hooking
104+ it up to the Internet either through a business-class internet service
105+ provider (ISP) or
106+ < a class ="reference external " href ="http://webdesign.about.com/od/colocation/a/what_colocation.htm "> co-locating the server</ a > with other servers.</ p >
107+ < p > The bare metal option offers the most control over the server configuration,
108+ usually has the highest performance for the price, but also is the most
109+ expensive upfront option and the highest ongoing maintenance. With bare
110+ metal servers the ongoing operating cost is the electricity the server(s)
111+ use as well as handling repairs when server components malfunction.</ p >
112+ < p > Buy actual hardware from a vendor either pre-built or as a collection of components that you assemble yourself.</ p >
106113</ div >
107114< div class ="section " id ="virtualized-servers ">
108115< h2 > Virtualized servers</ h2 >
@@ -120,7 +127,15 @@ <h2>Virtualized servers</h2>
120127overhead in the virtualization process. In addition, physical constraints
121128such as heavy I/O operations by a single virtualized instance on persistent
122129storage can cause performance bottlenecks for other virtualized instances on
123- the shared server.</ p >
130+ the shared server. Choosing virtualized server hosting should be based on
131+ your needs for urgency of service ticket requests and the frequency you
132+ require for ongoing maintenance such as persistent storage backups.</ p >
133+ </ div >
134+ < div class ="section " id ="infrastructure-as-a-service ">
135+ < h2 > Infrastructure-as-a-service</ h2 >
136+ </ div >
137+ < div class ="section " id ="platform-as-a-service ">
138+ < h2 > Platform-as-a-service</ h2 >
124139</ div >
125140< div class ="section " id ="server-monitoring ">
126141< h2 > Server Monitoring</ h2 >
0 commit comments