From 6a847fb9282983b1b876e626962b16e3c2400826 Mon Sep 17 00:00:00 2001 From: "caue.lugli" <54319415+cauelugli@users.noreply.github.com> Date: Thu, 27 Jan 2022 22:37:23 -0300 Subject: [PATCH 1/2] README.md - Corrected typos and deprecated certbot On 'Deployment Ubuntu 20.04' part, at the very end, fixed the deprecated certbot package instruction --- README.md | 19 +++++++++---------- 1 file changed, 9 insertions(+), 10 deletions(-) diff --git a/README.md b/README.md index e7457c2..a127435 100644 --- a/README.md +++ b/README.md @@ -123,7 +123,7 @@ npm start - Wait for QR CODE button to appear, click it and read qr code. - Done. Every message received by your synced WhatsApp number will appear in Tickets List. -## Basic production deployment (Ubuntu 18.04 VPS) +## Basic production deployment (Ubuntu 20.04 VPS) All instructions below assumes you are NOT running as root, since it will give an error in puppeteer. So let's start creating a new user and granting sudo privileges to it: @@ -146,7 +146,7 @@ Update all system packages: sudo apt update && sudo apt upgrade ``` -Install node and confirm node command is available: +Install node, and confirm node command is available: ```bash curl -fsSL https://deb.nodesource.com/setup_14.x | sudo -E bash - @@ -231,7 +231,7 @@ sudo npm install -g pm2 pm2 start dist/server.js --name whaticket-backend ``` -Make pm2 auto start afeter reboot: +Make pm2 auto start after reboot: ```bash pm2 startup ubuntu -u `YOUR_USERNAME` @@ -250,7 +250,7 @@ cd ../frontend npm install ``` -Edit .env file and fill it with your backend address, it should look like this: +Create frontend .env file and fill it ONLY with your backend address, it should look like this: ```bash REACT_APP_BACKEND_URL = https://api.mydomain.com/ @@ -337,14 +337,14 @@ server { } ``` -Create a symbolic links to enalbe nginx sites: +Create a symbolic links to enable nginx sites: ```bash sudo ln -s /etc/nginx/sites-available/whaticket-frontend /etc/nginx/sites-enabled sudo ln -s /etc/nginx/sites-available/whaticket-backend /etc/nginx/sites-enabled ``` -By default, nginx limit body size to 1MB, what isn't enough to some media uploads. Lets change it to 20MB adding a new line to config file: +By default, nginx limit body size to 1MB, which isn't enough for some media uploads. Lets change it to 20MB, adding a new line to config file: ```bash sudo nano /etc/nginx/nginx.conf @@ -362,17 +362,16 @@ sudo nginx -t sudo service nginx restart ``` -Now, enable SSL (https) on your sites to use all app features like notifications and sending audio messages. A easy way to this is using Certbot: +Now, enable SSL (https) on your sites to use all app features like notifications and sending audio messages. An easy way to this is using Certbot: Install certbot: ```bash -sudo add-apt-repository ppa:certbot/certbot +sudo snap install --classic certbot sudo apt update -sudo apt install python-certbot-nginx ``` -Enable SSL on nginx (Fill / Accept all information asked): +Enable SSL on nginx (Fill / Accept all information required): ```bash sudo certbot --nginx From d409aa28c8af773d70d9044ca79aa34c47c355c8 Mon Sep 17 00:00:00 2001 From: "caue.lugli" <54319415+cauelugli@users.noreply.github.com> Date: Fri, 28 Jan 2022 15:12:45 -0300 Subject: [PATCH 2/2] Update README.md --- README.md | 4 ---- 1 file changed, 4 deletions(-) diff --git a/README.md b/README.md index a127435..1f13b45 100644 --- a/README.md +++ b/README.md @@ -16,10 +16,6 @@ Frontend is a full-featured multi-user _chat app_ bootstrapped with react-create **NOTE**: I can't guarantee you will not be blocked by using this method, although it has worked for me. WhatsApp does not allow bots or unofficial clients on their platform, so this shouldn't be considered totally safe. -## Motivation - -I'm a SysAdmin, and in my daily work, I do a lot of support through WhatsApp. Since WhatsApp Web doesn't allow multiple users, and 90% of our tickets comes from this channel, we created this to share same whatsapp account cross our team. - ## How it works? On every new message received in an associated WhatsApp, a new Ticket is created. Then, this ticket can be reached in a _queue_ on _Tickets_ page, where you can assign ticket to your yourself by _aceppting_ it, respond ticket message and eventually _resolve_ it.