By default, the logs are located within the Docker container at /app/logs
and in order to be able to access the logs from the container, you will first need to mount the /app/logs
directory at startup using the volume (-v) parameter.
Example Docker command:
docker run --rm --env ACCEPT_EULA=YES --env LICENSE_KEY=$MY_LICENSE_KEY --volume /local/path/to/logs:/app/logs --workdir /app --publish 21412:21412 --name prizmdoc-editor accusoft/prizmdoc-editor:latest
You'll just need to do the following:
- Add the license key,
- Modify the path you would like to use for the volume
- Use the appropriate version tag of the PrizmDoc Editor version image you want to use in production.
Note: For more information about the parameters used above, please see the "Running the Editor Server" section of our PrizmDoc Editor documentation.
We don't recommend deleting the log files outright, as that could cause the logging process to fail and potentially lead to application crashes. Instead, you should use the truncate command (shown below) to safely clear the log files. This will preserve the file handles while reducing the file size to zero.
Ideally, you would create a periodic task on the Docker Host to run this command every 15 minutes (or at your preferred interval):
truncate -s 0 /local/path/to/logs/*.log
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article