line |
stmt |
bran |
cond |
sub |
pod |
time |
code |
1
|
|
|
|
|
|
|
package Bigtop::Backend::Conf; |
2
|
|
|
|
|
|
|
|
3
|
1
|
|
|
1
|
|
5
|
use Bigtop::Keywords; |
|
1
|
|
|
|
|
2
|
|
|
1
|
|
|
|
|
84
|
|
4
|
|
|
|
|
|
|
|
5
|
|
|
|
|
|
|
BEGIN { |
6
|
1
|
|
|
1
|
|
6
|
Bigtop::Parser->add_valid_keywords( |
7
|
|
|
|
|
|
|
Bigtop::Keywords->get_docs_for( 'app', 'location' ) |
8
|
|
|
|
|
|
|
); |
9
|
1
|
|
|
|
|
4
|
Bigtop::Parser->add_valid_keywords( |
10
|
|
|
|
|
|
|
Bigtop::Keywords->get_docs_for( |
11
|
|
|
|
|
|
|
'controller', 'location', 'rel_location' |
12
|
|
|
|
|
|
|
) |
13
|
|
|
|
|
|
|
); |
14
|
1
|
|
|
|
|
4
|
Bigtop::Parser->add_valid_keywords( |
15
|
|
|
|
|
|
|
Bigtop::Keywords->get_docs_for( |
16
|
|
|
|
|
|
|
'app_literal', 'Conf' |
17
|
|
|
|
|
|
|
) |
18
|
|
|
|
|
|
|
); |
19
|
1
|
|
|
|
|
3
|
Bigtop::Parser->add_valid_keywords( |
20
|
|
|
|
|
|
|
Bigtop::Keywords->get_docs_for( |
21
|
|
|
|
|
|
|
'controller_literal', 'GantryLocation', |
22
|
|
|
|
|
|
|
) |
23
|
|
|
|
|
|
|
); |
24
|
|
|
|
|
|
|
} |
25
|
|
|
|
|
|
|
|
26
|
|
|
|
|
|
|
1; |
27
|
|
|
|
|
|
|
|
28
|
|
|
|
|
|
|
=head1 NAME |
29
|
|
|
|
|
|
|
|
30
|
|
|
|
|
|
|
Bigtop::Backend::Conf - defines the legal keywords for conf backends |
31
|
|
|
|
|
|
|
|
32
|
|
|
|
|
|
|
=head1 SYNOPYSIS |
33
|
|
|
|
|
|
|
|
34
|
|
|
|
|
|
|
If you are making an conf generating backend: |
35
|
|
|
|
|
|
|
|
36
|
|
|
|
|
|
|
use Bigtop::Backend::Conf |
37
|
|
|
|
|
|
|
|
38
|
|
|
|
|
|
|
This specifies the keywords for conf generating backends. Note |
39
|
|
|
|
|
|
|
that you don't need inherit from this module, simply use it. |
40
|
|
|
|
|
|
|
|
41
|
|
|
|
|
|
|
If you need to add a generally useful keyword, add it here |
42
|
|
|
|
|
|
|
(and send in a patch). If you need a backend specific keyword, register |
43
|
|
|
|
|
|
|
it within your backend module. |
44
|
|
|
|
|
|
|
|
45
|
|
|
|
|
|
|
=head1 DESCRIPTION |
46
|
|
|
|
|
|
|
|
47
|
|
|
|
|
|
|
If you are using a Bigtop backend in the Conf family, you should |
48
|
|
|
|
|
|
|
read this document to find out what the valid keywords are and what |
49
|
|
|
|
|
|
|
effect they have. |
50
|
|
|
|
|
|
|
|
51
|
|
|
|
|
|
|
If you are writing a Bigtop::Conf:: module, you should use this |
52
|
|
|
|
|
|
|
module. That will register the keywords your module will need. |
53
|
|
|
|
|
|
|
|
54
|
|
|
|
|
|
|
=head1 BASIC STRUCTURE |
55
|
|
|
|
|
|
|
|
56
|
|
|
|
|
|
|
A bigtop file looks like this: |
57
|
|
|
|
|
|
|
|
58
|
|
|
|
|
|
|
config { |
59
|
|
|
|
|
|
|
} |
60
|
|
|
|
|
|
|
app name { |
61
|
|
|
|
|
|
|
controller name { |
62
|
|
|
|
|
|
|
} |
63
|
|
|
|
|
|
|
} |
64
|
|
|
|
|
|
|
|
65
|
|
|
|
|
|
|
=head1 KEYWORDS |
66
|
|
|
|
|
|
|
|
67
|
|
|
|
|
|
|
Inside the app braces, you can include the location keyword. Its value will |
68
|
|
|
|
|
|
|
be the base Apache Location for the application. Location defaults to '/'. |
69
|
|
|
|
|
|
|
|
70
|
|
|
|
|
|
|
Inside the controller braces, you may include a location or a |
71
|
|
|
|
|
|
|
rel_location keyword. Use location to specify the absolute Apache Location |
72
|
|
|
|
|
|
|
or rel_location to specify the path relative to the app level location. |
73
|
|
|
|
|
|
|
|
74
|
|
|
|
|
|
|
You can also add literal output in the generated conf file at either the |
75
|
|
|
|
|
|
|
top level or at locations. Use literal Conf at the app level and/or literal |
76
|
|
|
|
|
|
|
GantryLocation at the controller level to generate it. |
77
|
|
|
|
|
|
|
|
78
|
|
|
|
|
|
|
=head1 AUTHOR |
79
|
|
|
|
|
|
|
|
80
|
|
|
|
|
|
|
Phil Crow |
81
|
|
|
|
|
|
|
|
82
|
|
|
|
|
|
|
=head1 COPYRIGHT and LICENSE |
83
|
|
|
|
|
|
|
|
84
|
|
|
|
|
|
|
Copyright (C) 2005 by Phil Crow |
85
|
|
|
|
|
|
|
|
86
|
|
|
|
|
|
|
This library is free software; you can redistribute it and/or modify |
87
|
|
|
|
|
|
|
it under the same terms as Perl itself, either Perl version 5.8.6 or, |
88
|
|
|
|
|
|
|
at your option, any later version of Perl 5 you may have available. |
89
|
|
|
|
|
|
|
|
90
|
|
|
|
|
|
|
=cut |