Here’s a quick command you can use to find any folders that are over a GB in size on a Linux OS.
sudo du -h / | grep '[0-9\.]\+G'
Read Next
I recently found myself with the need to connect to a Mongo DB instance from a PHP application running on Amazon EC2. The PHP docs led me to this MongoDB extension, which seemed to be a good fit for my needs. Still, the matter of installation was a little bit less clear, considering that the EC2 instance was pretty barebones and lacked a fair number of the “standard” libraries that would enable this single line installation to work.
After a bit of finagling, I got everything to work via the steps I’ve outlined below.
One of the most common challenges any web designer faces is ensuring that their work appears as intended. Print designers have the advantage of creating the physical designs themselves, but web designers depend upon user environments (read, browsers) to render their designs correctly.
In the past, browsers could only render the fonts already installed on a user’s computer, which meant that users without a good library of fonts would miss out on designs that made use of uncommon fonts. CSS 3 introduces a new fix called @font-fact that could be the future of web design typography.
I’ve been very busy developing a couple projects over the past couple days, but here is a quick little trick to get around one of Drupal’s quirks. If you’re unfamiliar with Drupal, it’s a fantastic CMS (content management system) built on PHP and MySQL. For those blog-savvy among us, it is to general websites what WordPress is to blogs. I use Drupal to get sites up quickly and with great functionality, and I highly recommend it to anyone who is looking to build powerful, custom websites without “re-inventing the wheel.”
Anyway, Drupal has this strange quirk in its source that creates a small grey border on the top of tables inserted in a page’s content. A quick trip to my inspector revealed how to remove the top border from Drupal tables. Simply add the following line to your CSS.
body tbody { border-top: none; }
All there is to it. 🙂
Whenever a MySQL query contains a WHERE conditional, the database server must find all the matching rows before it can execute any operations. In order to optimize this matching, a database administrator might define an index on any columns he or she knows will be used more frequently in WHERE conditions.
Adding an index to an existing table with many rows, however, can take a long time or even fail entirely. Here’s a quick tip to deal with those situations.
