Install the digg AdBlocker extension for Google Chrome here:

https://chrome.google.com/extensions/detail/gclmekogkkggoehdimnceffmboanpibn

Check out the source here:

http://tdupree.com/chrome/digg_adblocker/chrome_digg_adblocker_source.zip

Install Hacker News OnePage for Google Chrome:

https://chrome.google.com/extensions/detail/plldnnbdlbgbiknjebohmlggcbicghlj

Check out the source code:

http://tdupree.com/chrome/chrome_onepage/chrome_hn_onepage_source.zip

Google just recently released Chrome v3.0, and the developer builds in the dev channel now have extensions turned on by default (no need to append –enable-extensions to the exe target).  The extensions system for Chrome is getting nicer and nicer (just check out chrome://extensions in your Chrome browser).  I have a working version of Hacker News OnePage that I have tested with dev channel build 4.0.206.1.  I assume that it will also work fine with the new 3.0 stable release if you have extensions enabled.

Install Hacker News OnePage (OnePage.crx)

Download the source (OnePage.zip)

Everything worked fine in Firefox and IE.  When I went to test it in Chrome and Safari non of the functionality worked and I received an error such as “TypeError: Result of expression ‘jQuery(document).ready’ [undefined] is not a function”.  I tried some workarounds and got rid of the above error but was stuck with “Error: NOT_SUPPORTED_ERR: DOM Exception 9″ referring to line 1081 of prototype.js.

Eventually, in searching the net, I stumbled across the solution.  If you need to use jQuery with an old version of prototype/scriptaculous/moodom, make sure you load your namespaced jQuery library, and any jQuery code you write, BEFORE the other legacy js frameworks. Works like a charm now.

A new update to Chrome brought a better packaging system for extensions, but also broke all the extensions packaged with the old system.  So here are the new Hacker News and Digg extensions that will work with chrome.

Hacker News OnePage (install): Provides users with the ability to browse Hacker News articles and comments without leaving the page. source - manifest

Digg AdBlocker (install): Removes ads from digg. source - manifest

Today I decided to convert some of my Greasemonkey Scripts to Chrome Extensions.  I converted my Digg AdBlocker, Hacker News OnePage, and Hacker News Comments scripts.  It turned out to be quite easy, I barely had to change anything to get them running as Chrome Extensions.  I packaged them using the python script Google supplied, so they are easy for anyone to install.

To use the extensions, you first need to be running the dev build of Google Chrome, you can get it here. Then ad --enable-extensions to your Chrome command line. Do this by right clicking your Chrome shortcut and choosing “properties”. Then in the “Target:” field add a space after the file path and then add the command.  It should like similar to “C:\...your..path..\chrome.exe --enable-extensions“.

Click the following install links and Chrome will ask you if you wish to install the extension.  There are also links to view the source and JSON manifest of the extensions.

Hacker News OnePage (install): Provides users with the ability to browse Hacker News articles and comments without leaving the page. source - manifest

Hacker News Comments Footer (install): Adds a footer to the end of the comments pages to give a visual cue of the end of page. source - manifest

Digg AdBlocker (install): Removes ads from digg. source - manifest

To view your installed extensions, or to uninstall an extension visit this address in Chrome: chrome://extensions/

Here are some resources you might find helpful in getting your nginx server up and running…

-

Official Stuff:

Official nginx website: http://nginx.net/

Official nginx English wiki: http://wiki.nginx.org/Main

-

Installing nginx on Ubuntu Intrepid:

Install it really quick  - Install nginx using aptitude package manager

or

Install it from source (giving you much greater control) - Install nginx from source

When installing from source, make sure you look over the install options.  You may want to configure nginx to support https, mail proxy, or sha1 (–with-http_ssl_module, –with-mail, –with-sha1=DIR). Check it out here: Nginx Compile-time Options

If you installed from source, make the init scripts to start nginx on reboot: Nginx init scripts

now that you have installed nginx, you will need to…

-

Configure nginx (modifying the nginx.config file)

This link is more usefull if you installed nginx using the aptitude package manager.  If you installed from source, you will just have to keep your eye out or differences in paths etc.: Slicehost nginx.config tutorial

Learn about all the modules in your nginx.config file: Nginx Modules

More advanced configuration examples: Nginx Configuration Examples

Once you have nginx running you will probably want to get MySQL and PHP running as well so you can actually do something.

-

MySQL, PHP5, FastCGI, and other goodies

Between the following articles and Googling here and there, you should be able to get MySQL, PHP5, FastCGI, Ruby on Rails, etc up and running alongside nginx.

Tutorial 1 - nginx, MySQL, PHP5, and FastCGI

Tutorial 2 - nginx, MySQL, PHP5, FastCGI, Ruby on Rails, and Rewrite

Tutorial 3 - nginx, MySQL, PHP5, PHP-fpm, and Ruby

Tutorial 4 - nginx and PHP5

Turorial 5 - nginx, PHP5, and xcache

Tutorial 6 - nginx, MySQL, PHP5, and FastCGI

Tutorial 7 - nginx, PHP5, FastCGI, and xcache

Tutorial 8 - nginx, PHP, FastCGI, APC

I also found the slicehost forum to be of help as well: Slicehost forum

Update (04/13/2009): nginx “how to” by calomel.org.  This has a lot of great information and explains things very clearly. It also goes over setting up https with a GoDaddy SSL cert.

Good luck!

RewriteEngine On
RewriteBase /
RewriteCond %{HTTP_HOST} !^mydomain.com$ [NC]
RewriteRule ^(.*)$ http://mydomain.com/$1 [L,R=301]

Just replace “mydomain” with the name of your domain and you’re done. Thats it! Now any time someone goes to www.mydomain.com the www. will be automatically dropped.  The one caveat, your server has to be running the apache webserver for this to work.  If you’re on a linux host, you proabably run apache webserver and are good to go.