Deployment Properties

Overview

This page documents the "deployment" properties used in the configuration to tune the deployment behavior of the system.  

Details

Most of the deployment properties start with "deploy" and they affect the overall system behavior when deployed.  Most of these properties listed below are available to the Javascript environment via 'appConfig' construct which can be injected to any Angular service, directive, or controller.

Following is a sample deploy properties section from the config.properties file with comments indicating what the settings are for and what they do.

#
# The following properties supply configuration information that appears on the 
# application header, footer, or default login page.  They are informational only.
#

# header title
deploy.title=Term Server Demo
# header icon link
deploy.link=http://www.westcoastinformatics.com
# footer copyright
deploy.footer.copyright=Copyright @2017
# footer feedback email
deploy.feedback.email=info@westcoastinformatics.com
# footer "presented by" information
deploy.presented.by=Presented by \
 <a href="http://www.westcoastinformatics.com">West Coast \
 Informatics, LLC</a>
# default login page "reset password" link.
deploy.password.reset=http://passwordreset.example.com

#
# This property determines which tabs are to be displayed by default.
# The behavior of this must be coordinated with the Angular tab service
# and route providers.
#
deploy.enabled.tabs=terminology,content,metadata,workflow,edit,admin,process

#
# These properties indicate whether landing, license, and/or login pages are used
# by the application when a user comes to the base.url.  If landing=true, the
# config project should override the landingContent.html page.  If license=true,
# the config project should override the licenseContent.html page.  If login=true
# the confi gproject should also override the loginContent.html page.
deploy.landing.enabled=true
deploy.license.enabled=true
deploy.login.enabled=true

#
# This is an opportunity to supply code for analytics tracking (e.g. google analytics)
#
deploy.tracking.code=<!-- sample tracking \
  code -->

#
# This is an opportunity to supply code that informs user regarding a cookie policy
#
deploy.cookie.code=<!-- sample cookie \
  code -->

#
# This is used to enable "simple edit" behavior in the application
# BETA feature, still in development so leave it out unless you know
# what you're doing.  This will probably change in future versions.
deploy.simpleedit.enabled=EDIT_THIS

 

  • n/a