Are we sure we want to do this? I think this will be a support nightmare. Not to mention hurting the docker purist in me so very badly. Multiple processes in a docker container kind of defeats the whole purpose of docker and containerization.

[edit] Now I get the purposed. Testing... and a way to quickly bring up and preview

I am also more the „one container, one process“ guy. What does the addition of mongo solve or improve? I would stick with the docker-compose way of combining Rocket.Chat and mongo containers.

I just edited my reply. But talked a bit, the goal is for quick and easy way to preview Rocket.Chat on-premises. Also for use in testing. For sure not an alternative way to run a production system.

Can we add a README.MD and a BIG comment on the docker file that this is for preview and automated testing only, and not meant for production environments?

Yes this would help a ton! I wonder if we want to make it super easy... Should we go so far as to set it up with a user so they just login and start using? Helping re-inforce(hopefully) that it's a preview?

@engelgabriel is on the money here.

There really needs to be a large warning everywhere possible that this is for previewing and not production.

Might be worth putting this in the container as a start up banner similar to what I've done for the rocket.chat hubot container

Ooooh! We already have a bash script included. Would be awesome to have ascii text saying something like:

Rocket.Chat Preview(in sweet ascii text)

This image is for testing purposes only. Please do not attempt to use in production. For deploying a production ready install please see: https://rocket.chat/docs/installation/

@geekgonecrazy can you add this sweet ascii text to .docker-mongo/entrypoint.sh?

We need to define if this will be a tag like rocketchat:0.61.0-preview or if this will be another image (I prefer this) like rocketchat-preview:0.61.0

@JSzaszvari what did you use to generate that text for hubot?

@rodrigok I agree. It should be a completely separate image. Treat it as completely separate thing so it's always clear it's not production with every little detail 😁

I agree with @geekgonecrazy , it should be a completely separate image

As per suggestions, I've added the Rocket.Chat Preview banner.

I've also included the new docker image on CI as rocket.chat.preview .. it will have the same tags as the official one