~donal-k-fellows/taverna-server/2.4.1i-maintenance

« back to all changes in this revision

Viewing changes to server-webapp/src/main/webapp/WEB-INF/tavernaserver.properties

  • Committer: Donal Fellows
  • Date: 2015-06-23 10:32:45 UTC
  • Revision ID: git-v1:75f33c4befcbf47d6d1068e585e7e73202a207e5
Workaround problems with interactions when running Taverna Server inside
Docker inside a VM.
The networking configuration in that situation is non-trivial, and
beyond what it is practical to auto-detect. This means that at least it
is possible to fix the problem by just adjusting a properties file,
instead of having to edit the bean configuration file directly.

Show diffs side-by-side

added added

removed removed

Lines of Context:
75
75
taverna.interaction.port:                       none
76
76
taverna.interaction.webdav_path:        none
77
77
taverna.interaction.feed_path:          none
 
78
# Set to the comma-separated list of IP *addresses* that interaction
 
79
# self-connections can come from. In normal network configurations, this is
 
80
# auto-detected. With complex VM setups, we can end up needing guidance.
 
81
taverna.interaction.trusted_ip_addresses:       127.0.0.1