ducnm0711 commented on a change in pull request #718:
URL: https://github.com/apache/james-project/pull/718#discussion_r740029947



##########
File path: 
server/apps/distributed-app/docs/modules/ROOT/pages/helm/checklist.adoc
##########
@@ -0,0 +1,43 @@
+# Checklist
+
+There is some things that you must have before being able to run James on your 
Kubernetes Cluster.
+
+## MUST have
+
+Those are absolutely necessary if you want at least James to start without 
crashing.
+
+- [ ] Setup RabbitMQ and create James user in it.
+- [ ] Create a Kubernetes namespace for James deployment.
+- [ ] A `distributed` version of James image.
+- [ ] Have an appropriate email domain (Contact your Domain Service Provider)
+- [ ] Cassandra nodes deployed.
+- [ ] An ObjectStorage compatible with S3 APIs.
+- [ ] Configure JWT keys, keystores, SPF and DKIM. See document 
[here](https://james.apache.org/howTo/)
+- [ ] Adding the proper `mailetcontainer.xml` file with other conf files in 
James Helm package

Review comment:
       the `mailetcontainer.xml` explain + link to sample is alr in 
`run/run-kubernetes.adoc`
   ```
   === James Configuration
   
   The configuration files proper to James are stored in the Chart 
`james/configs` folder. They are being stored in a `ConfigMap` and then being 
mounted in the James pod at /root/conf path.
   
   If you need to change a conf in James, this is were you need to look at.
   
   For now all configuration files are the same for every deployment, except 
for `mailetcontainer.xml` that has been excluded (see section below).
   
   You can get the template `mailetcontainer.xml` in our 
link:https://github.com/apache/james-project/blob/master/server/apps/distributed-app/sample-configuration/[sample-configuration]
 folder.
   ```




-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to