bjl23
|
94e89060ba
|
NIHVIVO-1584 documentation changes for new DB-related deploy properties
|
2011-01-14 16:51:37 +00:00 |
|
cdtank
|
63a3e318ea
|
1. Added comment about the new visualization.topLevelOrg property for deploy.proeprties. Added similar content for install.txt.
2. Made front-end improvements to temporal graph vis per Katy's suggestions.
3. Made improvements to person level vis front-end.
|
2011-01-13 21:30:15 +00:00 |
|
bjl23
|
b68a6240e7
|
NIHVIVO-1509 max idle connections property
|
2011-01-13 19:37:49 +00:00 |
|
bjl23
|
651808da50
|
additions to example.deploy.properties
|
2011-01-07 21:18:13 +00:00 |
|
jeb228
|
42191b21b1
|
NIHVIVO-1329 document how to setup Shibboleth.
|
2010-12-14 21:58:02 +00:00 |
|
bjl23
|
a45190973d
|
NIHVIVO-1509 connection pool size configuration
|
2010-12-13 15:24:54 +00:00 |
|
nac26
|
2e66dea391
|
more cleanup after the iu-vis reintegration...rolling back example.deploy.properties to r1729 (extra space was introduced on line 17)
|
2010-11-22 20:11:19 +00:00 |
|
bkoniden
|
67d14f3212
|
re-integrating the branch /branches/iu-vis-dev-branches/vivo-post-1.1
|
2010-11-22 19:39:51 +00:00 |
|
jeb228
|
fd98969be3
|
Merge revisions 415 to the trunk. For bdc34
|
2010-04-13 12:57:52 +00:00 |
|
jeb228
|
45882f3dd7
|
Return comment and default setting for vitro.core.dir to reflect the structure of the release files.
|
2010-03-29 19:32:48 +00:00 |
|
rjy7
|
4caa07f705
|
Updated default to reflect current repository structure (vitro now no longer inside vivo)
|
2010-03-23 15:03:45 +00:00 |
|
rjy7
|
5bdb859d4f
|
Updated comment to reflect current repository structure (vitro now no longer inside vivo)
|
2010-03-23 15:03:08 +00:00 |
|
jeb228
|
710ddfedc6
|
NIHVIVO-56 Adjust to the restructured core build script - use a build that is based on the core product-build script.
|
2010-02-21 18:46:05 +00:00 |
|
jeb228
|
4b5a111b8b
|
Correct a typo in the example paths: /usr, not /user
|
2010-02-08 20:05:42 +00:00 |
|
jeb228
|
3f17d16d7b
|
Tweak the build script, so a developer can build vitro-core and it won't have any effect when they build vivoweb in the same workspace.
|
2010-01-29 22:12:41 +00:00 |
|