The folders are volumes for your containers and hold the state so that your server will persist across reboots/containers. A Note About StateĪfter having run the docker-compose up command, rocket chat will create the following folders from wherever you ran the command (which should be in $HOME if you used my instructions). One of the first things you may need to do is look through the settings and configure SMTP and email confirmation for registration. If you wait patiently enough, eventually you will see this screen and you're good to go. You may also see messages in the CLI from when you ran docker-compose with error messages from hubot_1. The first time you register, you will be stuck on this screen for a looooong time. Register yourself as the first user, which does not require email authentication and will default you to being an administrator. There is no default admin account at the time of writing this tutorial. Navigate to the server in your web browser. Start rocket chat (both the mongo database container and the application container) by running the command below: docker-compose up Go through it and change all instances of to your server's IP or hostname. MONGO_OPLOG_URL=mongodb://mongo:27017/local ROOT_URL= - MONGO_URL=mongodb://mongo:27017/rocketchat It should look similar to below (although it keeps changing). mv Rocket.Chat/docker-compose.yml $HOME/. git clone Ĭlone the docker-compose file up to your home and remove all the other content (we dont actually wan the code and this simplifies the volumes later). Ssl on # check letsencrypt's certbot for these =) ssl_certificate /etc/nginx/certificados/certificado.crt # you need to create these, use self-signed our a free CA ssl_certificate_key /etc/nginx/certificados/chave_privada.Firstly, install docker and then install docker compose if you haven't already.Ĭlone the RocketChat repository and navigate to within the source code. Listen 443 # lets protect our data transactions server_name Įrror_log /var/log/nginx/ Listen 80 #lets take everything that comes in http 80 and throw to https 443 server_name Ip_hash #makes it sticky, users request allways returns to the same server server r1. # remember setting ip address for these guys in the /etc/hosts server r2. By the way, we will need 7 servers to this tutorial. Prepare your selfįirst we'll need some tools to start, get inside your servers and start to set a health enviroment. Taking all that in consideration, I won't spoiled out all your fun in this tutorial, but I promise to answer the comments =). YEP: You probably won't need one, you can use the server for free and it is a awesome server, but if want to have your own internal videoconference tool running inside your NAT, thats the way to go.Īfter this tutorial you will need to explore the Rocket Power, learn some good confs, set up live chat in your website, maybe do some webhooks integrations with gitlab and github, and probably you will want to checkou the new Hubot integration. TOUGHT: You could do this with apache or other apps just for fun, if you do, please let me know what you find out. A light weight Load Balancer and Reverse Proxy with NGINX TIP: I will be installing a Virtual Machine server, but if you want to be in state of art, you will check the Docker's Swarm architeture, just to get inspired.ģ. We will install a good and neet Rocket.Chat server INFO: If you are planning to have a realy big number of users, you might want to take a look at MongoDB Sharding tutorial too.Ģ. Let's set up a MongoDB replicaSet with 3 servers Some tips and good pratices that you'll found here can be used in other architetures too, but remember that if you are not going to need a HA architeture, you might wanna use the Docker image to save some precious time.ġ. This is a detailed tutorial about how to install Rocket.Chat in a High Availability (HA) architeture, over Debian 8.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |