pushover Pushover.net is a service that allows you to send popup notifications to your iPhone, iPad or Android device via calls to a simple API.

I wanted a notification whenever someone left me a comment or webmention on my idno site, so I put together a plugin that does just that!

Installation

Install and activate the Pushover plugin on your idno site, and then create an application for your site on Pushover.net, via their admin panel.

Once you have done this, go back to your idno site and configure the plugin via your user settings page, putting the application and user API keys in the appropriate boxes.

Hit save, and you should now get popup notifications whenever a new comment is left!

» Visit the project on Github…

Idno was primarily built around the idea of distributed commenting, that is, when replying to a post written on someone else’s blog you’d actually write your reply on your own site, and then send a webmention.

This works well, but since many people are still trapped in legacy silo platforms like Facebook or Google+, it’d be nice if they could have a way to join in the discussion. So, I put together a quick plugin which provides traditional commenting functionality.

This plugin, once installed and activated, will provide comments for logged in and logged out users. At the moment it’s pretty basic, but hopefully I’ll add spam filtering, moderation and gravatar support soon.

» Visit the project on Github…

I do a lot of web development these days, on number of projects, which often require their own domain, so I thought I’d share a quick tip that I’ve found helpful.

In a nutshell, I use wildcard domains and used the Apache vhost alias module in order to be able to automatically create a domain per project.

Setting up bind

The first step is to set up wildcard DNS for your machine, in this case *.dev.mymachine. Assuming you’ve got bind set up, this is just a matter of configuring a local zone for your network (or adding this to your existing local zone).

It’s late, and I’m tired, Google “wildcard dns bind” and that’ll point you in the right direction.

Setting up the vhost

Next, you need to set up an Apache vhost for your wildcard domain, but crucially, instead of specifying DocumentRoot in the normal way define VirtualDocumentRoot.

First, enable the module:


a2enmod vhost_alias

Then, set up and enable a definition which uses variables supplied by the vhost_alias, which will use the structure of the url line to load the appropriate web page.


<VirtualHost *>

ServerAdmin webmaster@myhost.com
ServerName myhost.com
ServerAlias *.myhost.com

# Indexes + Directory Root.
DirectoryIndex index.html index.php
VirtualDocumentRoot /home/%2/mycode/%1/

<Directory "/home/*/mycode/">
AllowOverride All
Options +Indexes +Includes +FollowSymlinks +ExecCGI
</Directory>

</VirtualHost>

The above code will use the directory name plus the user’s username, for example, fizzbuzz.marcus.myhost.com.

What this means is that you don’t need to create a new virtual host for each one of your projects, which may save you a little time.