It’s ok. You can send a meeting request to me (hainguyen@mycollab.com) at Chicago time. Thanks and see you soon.

We don't support the current MyCollab instance but the newer MyCollab. This piece doesn't take a lot of effort, but we keep it with the new version which will be released very soon along with some interesting features such as kanban board. Please be patient!

Thank you for reporting this issue. It has been fixed in the community edition. You can get the latest source on the master branch and deploy on your side. 

You can use the mysql client tool to connect from your ec2 instance to amazon rds, if it can connect then cope the same configurations to mycollab settings.

mysql -h amazonrds -P 3306 -u username -p

it seems the application could not connect to the database. Where do you install the database? do you install the DB in the same or different EC2 instance or the Amazon RDS?

Could you give me the full log, as well as the file application.properties in the folder %MYCOLLAB_HOME%/config?

You don't need to force to use java 8 to build the project. If you review the changeset https://github.com/MyCollab/mycollab/commit/0050d992355928c0ffea44c83ebff4b7827d5967, I make the recompiled the gwt wigetsets and the developers don't need to build it again. It is different than in the past when we want to let developers compile the widget sets by themselves. We don't want to push to git whatever could be generated by tools.

Regarding the error of heap, you can increase the heap size, it is mandatory for the big java project like MyCollab. Hope the below screenshot is helpful

That makes sense! The effort of implementing this is not too much. We can deliver it in the next release (rough estimate is 2-3 weeks from now). The rush of having many changes in the next release made me skeptical into any additional feature, but this feature is fine.

Thank you for this suggestion.

As I can see, now it used the proper vaadin maven plugin 7.7.14. The latest issue seems to come from the gwt project could not be compiled by Java 10. See https://stackoverflow.com/questions/51877006/migrating-a-gwt-2-5-web-app-to-java-10

You should force maven to use Java 8 to compile the java process. By the way, you can get the latest source again, I modified the maven project to recompile GWT assets (by java 8), and developers don't need to make this step and make an error due to the difference of environments.

May not exactly what we did but it is the reference https://www.linode.com/docs/development/java/how-to-deploy-spring-boot-applications-nginx-ubuntu-16-04/.