Skip to content

Applying .meta directives to new files #141

Answered by Johann150
jbanana asked this question in Q&A
Discussion options

You must be logged in to vote

The issue here is that the Globs (* or **) are "compiled" (i.e. expanded into all matching absolute paths) when the .meta file is read. This allows Agate to just look up the path, without having to handle pattern matching or conflicts while serving a file. This of course means better performance no matter how complicated your configuration file is. (The metadata lookup performance is O(log(n)) where n is the number of entries compiled to.)

However, the .meta file will be reread during a request, if its last modified time changes, which also recompiles the globs. And that could be done by either editing and saving the file, or by using touch(1).

Replies: 1 comment 1 reply

Comment options

You must be logged in to vote
1 reply
@jbanana
Comment options

Answer selected by jbanana
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants