Please enable JavaScript.

Coggle requires JavaScript to display documents.

Provision New Ubuntu Server For App (Test Node App (Install Node (NVM)…

- - - - Select Generic Deployment => Automatic
      - Add the following Script for Deployment:
        //install PM2
        
        npm install -g pm2
        // Add this server as a known host
        
        ssh-keyscan -p 22 -H droplet-ip-address >> ~/.ssh/known_hosts
        //Run the deployment command
        pm2 deploy ecosystem.json production
      - This will provide a private key file for - copy it to clipboard
        cat ~/.ssh/semaphoreci_id_rsa | pbcopy
      - Simulate semaphoreci to test
        
        ssh -i ~/.ssh/semaphoreci_id_rsa semaphoreci@droplet-ip
        
        Shortcut
        
        1) nano ~/.ssh/config
        2) Enter
        Host semaphoreci-droplet
        Hostname droplet-ip-address
        User semphoreci
        ForwardAgent yes
        Port 22
        IdentityFile ~/.ssh/semaphoreci_id_rsa
        Then just run ssh semaphoreci-droplet
      - Add Github Deployment Key
        
        1) SSH into droplet
        2) Create a new SSH Key pair
        cd ~/.ssh
        ssh-keygen -t rsa -b 4096
        
        3) Go to Github => Settings and under "Deploy Keys" add a deployment key - give it write access and paste in id_rsa.pub
        
        Test it works - on remote server
        
        ssh -T git@github.com => should say success
- - - - iptables -t nat -I PREROUTING -p tcp --dport 80 -j REDIRECT --to-ports 3000
      - apt-get install iptables-persistent - to run even when server reboots
- - - - Long way
        
        3) sudo apt-get install redis-server
        
        4) redis-benchmark -q -n 1000 -c 10 -P 5
        
        5) source ~/.profile
        
        2) sudo apt-get update
        
        1)sudo add-apt-repository ppa:chris-lea/redis-server
      - Short way
        
        1) sudo apt-get update
        sudo apt-get upgrade
        
        2) sudo apt-get -y install redis-server
        
        3) Check its running:
        sudo service redis-server status
        Or start the command-line interface:
        redis-cli or even start the server: redis-server
    - - Check netstat where redis-server is listening and on what port:
        sudo netstat -naptu | grep LISTEN
      - Restart
        
        sudo service redis-server restart
      - Benchmarking
        
        redis-benchmark => will run benchmarking on redis
    - - Config file located at:
        /etc/redis/redis.conf
      - Configure a server to be redis-server/cache for a number of other servers - in the redis.conf file change the:
        
        bind 127.0.0.1 with
        
        bind 0.0.0.0
        
        Check where Redis is now listening: sudo netstat -naptu | grep LISTEN
        
        redis will be listening on all interfaces on port 6379
    - - Default Redis is not secure - it assumes that it runs on a secure environment - therefore don't expose Redis directly to the internet of in general
      - Set up a Firewall
        
        UFW or iptables
      - Set up a password
        
        In redis.conf file (/etc/redis/redis.conf) find the line:
        
        #requirepass foobared
        
        Replace foobared with your own password and uncommet it
        
        Restart the server - sudo service redis-server restart
        
        redis-cli
        
        enter PING to see if requires password
        
        enter AUTH <password> to use redis
        
        test with PING again and should get PONG back
      - Disable dangerous commands
        
        In redis.conf under SECURITY
        
        rename-command CONFIG 123aqCNFGG
        
        Disable: rename-command CONFIG ""
- - - - Need to give low privilege user read and write access to the var/www/ directory on the server
      - This directory is where pm2 deploys
    - - SSH into remote sever as root
        
        create the folder
        sudo mkdir /var/www
      - Add permissions to created user:
        
        sudo adduser semaphoreci wwww-data
      - Change ownership of the folder and its files recursively
        sudo chown -R www-data:www-data /var/www
      - Grant the group read and write permissions
        
        sudo chmod -R g+wr /var/www
      - Test - ssh in remote as low privilege user and try to run
        
        touch /var/www.test.txt => should let you create a blank text file
  - - - pm2 deploy ecosystem.json production setup
        
        pm2 deploy ecosystem.json production
      - Check if up at http://<IPADDRESS:3000>
    - - 1) SSH into droplet
        2) pm2 startup ubuntu
        3) Above command will give you an output which need to run as user with root access
        3) Re-enter droplet as root and paste output
        
        ssh root@droplet-ip-address
        #paste output and run it here
      - 4) Save the current processes to automatically restore them if server reboots or something happens - to do this make sure there is a PM2 service to save on remote server:
        
        pm2 status
        
        If processes appear continue
      - 5) Above ok - run this command as user to restore processes:
        
        pm2 save
      - To test sudo reboot on remote server - SSH back into it and run pm2 status to show its running
      - Push changes to github repo and changes will automatically takes place after going through semaphoreCI
    - - Get Personal Access Token from Github from Settings => Token and give control of private repos
      - Copy Token then paste into ecosystem.json file under repo as follows:
        https://<GITHUBTOKEN>@github.com/username/repo.git
    - - pm2 deploy production => command to deploy codebase (after saving files to Github)
      - If don't want to store Github changes and deploy:
        pm2 deploy production --force
  - - - Anything above 10-20% means get another server (expand vertically)