chowdhary987

AWS new instance type which are full HVM, utilizes NVMe interface for accessing the EBS volume, instead of paravirtual driver on HVM AMI.

With the following instances, EBS volumes are exposed as NVMe block devices: C5, C5d, i3.metal, M5, and M5d. The device names are /dev/nvme0n1, /dev/nvme1n1, and so on. The device names that you specify in a block device mapping are renamed using NVMe device names (/dev/nvme[0-26]n1).

Please type sudo lsblk to get the device listing e.g. when I have created another volume and attached as /dev/sdb, it is being shown as nvme1n1.

NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
nvme0n1 259:1 0 30G 0 disk
nvme0n1p1 259:2 0 1M 0 part

chowdhary987

Auto start for Supervisord at AWS

Install commands

$ sudo mv supervisor /etc/init.d
$ sudo chkconfig --add supervisor
$ sudo chkconfig supervisor on

chowdhary987

sudo wget http://repos.fedorapeople.org/repos/dchen/apache-maven/epel-apache-maven.repo -O /etc/yum.repos.d/epel-apache-maven.repo
sudo sed -i s/\$releasever/6/g /etc/yum.repos.d/epel-apache-maven.repo
sudo yum install -y apache-maven
mvn --version

chowdhary987

#!/bin/bash
###############################################
# To use: 
# https://raw.github.com/gist/2776351/???
# chmod 777 install_postgresql.sh
# ./install_postgresql.sh
###############################################
echo "*****************************************"
echo " Installing PostgreSQL"
echo "*****************************************"

chowdhary987

#sudo pip3 install mysqlclient fails with mysql_config not found
sudo apt-get install libmysqlclient-dev
#without pip3 it will not going to work for python3
sudo pip3 install mysqlclient

# to run django migration
python3 manage.py migrate

chowdhary987

Virtual Hosts on nginx (CSC309)

When hosting our web applications, we often have one public IP address (i.e., an IP address visible to the outside world) using which we want to host multiple web apps. For example, one may wants to host three different web apps respectively for example1.com, example2.com, and example1.com/images on the same machine using a single IP address.

How can we do that? Well, the good news is Internet browsers

chowdhary987

version: '2.1'
services:
  kong-migrations:
    image: "${KONG_DOCKER_TAG:-kong:0.14.1-alpine}"
    command: kong migrations up
    depends_on:
      db:
        condition: service_healthy
    environment:
      KONG_DATABASE: postgres

chowdhary987

daemon off;
#error_log /dev/stdout debug;
error_log /dev/stdout info;
events {

}
http {
        access_log /dev/stdout;

chowdhary987

# Official framework image. Look for the different tagged releases at:
# https://hub.docker.com/r/library/node/tags/
image: node:6

before_script:
  - npm install

# This folder is cached between builds
# http://docs.gitlab.com/ce/ci/yaml/README.html#cache
cache:

chowdhary987

trigger:
  branches:
    include:
    - master
    - releases/*
    exclude:
    - refs/tag/*


pool: