LIBDRUM-915. Updated docker-compose.yml to support VS Code debugging #241
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
In DSpace 7.6.2, the back-end was run using the Tomcat “catalina.sh”
script, which automatically included the “JPDA_OPTS” environment
variable, if present in the shell.
With the switch to using a Spring Boot embedded Tomcat server, the
Tomcat server is started by a “java” command, instead of the
“catalina.sh” script.
Modified the “docker-compose.yml“ to use the “JPDA_OPTS” environment
variable when starting the DRUM back-end, i.e. changed:
```yaml
entrypoint:
...
java -jar /dspace/webapps/server-boot.jar --dspace.dir=/dspace
```
to
```yaml
entrypoint:
...
java $${JPDA_OPTS} -jar /dspace/webapps/server-boot.jar --dspace.dir=/dspace
```
The use of the ${{...} was suggested by https://stackoverflow.com/a/65564161
Updated the “DockerDevelopmentEnvironment.md” document to reference the
“JPDA_OPTS” environment variable, instead of the non-existent
“JAVA_TOOL_OPTIONS” environment variable.
https://umd-dit.atlassian.net/browse/LIBDRUM-915
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In DSpace 7.6.2, the back-end was run using the Tomcat “catalina.sh” script, which automatically included the “JPDA_OPTS” environment variable, if present in the shell.
With the switch to using a Spring Boot embedded Tomcat server, the Tomcat server is started by a “java” command, instead of the “catalina.sh” script.
Modified the “docker-compose.yml“ to use the “JPDA_OPTS” environment variable when starting the DRUM back-end, i.e. changed:
to
The use of the ${{...} was suggested by https://stackoverflow.com/a/65564161
Updated the “DockerDevelopmentEnvironment.md” document to reference the “JPDA_OPTS” environment variable, instead of the non-existent “JAVA_TOOL_OPTIONS” environment variable.
https://umd-dit.atlassian.net/browse/LIBDRUM-915