git clone [email protected]:YOUR-USERNAME/YOUR-FORKED-REPO.git
cd into/cloned/fork-repo
git remote add upstream git://github.com/ORIGINAL-DEV-USERNAME/REPO-YOU-FORKED-FROM.git
git fetch upstream
git clone [email protected]:YOUR-USERNAME/YOUR-FORKED-REPO.git
cd into/cloned/fork-repo
git remote add upstream git://github.com/ORIGINAL-DEV-USERNAME/REPO-YOU-FORKED-FROM.git
git fetch upstream
For this configuration you can use web server you like, i decided, because i work mostly with it to use nginx.
Generally, properly configured nginx can handle up to 400K to 500K requests per second (clustered), most what i saw is 50K to 80K (non-clustered) requests per second and 30% CPU load, course, this was 2 x Intel Xeon with HyperThreading enabled, but it can work without problem on slower machines.
You must understand that this config is used in testing environment and not in production so you will need to find a way to implement most of those features best possible for your servers.
| const admin = require('firebase-admin'); | |
| const CryptoJS = require("crypto-js") | |
| const firebaseConfig = require('./config/firebase') | |
| const express = require('express') | |
| const cors = require('cors') | |
| const bodyParser = require('body-parser') | |
| const app = express() | |
| app.use(cors()) |
| decrypt(data) { | |
| const ciphertext = data.msg | |
| const key = this.chatService.getPasscode | |
| const bytes = CryptoJS.AES.decrypt(ciphertext, key) | |
| const plaintext = bytes.toString(CryptoJS.enc.Utf8) | |
| console.log(data.msg) | |
| console.log(key) | |
| console.log(bytes.toString(CryptoJS.enc.Utf8)) | |
| return {msg: plaintext} | |
| } |
| const sayHi = (name: string) => { | |
| console.log(`My name is ${name}`) | |
| } |