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
{{ message }}
This repository has been archived by the owner on Jan 23, 2025. It is now read-only.
All configurable folder paths and container volumes must be explicitly documented in the README.
Non-existent folder paths that the application depends on must be properly created as part of the build/Dockerfile steps i.e. mkdir -p /path/to/folder.
Tasks
These paths and similar paths1 referenced in configuration files used by tc-website should exist and be properly accessible from the docker image.
Requirements
All configurable folder paths and container volumes must be explicitly documented in the README.
Non-existent folder paths that the application depends on must be properly created as part of the
build/Dockerfile
steps i.e.mkdir -p /path/to/folder
.Tasks
These paths and similar paths1 referenced in configuration files used by
tc-website
should exist and be properly accessible from the docker image.ApplicationServer.properties
BASE_DIR
path to thetc-website
JSPs.applicationContext.xml
/home/tc/jboss-4.0.4.GA/server/all/conf/template.txt
2/mnt/apache/tcdocs/i/m
/mnt/apache/tcdocs/i/m
1Do a regex search to find folder paths in other configuration files.
2You can ignore folder paths that appear to no longer be used.
In most cases, there should be no changes to the configuration files themselves, to be consistent with the current paths used by the VM environment.
The text was updated successfully, but these errors were encountered: