Using Disqus without any plugins

At TurnGeek we recently had the task to include Disqus (which is great by the way) into our site, so readers of our books can leave comments for each chapter.

For a couple of reasons we couldn’t use their WordPress plugin although the site is running on WordPress. If you’re running in the same issue or you just don’t want the dependency of another plugin, you can paste the following snippet in your WordPress posts (by the way, this also works with non WordPress sites):

Using the data-name attribute you have to set the shortname you’re using on Disqus. This means you have to replace my_disqus_shortname with this shortname, in our case it is turngeekpress, so our snippet looks like this:

Have fun using this and let me know your thoughts.

Proxy Your Requests With Grunt

Probably you’re already using grunt to serve your local frontend code. Everything is fine, but if you’re developing your backend with something different than JavaScript (Being a Java developer I heard that might happen), you will have problems accessing this backend while running grunt server.
With grunt-connect-proxy there exists a grunt module to help you out. It basically delegates requests that match a given URL to a different backend of your choice. Unfortunately I found it rather difficult to configure, if you are unaware of the connect middleware concept.

Basically you just need to add two things to your Gruntfile.js file:

Firstly add the connect server configuration to your config JSON inside of grunt.initConfig. This example delegates all requests to http://localhost:8000/services to http://localhost:8090/services – keep in mind the grunt server is running on port 8000 and the backend on port 8090:

Secondly register your grunt server task:

then you can call your grunt server with the configured proxy via :
grunt server
from the command line.