Archive for the ‘Backend’ Category

File Under: Backend

Set Up a Home Server

Setting up a home server running an open-source operating system is a popular and useful activity. Useful in what ways, you may ask. You could use it to run a website (I use a home server to power my world travel website,, collect and send e-mail messages, store your OpenID credentials or serve your music around the home.

As you can guess, we have a great many tutorials on Webmonkey for getting the most out of that machine in your closet. But here are some guidelines for the hardware side of it.

Continue Reading “Set Up a Home Server” »
File Under: Backend

Set Up a Debian or Ubuntu Machine as a Maildrop

The setup described here enables you to store all your email (and email for other people) on a single machine, which might be a home server, a remotely hosted server, or even a desktop, and then access it from anywhere.

Continue Reading “Set Up a Debian or Ubuntu Machine as a Maildrop” »
File Under: Backend, Security, Software

Modify User Permissions

File permissions on Unix and Linux are one of the most ubiquitous stumbling blocks for even regular users of those operating systems. The intricate structure of which users on a system are allowed to do what is one of the foundations of Unix, providing security and interoperability, but at times it can make working with the system a pain. Here’s a look at how permissions work and how to work with them.

Continue Reading “Modify User Permissions” »
File Under: Backend, Web Services

Google Launches a Public DNS Service

If you’ve ever looked at a common web technology, protocol, service or piece of internet infrastructure and wondered aloud if Google was working on its own better, faster version of it, rest assured that the answer is almost always, “yes.”

The company announced Thursday that it is launching a public domain name system (DNS) service. On the Google Public DNS project’s website, Google tells us why DNS matters to everyone:

The DNS protocol is an important part of the web’s infrastructure, serving as the internet’s phone book: every time you visit a website, your computer performs a DNS lookup. Complex pages often require multiple DNS lookups before they start loading, so your computer may be performing hundreds of lookups a day.

The company’s plan, in its words, is to make those lookups happen faster, more securely and without redirects.

To start using Google Public DNS, set your network controls for the heart of Google’s servers, which live at the very cool IP addresses and

There are also full configuration instructions for changing your “web switchboard operator” on the Google Public DNS docs page.

If you set it up, let us know how it performs for you.

Google will always swear it isn’t up to no good, but some feel this launch is clearly a move to collect as much user data as possible to use for ads, better traffic routing and, of course, improving search.

One thing to note: in the project FAQ, Google says it does not plan to release Google Public DNS as an open source project, and as of now, it is an experimental service with no software license agreement that is only designed to be implemented within Google.

Of course, the web already has a free, fast DNS service you can use in tandem with or as a replacement for your ISP’s DNS service. It’s called OpenDNS, and it offers more control over your experience than Google does.

As expected, the founder of OpenDNS is not taking Thursday’s news lying down.

See also:

File Under: Backend, Web Services

New Google Tools Help Speed Up Your Website

Good web developers know that even the most beautifully designed page is worthless if it takes too long to load.

To help you optimize your pages, Google has announced a new Labs feature in Google Webmaster Tools designed to track page load speed. The new Site Performance tool is one part tracking and stats tool, and one part Firefox add-on.

The tracking and stats can be accessed through the Labs menu in Google Webmaster Tools. To get the live profiling add-on, you’ll need to be using Firefox and have the Firebug add-on installed. Yes, like Yahoo’s YSlow add-on, Google’s Page Speed add-on injects some extra profiling tools into the Firebug panel.

These days, nearly everyone has a blog or a website they maintain. Popular publishing systems like WordPress, Movable Type and Blogger do a decent job of keeping your sites slim, but once you load up a complicated theme and add a few widgets, your page load times can start to take a substantial hit. Google’s new set of tools, along with similar tools like Yahoo’s YSlow, are powerful and full-featured, making them a must for large-scale site developers. But they are also easy to install and simple enough to use that even bloggers and small site builders should gain plenty of insight from the data they provide.

To get the new tools, install the Firebug add-on and head to the Site Performance section of Google Webmaster Tools. At the bottom of the page you’ll see a button to install the new Firefox plugin. Once installed, head to your site, click the Firebug icon and look for two new tabs: Page Speed and Page Speed Activity.

Click on Page Speed and run the tool and you’ll get a list of potential speed killers. For example are you using image compression? How about minifying JavaScript and CSS? The handy part is that Page Speed offers links to minified and compressed version of your files.

So what does Google’s new tool offer that YSlow doesn’t? Well, there is definitely some overlap, but Page Speed has quite a few more details that make it worth having. For instance the CSS profiling looks at the complexity of your selectors — shorter, more specific CSS rules mean the browser has less to evaluate, hence faster parsing. Google’s Page Speed tools parse your CSS and suggest optimizations.

Even some of the tools that duplicate those of YSlow are a bit nicer than what YSlow offers. For example the list of links to external images and files is much easier to see at glance in Google’s interface and the links to detailed explanations are a nice touch.

We did notice an odd conflict between YSlow and Google’s new tools. In our tests, YSlow didn’t report any cookies coming from the domain serving images, but Google Page Speed did. Which one is right? Frankly we’re not sure, our cookie logs don’t show anything for the image domain, but that doesn’t mean cookies weren’t sent.

Despite a couple of quirks Google’s new Page Speed tools for Firebug are a worth addition to your web profiling toolset. There’s definitely some overlap with YSlow, but enough extra features to make it worth having both on hand when you’re testing websites.

See Also: