Posts tagged Hosting
PHP 5.3 added a useful feature, per-directory .ini files. You can enter PHP configuration directives into a text file named “.user.ini”, upload it to your htdocs directory or any other directory of your website, and that configuration will be used for any PHP scripts in that directory or below.
For example, you may not want to display page errors to visitors of your website, but want to see them for anything in the /development/ sub-directory where you’re working on new things. You might create a .user.ini file in that sub-directory containing
error_reporting = E_ALL
display_errors = On
display_startup_errors = On
Or perhaps you have a sub-directory of remote procedure calls which are invoked from a webpage via AJAX and always return JSON data. You could simplify them by creating a .user.ini file in that subdirectory containing
default_mimetype = “application/json”
display_errors = Off
What can’t you do? You can’t use any configuration directives marked PHP_INI_SYSTEM, which cover fundamental and security-related PHP configuration are reserved for the root php.ini file.
- They boast of their “multi-homed SLIP” connectivity
- They’re proud to provide both types of power, volts and amps
- Each rack is supplied with its own extension cord and ground plug adapter
- Their climate control system is an open window and a $10 box fan
- They try to sell you a “virtual rail kit”
- Private cages can be used for fights on the weekends
- Their tech support email address ends in @hotmail.com
- Their fire suppression system is a “No Smoking” sign
- Their security system reads “Beware of Shih-Tzu”
- Their backup system involves WinZip and BitTorrent
Congratulations to Tegile, whose press release today (picked up on multiple news sites, links below) includes one of the reasons we chose their HA2100EP storage array for our needs: Low latency & high throughput. We also needed iSCSI and F/C for our customers.
Newcomer gets out its box, plans to sell it cheaply to all comers http://ger.ms/LTjuzY
Tegile Selected as a Red Herring Top 100 North America Tech Startup http://ger.ms/KxUJZE
Our vmForge VDC clusters are peaking around 14,000 IOPS and the MASS solution is offloading about 11,500 IOPS via SSD. I wish I could graph this and show it to the public at large but I don’t have a way yet. (those are peaks, average is closer to ~8,000 IOPS with ~6,900 IOPS via SSD)
There is always confusion about what DNS does and what it doesn’t do. In particular, I see constant reference to DNS functions mixed up with web server functions, and vice-versa. Hopefully this post clarifies things a bit to separate what DNS does and what web servers handle.
IP address allocation for web hosting isn’t really a new topic, it has in fact been pretty well resolved for over a decade. But it’s still a point of confusion to some people, so here we go.
Websites have a hostname, like www.iphouse.com. When you click on a link or enter a URL into your web browser, the browser extracts the hostname from the URL and opens a connection to it. But the network doesn’t work with a hostname, it works with numeric IP addresses like 3522190849, which is usually written 184.108.40.206. So the web browser first has to look up the IP address for the hostname through DNS, the Domain Name System. Once it has an IP address, it can open a connection to the server and request the file.