# this is used to expose the hubot port for notifications on the host on port 3001, e.g. EXTERNAL_SCRIPTS=hubot-help,hubot-seen,hubot-links,hubot-greetings Image: rocketchat/hubot-rocketchat:v0.1.4 MONGO_URL=mongodb://db:27017/rocketchat Also, feel free to suggest a better approach for this problem. If things get confused to you, tell me so I check if there's a mistake, typo or give more info. Note: for didactic and privacy reasons I've changed everything to use and, hope you don't get it wrong. What's going on? What should I do in order to fix these problems and get as many Rocket.Chat instances as I want, each of them being provided in the URL I want? There's no problem in using ports explicitly to access chats (e.g: use :3002 instead, but the later is more desirable).īelow you can see the most relevant files. Follow the prompts, setup the network with DHCP or static as desired. Upon the reboot, click TAB to accept the preselected INSTALL selection. :3000 -> Loads, but seems to be using Rocket.Chat instance / database. Open Remote Console, and perform the BIOS change and Installation: In the BiOS settings, change to the Boot Options tab and move CDROM above Disk.If I try to access the sites, I got the following: Did I misunderstood some key concepts from Docker Compose or it's really not working as expected? I've found that is being initialized in port 3000 according to it's own output, therefore change the property ports in the docker-compose.yml file doesn't seems to be working. The things get weird when works as expected, but no. I'm trying to attach the following ports to each instance: etc/nginx/sites-enabled/chat_example2_comĮverythings was going fine while I have a single Rocket.Chat instance using Docker Compose, but with more instances things get confused. etc/nginx/sites-enabled/chat_example1_com etc/nginx/sites-enabled/www_example2_com etc/nginx/sites-enabled/www_example1_com So you can imagine that I have the following architecture: # Sites content This instance has a Nginx server that serves these sites. Remember that (.) are hosted in the same EC2 instance. What I want to do is somewhat like the following: Note that each of these projects has it's own userbase and is completely isolated from others, thus each Rocket.Chat instance should be isolated too. ProxyPassMatch ^/sockjs/(.*)/websocket ws://127.0.0.I'm developing some projects that are available under the same Amazon EC2 instance (AWS EC2 instance) and I'm trying to create a Rocket.Chat for each of these projects. Header always set Strict-Transport-Security "max-age=15768000 preload" If your Rocket. SSLCipherSuite EECDH+AESGCM:EDH+AESGCM:AES256+EECDH:AES256+EDH edit rocketchatuser, rocketchatpassword, and botname. SSLCertificateChainFile /etc/apache2/ssl/intermediate.crt 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.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 |