so, first thing is to get a swapfile up and running. we will close this port later.Įc2 micros only come with one gig of ram out of the box and no swap partition, which is fine for hello-world calibre stuff, but rocketchat wants ram. We will also want to have a domain name pointing to our ec2, so fire up route53 and do that, and port 3000 open on our firewall. this is slim at the best of times, but rocket and mongo eat up disk space, so we're going to give ourselves a 20gb disk. The default disk size for t2.micros is 8gb. if you plan on this being used in production, an elastic ip is highly recommended. Fix importer agent being added as a member of every imported room. for the detail-oriented, that's ami-03d5c68bab01f3496.Įnsure that you have a public ip address. 6.2.4 Latest 2 2 5 Engine versions Node: 14.21.3 NPM: 6.14.17 MongoDB: 4.4, 5.0, 6.0 Apps-Engine: 1.39.1 Bug fixes Imported messages are not displayed ( 29485) Fix issue with imported messages not being displayed in the room. This is going to be on an ec2 t2.micro running ubuntu 20.04. In this fly-over we will be deploying rocket chat backed by mongodb 5.0 on an ec2 t2.micro running ubuntu 20.04 and we'll be putting it behind an nginx reverse proxy so we can serve easily over ssl. if you're looking to include live chat in your next project or are just looking for a roll-your-own slack replacement, it's a good candidate. The output will be similar to the following: Replace /var/snap/rocketchat-server/1195/Caddyfile with your own to customize reverse proxyĮdit the file with your favourite editor (such as Vim or Nano).Rocketchat is a slick chat server that you can deploy yourself. (36)Tag Scanner (1)Text (3)Text-to-speech (12)Time (1)Transport (31)Update (23)Utility (31)Vacuum (10)Voice (21)Water Heater (19)Weather (30)Other (40). Before we can change it’s settings, we need to generate a config file. RocketChat uses Caddy as it’s HTTP server. You can use the same systemctl commands above to manage it. The MongoDB database that powers your RocketChat server is ran by the service. We can also restart the server directly, instead of stopping and starting it: To start the server again, we can run the above command, replacing stop with start: Loaded: loaded (/etc/systemd/system/ enĪctive: inactive (dead) since Sun 00:54:25 EST 1min 15s agoĪs you can see, the Active line now says inactive. Now our server will be inaccesible, and if we check it’s status: - Service for snap application rocketcha The Active line tells us that the service is running. Loaded: loaded (/etc/systemd/system/ enabled vendor preset: enabled)Īctive: active (running) since Sat 23:36:30 EST 1h 13min ago The output will look something like: - Service for snap application rocketchat-server.rocketchat-server You can check the status of the RocketChat server service with the following command: By default, they start on boot and automatically restart on failure. Your RocketChat server is managed through systemd services. Now, let’s move on to server configuration! Managing the RocketChat service If you click on your name at the top-left, you will open a menu where you can change your status (online, away, etc), change your account settings, or (if you’re an admin), change server administration settings. Other featuresįrom the right sidebar, you can also change notification preferences and see the file list for a channel. Stars and pins can be accessed from the right sidebar. You can also star a message to save it for later, or, with the proper permissions, pin it to the channel to save it for everyone. If you sent the message (or you have the proper permissions), you can edit or delete it. You may add attachments (files, video and audio), emoji, and apply basic formatting.Īll messages have a menu that can be accessed by hovering over them and clicking on the series of dots that appear over it at the top-right corner. Messages can be sent (quite intuitively) by typing in the chatbar and pressing enter. Past direct messages will appear on the left sidebar, under the list of channels. You may send direct messages to team members by opening the member list (located on the right sidebar), clicking on someone’s name and clicking on the Conversation button. Creating a channel 802×640 39 KB Sending direct messages
0 Comments
Leave a Reply. |