Mirrored_Repos/docker-atlassian-confluence-server
1
0
Fork 0
mirror of https://bitbucket.org/atlassian-docker/docker-atlassian-confluence-server.git synced 2024-08-30 18:22:16 +00:00
Code Issues Packages Projects Releases Wiki Activity

Merged in DCD-1148-default-to-log-file (pull request #76)

Browse Source 
DCD-1148: Default application logs back to the log files (instead of stdout)

Approved-by: Steve Smith
This commit is contained in:
Adam Brokes 2020-11-24 07:03:45 +00:00
commit f7955bc991
2 changed files with 7 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
Dockerfile
View File

@ -10,7 +10,7 @@ ENV RUN_GID 2002
ENV CONFLUENCE_HOME /var/atlassian/application-data/confluence ENV CONFLUENCE_HOME /var/atlassian/application-data/confluence
ENV CONFLUENCE_INSTALL_DIR /opt/atlassian/confluence ENV CONFLUENCE_INSTALL_DIR /opt/atlassian/confluence
ENV CONFLUENCE_LOG_STDOUT true ENV CONFLUENCE_LOG_STDOUT false
WORKDIR $CONFLUENCE_HOME WORKDIR $CONFLUENCE_HOME

10
README.md
View File

@ -165,11 +165,13 @@ Example:
The Confluence license string. Providing this will remove the need to supply it through the web startup screen. The Confluence license string. Providing this will remove the need to supply it through the web startup screen.
* `CONFLUENCE_LOG_STDOUT` (from Confluence 7.9 onwards) `[true, false]` * *use with caution* `CONFLUENCE_LOG_STDOUT` `[true, false]` (from Confluence 7.9 onwards)
Prior to Confluence version 7.9.0, the log files are stored in the `logs` folder in Confluence home. From version Prior to Confluence version 7.9.0, the log files are always stored in the `logs` folder in Confluence home. From version
7.9.0, the logs are printed to the `stdout` by default. This makes it possible to fetch the log messages 7.9.0, the logs can be printed directly to the `stdout` and don't use the file at all. This makes it possible to fetch the log messages
via `docker logs <CONTAINER_ID>`. You can revert to log into the `logs` folder by setting this variable to `true`. via `docker logs <CONTAINER_ID>`. In this setup we recommend using some log aggregation tooling (e.g. AWS Cloudwatch or ELK stack).
**Beware, if enabled, the support ZIP produced by the Troubleshooting and Support plugin doesn't contain the application logs.**
## Database configuration ## Database configuration