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



##########
File path: server/apps/distributed-app/helm-chart/james/doc/checklist.md
##########
@@ -0,0 +1,45 @@
+# 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.
+
+- [ ] Create a namespace for James deployment.
+- [ ] The right image container used for James
+- [ ] Have an appropriate email domain (Contact your Domain Service Provider)
+- [ ] Deploy Helm RabbitMQ package
+- [ ] Cassandra nodes deployed 
+- [ ] Put valid Cassandra keyspaces in the configuration
+- [ ] ElasticSearch nodes deployed
+- [ ] LDAP deployed 

Review comment:
       MUST HAVE
   ```
   - [ ] Setup RabbitMQ and create James user in it.
   - [ ] Create a Kubernetes namespace for James deployment.
   - [ ] A `distributed` version of James image.
   - [ ] An ObjectStorage compatible with S3 APIs.
   - [ ] Configure JWT keys, keystores.
   - [ ] Adding the proper `mailetcontainer.xml` file with other conf files in 
James Helm package
   ```
   OPTIONAL
   ```
   - [ ] Cassandra nodes deployed.
   - [ ] Put valid Cassandra keyspaces in the configuration.
   - [ ] Have an appropriate email domain (Contact your Domain Service Provider)
   - [ ] Create your Domain SPF and DKIM Record. See document 
[here](https://james.apache.org/howTo/)
   - [ ] ElasticSearch nodes deployed.
   - [ ] LDAP deployed.
   ...
   ```
   




-- 
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