sahilsk

#!/bin/bash
#### Source : https://vincent.composieux.fr/article/install-configure-and-automatically-renew-let-s-encrypt-ssl-certificate

WEB_SERVICE='nginx'
CONFIG_FILE='/usr/local/etc/le-yourdomain-webroot.ini'
LE_PATH='/opt/letsencrypt'
EXP_LIMIT=30;

if [ ! -f $CONFIG_FILE ]; then
        echo "[ERROR] config file does not exist: $CONFIG_FILE"

sahilsk

# vim: filetype=upstart

env UWSGI_BIN=/home/ubuntu/www/example_app/current/venv/bin/uwsgi
env PYTHONPATH=/home/ubuntu/www/example_app/current
env NEW_RELIC_CONFIG_FILE=/etc/newrelic/newrelic.ini
env NEW_RELIC_ADMIN=/usr/local/bin/newrelic-admin

expect fork
umask 0000

sahilsk

log_format elb_log '$proxy_protocol_addr - $remote_user [$time_local] ' '"$request" $status $body_bytes_sent "$http_referer" ' '"$http_user_agent"';

server {
    listen 80 proxy_protocol;
    listen [::]:80  proxy_protocol;
    server_name localhost;
    access_log  /var/log/nginx/elb-access_http.log elb_log;
    location / {
      root   /var/www/html;
      rewrite ^(.*)$ https://$host$1 permanent;

sahilsk

Instructions

Export

• Create tunnel

sahilsk

---
# file  docker/tasks/main.yml

- name: run apt-get update
  apt: update_cache=yes
  sudo: yes

- name: install required packages
  apt: name="linux-image-generic-lts-trusty" state="present"
  sudo: yes

crunchie84

install the ELK stack on an ubuntu-x64 machine on Azure

This guide has been revised 06-03-2015. Start with a clean ubuntu 14.04LTS-x64 machine and get it updated

sudo su
apt-get update && apt-get dist-upgrade
reboot

obolton

AWS ELB with Node.js and WebSockets

This assumes that:

• You are using Nginx.
• You want to accept incoming connections on port 80.
• Your Node.js app is listening on port 3000.
• You want to be able to connect to your Node.js instance directly as well as via the load balancer.

####1. Create load balancer

masteinhauser

#!/bin/bash -x                                                                                                                                                                                                                                                                   
                                                                                   
#DEBUG="-debug"                                                                    
VM=`echo ${1} | sed 's/.json//g'`                                                  
                                                                                   
PACKER=`which packer`                                                              
                                                                                   
rm -rf output-${VM}                                                                
                                                                                   
${PACKER} build ${DEBUG} ${VM}.json                       

pablitoc

##Install AWS CLI Tools##

1. Install AWS CLI Tools. You can also use the EC2 API Tool if you are more comfortable with them. But this write-up uses the EC2 CLI.
2. Create a user via Amazon IAM or download the security accessID and securitykey you will need it to query Amazon CLI.
3. using Terminal cd into .aws directory cd ~/.aws edit or create new file named config paste the following contents inside.
   `[default]`
   `aws_access_key_id = ACCESS_ID`
   `aws_secret_access_key = SECRET_ID`
   `output = json OR bson OR text`
   `region = PREFERRED_AWS_REGION`

Save the file as "config"

yeukhon

Vagrant crash course

This is a 5-minute crash course to start using vagrant. We will host our vagrant files in /home/USER/vms. That's my convention working with many vagrant machines.

Minute 0: Get vagrant and virtulabox

vagrant: https://docs.vagrantup.com/v2/installation/

virtualbox: https://www.virtualbox.org/wiki/Downloads