Steffen Bleul

Jira Image is configured differently. This changed recently: https://github.com/blacklabelops/jira#a-word-about-memory-usage

According to Atlassian documentation they changed the memory configuration also for Confluence: https://confluence.atlassian.com/confkb/how-to-fix-out-of-memory-errors-by-increasing-available-memory-154071.html Can somebody check if either CATALINA_OPTS or JVM_MINIMUM_MEMORY, JVM_MAXIMUM_MEMORY still works? Maybe we will need an issue...

Thank you!

That's very confusing. I find different solutions everywhere. "utf-8", "utf8", "UTF-8". It would be really nice if someone can contribute the correct `create table statement` for postgres.

Copy & paste mistakes.

We have a version reference: - Inside the Dockerfile - Inside the readme.md - Inside the release.sh For a clear solution we should disregard all these references. Anyone in favor...

The github repository is here: https://github.com/blacklabelops-legacy/nginx Do not use this outdated version for https! You have to update the image: Alpine version and Nginx version.

Interesting, I will take a look.

I can verify this in Jira 7.6.0. Still looking for a solution. Simple solution: * Disable caching Wanted solution: * Configurable: Not only size but move cached files outside image...

Already possible you can "hook-in" your own proxy conf, see here: https://github.com/blacklabelops/nginx/issues/30