Create a gist now

Instantly share code, notes, and snippets.

What would you like to do?
DocPad: Custom Routing
# =================================
# DocPad Events
# Here we can define handlers for events that DocPad fires
# You can find a full listing of events on the DocPad Wiki
events:
# Server Extend
# Used to add our own custom routes to the server before the docpad routes are added
serverExtend: (opts) ->
# Extract the server from the options
{server} = opts
docpad = @docpad
# Include our custom routes
require(__dirname+'/routes.coffee')({docpad,sever})
# Our custom routes for our DocPad Server
# Loaded via our require in the serverExtend event in our docpad.coffee configuration file
module.exports = ({server,docpad}) ->
# As we are now running in an event,
# ensure we are using the latest copy of the docpad configuraiton
# and fetch our urls from it
config = docpad.getConfig()
oldUrls = config.templateData.site.oldUrls or []
newUrl = config.templateData.site.url
# Redirect any requests accessing one of our sites oldUrls to the new site url
server.use (req,res,next) ->
if req.headers.host in oldUrls
res.redirect(newUrl+req.url, 301)
else
next()

Cool; note that there's a typo in the last line of docpad.coffee: sever should be server.

Gems commented Oct 12, 2013

At the first file docpad.coffee you have "routes" module initialization through "require" function that you've passed two arguments in the following order — docpad, server

But at the second file routes.coffee you've defined module that expects parameters in reverse order — server, docpad.

May be I missed something but it is looks like a bug.

@Gems - thats the advantage of coffee-script object creation / de-structuring. The order doesn't matter. Its just shorthand for creating an object and extracting the values from that object.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment