You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+10-10Lines changed: 10 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -26,29 +26,29 @@ Resources/Providers
26
26
The LWRPs provided by this cookbook are not meant to be used by themselves; make sure you are familiar with the `application` cookbook before proceeding.
27
27
28
28
29
-
### `java\_webapp`
30
-
The `java\_webapp` sub-resource LWRP deals with deploying Java webapps delivered as WAR files which will either be retrieved from a remote URL or fetched by some other method and referenced locally.
29
+
### `java_webapp`
30
+
The `java_webapp` sub-resource LWRP deals with deploying Java webapps delivered as WAR files which will either be retrieved from a remote URL or fetched by some other method and referenced locally.
31
31
32
32
NOTICE: the `application` cookbook was designed around frameworks running on interpreted languages that are deployed in source code, checked out of an SCM using the `deploy_revision` resource. While this cookbook tries to map those concepts to a binary distribution mechanism, it may not map exactly.
33
33
34
34
#### Attribute Parameters
35
-
-database\_master\_role: if a role name is provided, a Chef search will be run to find a node with than role in the same environment as the current role. If a node is found, its IP address will be used when rendering the context file, but see the "Database block parameters" section below
36
-
-context\_template: the name of template that will be rendered to create the context file; if specified it will be looked up in the application cookbook. Defaults to "context.xml.erb" from this cookbook
35
+
-database_master_role: if a role name is provided, a Chef search will be run to find a node with than role in the same environment as the current role. If a node is found, its IP address will be used when rendering the context file, but see the "Database block parameters" section below
36
+
-context_template: the name of template that will be rendered to create the context file; if specified it will be looked up in the application cookbook. Defaults to "context.xml.erb" from this cookbook
37
37
- database: a block containing additional parameters for configuring the database connection (see below)
38
38
- war: if provided, will override the default of the basename of the repository
39
39
40
40
#### Database block parameters
41
41
The database block can accept any method, with the following being expected by the stock context.xml.erb:
42
42
43
43
- driver: a fully-qualified class name of the JDBC driver
44
-
- host: hostname or IP address of the database server; if set it will take precedence over the address returned from the search for database\_master\_role
44
+
- host: hostname or IP address of the database server; if set it will take precedence over the address returned from the search for database_master_role
45
45
- port: port to use to connect to the database server
46
46
- database
47
47
- username
48
48
- password
49
-
-max\_active: used to set the maxActive context parameter
50
-
-max\_idle: used to set the maxIdle context parameter
51
-
-max\_wait: used to set the maxWait context parameter
49
+
-max_active: used to set the maxActive context parameter
50
+
-max_idle: used to set the maxIdle context parameter
51
+
-max_wait: used to set the maxWait context parameter
52
52
53
53
You can invoke any other method on the database block, which will result in an entry being created in the `@database` Hash which is passed to the context template. See the examples below for more information.
54
54
@@ -58,7 +58,7 @@ The `tomcat` sub-resource LWRP configures Tomcat to run the application by creat
58
58
59
59
Attributes
60
60
----------
61
-
### scm\_provider
61
+
### scm_provider
62
62
Supports all standard scm providers (git, svn), and in addition:
63
63
* Chef::Provider::RemoteFile::Deploy allows downloading from a remote url
64
64
* Chef::Provider::File::Deploy allows using a package on the filesystem
0 commit comments