![]() You can now access your installation through your marathon-lb node. We keep “ since I don’t know the final service port upfront (rocket.chat will ask to change the URL after accessing it the first time, you can set it already to your final external URL if you know it upfront.įinalize the deployment and watch it starting □Īfter the setup has finished you can check the “servicePort” from the rocket.chat service to know which port you need on your loadbalancer. In the networking section I use the “Virtual Network” and define the default port 3000 to be mapped for external accessįor observing the containers I define a simple health check for the login pageįinally I define the required environment variables (PORT, ROOT_URL, MONGO_URL, MAIL_URL) and the HAPROXY_GROUP for our external access. With this in formation we can now deploy the rocket.chat container as a single service.ĭefine the basic image (rocketchat/rocket.chat:latest) and it’s resources, I assign 4 CPUs and 1GB of memory, otherwise I didn’t get this running Step 3: Setting up your Rocket.Chat Admin account On accessing your chat-server URL for the first time, follow the on-screen instructions until you have claimed your site as admin. We find that in the “Configuration” section of the mongoDB service Now, you can start the Rocket.Chat instance: docker-compose up -d Access the Rocket.Chat server domain specified in the configuration using your domain URL. To continue we have to lookup the “Load Balanced Address” of the mongoDB installation, so we can provide the correct connection string. The rocket.chat team provided a ready to use docker image which we can utilize: Start the installation by clicking “Review & Install” and on “Install” in the following window, you can monitor the process in the service overviewĪs soon as this has finished we can continue with rocket.chat itself. For the POC I will just keep the default values If you want to go for production should also update the “Username” and “Password” in the section “database”. ![]() I want to run the whole setup in a group called “rocket.chat” so I update the service name to contain also the group-nameĭuring testing I noticed that the default “CPU” value is a bit low, so we will increase this to at least 2 can get the ports mapped for these services by checking docker-compose ps. MongoDB is available in the default “Universe” repository which comes with DC/OS, which makes it very easy for us to setup a single instance for testing (if you want to go for production you should use here a full replicaset!)Ĭhoose “mongodb” from the package repository for installation You should have either a private RocketChat or Slack channel that was set up. Rocket.chat has one simple requirement, which is mongoDB, which we have to install first. You need a up and running DC/OS Cluster with at least one instance of “Marathon-LB” nothing else is needed in first step.īy the end of this we want to have a running rocket.chat instance including its requirements on DC/OS behind our “Marathon-LB” loadbalancer. Warning: This is example is not suitable for production use since it does not persist its data! Plesk Onyx has now a docker installation and Nginx proxy docker rule generator built in, that doesnt support adding custom directives. ProxyPassMatch ^/sockjs/(.*)/websocket ws://127.0.0.In this post I will quickly describe how to setup rocket.chat on DC/OS, which I used for a simple proof of concept. Header always set Strict-Transport-Security "max-age=15768000 preload" SSLCipherSuite EECDH+AESGCM:EDH+AESGCM:AES256+EECDH:AES256+EDH env file: docker-compose.yml version: 3 services: nginxb: image: nginx:latest. SSLCertificateChainFile /etc/apache2/ssl/intermediate.crt ports: - '6381:6380' Finally, load all the services in the docker-compose.yml file using the. SSLCertificateKeyFile /etc/apache2/ssl/cert.private SSLCertificateFile /etc/apache2/ssl/cert.public Create oplogger user with rights on local oplog database: db.createUser(/access-chat.log combined Today I was playing with Rocket.Chat, a neat open source web chat platform / framework with a lot of useful features.you can set a env var called INSTANCE_IP to set a private IP which an instance can talk to each other Both instances will need to have access to each other.Use a replica set mongodb because rocket.chat needs oplog tailing for multi-instances.A reverse proxy able to proxy requests to both instances.This guide shows you how to install Rocket.Chat as HA with mongodb replicaset as backend.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |