summaryrefslogtreecommitdiffhomepage
diff options
context:
space:
mode:
authorKasra Bigdeli <[email protected]>2021-10-27 07:09:45 -0700
committerKasra Bigdeli <[email protected]>2021-10-27 07:09:45 -0700
commitf0744722bc7e357bd0b3db9feb4279b1593b63d2 (patch)
tree6fb0e1c78d0fe5e8b59b8382f97ccb230ceaab37
parent128d47ef232bbd3bbfc76b6994fa64e57be2eb35 (diff)
downloadcaprover-one-click-apps-f0744722bc7e357bd0b3db9feb4279b1593b63d2.tar.gz
caprover-one-click-apps-f0744722bc7e357bd0b3db9feb4279b1593b63d2.zip
Added min req for Zammad
-rw-r--r--public/v4/apps/zammad.yml11
1 files changed, 9 insertions, 2 deletions
diff --git a/public/v4/apps/zammad.yml b/public/v4/apps/zammad.yml
index d1e5665..4460541 100644
--- a/public/v4/apps/zammad.yml
+++ b/public/v4/apps/zammad.yml
@@ -1,8 +1,15 @@
captainVersion: 4
caproverOneClickApp:
instructions:
- start: >-
- Zammad is a web-based, open source user support/ticketing solution.
+ start: |-
+ Zammad is a web-based, open source user support/ticketing solution. For Zammad and a database server like PostgreSQL we recommend at least:
+
+ - 2 CPU cores
+ - 4 GB of RAM (+4 GB if you want to run Elasticsearch on the same server)
+ - For optimal performance up to 40 agents:
+ - 4 CPU cores
+ - 6 GB of RAM (+6 GB if you want to run Elasticsearch on the same server)
+
end: >
Zammad is deployed and available.
IMPORTANT: It will take up to 5 minutes for Zammad to be ready. Before that, you might see a 502 error page.