Category: Charlesreid1


Charlesreid1.com Stack

Posted in Charlesreid1

permalink

This post is a preview of a series of posts to come, which will document the process of containerizing the entire charlesreid1.com website.

We will run through a lot of different moving parts and how to get them all working:

  • Multiple domains and subdomains pointing to different services
  • Docker pod for all services
  • Nginx + SSL
  • Reverse proxies via nginx
  • Apache + MySQL + MediaWiki
  • phpMyAdmin
  • Gitea
  • Configuration files under version control
  • Data managed with backup/restore scripts and cron jobs
  • Static content under version control
  • Files server
  • REST API
  • Management LAN

All of the code for doing this is in docker …



Tags:    web    git    pelican    nginx    ssl    apache    mediawiki    javascript    php    docker    security   


AWSome Day Seattle Notes: Part 2: Networking, Security, and Miscellany

Posted in Charlesreid1

permalink

These notes are also available on git.charlesreid1.com here or in https://git.charlesreid1.com/charlesreid1/aws.

AWSome Day Notes: Part 2: Networking, Security, and Miscellany

Following are some notes from Amazon's AWSome Day (Tuesday, February 27, 2018).

Nomenclature

Elastic: You'll see the word "elastic" on a lot of Amazon's services. The "elastic" concept refers to a service that is able to handle huge increases in traffic (Pokemon Go - number of users grew orders of magnitude faster/larger than what they designed for).

Virtual Private Cloud (VPC): The AWS equivalent of a virtual private network (VPN). A VPC is …



Tags:    aws    cloud    vpc    containers    data engineering   


AWSome Day Seattle Notes: Part 1: The Basics

Posted in Charlesreid1

permalink

These notes are also available on git.charlesreid1.com here or in https://git.charlesreid1.com/charlesreid1/aws.

AWSome Day Notes: Part 1: The Basics

Following are some notes from Amazon's AWSome Day (Tuesday, February 27, 2018).

EC2 Costs and Scheduling

Cost of a node:

  • Important to understand Amazon's price model: users pay for access, not for hardware
  • Cost of AWS node is cost for on the spot access

Scheduling:

  • If you can anticipate your usage, you can schedule instances in advance, and get a discount
  • Discount of 50% for one-year reservation (if you keep it busy for 6 months …


Tags:    aws    cloud    vpc    containers    data engineering