modules_appfolder. These modules we create are for developers eyes, and will not show up in the 'Manage Modules' administration menu. These are modules that you wouldn't want someone accidentally turning on / off, for example, a key part of the website.
/customModule/is added to the apps main routing table, by setting the entry point above. These children routes build on top of that.
/customModule/- and if that pattern is matched, that route says we want to use the 'Home" handler, and the "index" action. That is why you see the error looking for that, its because this is the default event for this module. You will also see there is another route pattern below,
/:handler/:action- this includes placeholders. So this will match anything with 2 or more values, and then it will use the first value as the handler name, and the second piece as the action.
/modules_app/customModule/views/home/index.cfmWe'll put in an <h1>My Custom Module</h1> and see what happens when we hit the entry point now.