Use an even smarter way of including additional resources for monotone

by using a wildcard dir matcher and document this accordingly.
This commit is contained in:
Thomas Keller 2010-10-30 22:09:55 +00:00
parent 612d00ade2
commit 039ae01cfa
3 changed files with 25 additions and 8 deletions

View File

@ -199,7 +199,7 @@ somewhere else for backup purposes. The monotone source tree already comes
with [many example scripts and hooks](http://code.monotone.ca/p/monotone/source/tree/h:net.venge.monotone/contrib) with [many example scripts and hooks](http://code.monotone.ca/p/monotone/source/tree/h:net.venge.monotone/contrib)
which serve these purposes, after only little additional configuration. which serve these purposes, after only little additional configuration.
The usher/indefero-controlled setup automatically looks for a file called The usher/indefero-controlled setup automatically looks for *.lua files
`hooks.lua` in the project's base directory (configured via $cfg['mtn_repositories']) in a directory called `hooks.d` right under the project's base directory
and this is the ideal place to put or link these additional lua sources. (configured via $cfg['mtn_repositories']) and this is the ideal place to
put or link these additional lua sources.

View File

@ -65,6 +65,15 @@ push_hook_functions({
}) })
-- --
-- Load additional local hooks, in case they exist -- Load local hooks if they exist.
-- --
include(get_confdir() .. "/hooks.lua") -- The way this is supposed to work is that hooks.d can contain symbolic
-- links to lua scripts. These links MUST have the extension .lua
-- If the script needs some configuration, a corresponding file with
-- the extension .conf is the right spot.
--
-- First load the configuration of the hooks, if applicable
includedirpattern(get_confdir() .. "/hooks.d/", "*.conf")
-- Then load the hooks themselves
includedirpattern(get_confdir() .. "/hooks.d/", "*.lua")

View File

@ -79,6 +79,14 @@ push_hook_functions({
}) })
-- --
-- Load additional local hooks, in case they exist -- Load local hooks if they exist.
-- --
include(get_confdir() .. "/hooks.lua") -- The way this is supposed to work is that hooks.d can contain symbolic
-- links to lua scripts. These links MUST have the extension .lua
-- If the script needs some configuration, a corresponding file with
-- the extension .conf is the right spot.
--
-- First load the configuration of the hooks, if applicable
includedirpattern(get_confdir() .. "/hooks.d/", "*.conf")
-- Then load the hooks themselves
includedirpattern(get_confdir() .. "/hooks.d/", "*.lua")