Sometimes I leave processes running which take up ports on my local machine (e.g., Redis server). I won’t be able to use the port until it’s freed up, but it’s sometimes a chore to figure out how to kill the process by port.
I found the following snippet super useful to kill a process by port in Mac OS:
lsof -t -i tcp:[port] | xargs kill
Just replace the [port] above with the actual numbered port (e.g., 6379).
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'
If you’re SSH’d into a MySQL server and want to export MySQL query results to CSV (readable by Excel), simply add the below snippet to the end of your query.
INTO OUTFILE '/tmp/results.csv' FIELDS TERMINATED BY ',' ENCLOSED BY '"' LINES TERMINATED BY '\n'
Note that ‘/tmp/results.csv’ in the code above should correspond to a writeable destination, and the file can’t already exist.
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. 🙂
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.
