Christie christiearcus

Web Development Basics

Quick start a new basic web project:

Use this as a cheat sheet for saving time when doing assessments. This is how you construct it from scratch. There are many things out there that can generate stuff for you, but it helps to know how the foundations.

Open iTerm terminal (the default Mac one sucks).
cd ~ to go to your home directory and then pwd to show your location (using finder is also fine if you don't like the terminal).
mkdir sylvia_study and then cd sylvia_study to navigate in to that directory.
git init to initiate the folder as a git repository so that version changes can be seen.

When we refer to 'upstream' in our project, we are referring to the central version (and not our personal forks). By default, when you clone your fork, there will be no reference to the upstream version. But it's necessary to add this, as this allows us to pull the latest changes when pull requests are merged.

To set this up use the following steps:

Check your remote versions on your project:

git remote -v- if you want to look at it in your project code, you can check the config file of the .git folder.

Add the reference to the upstream repository:

There are a couple of issues with our Wordpress deployment.

The EC2 instances running our wordpress site have databases running within them. Each of the databases is keeping state of the app for that instance. If the instance dies, and a new one is started by our ASG, our state will be lost.

To improve this, we can separate our database out from the instance running our app. This means that if our instance dies, our state is safe.

We will need:

A RDS instance to run our MySQL database.
An S3 bucket to store a tarball of our customised Wordpress app (with the correct database access file).

To link a standalone bower component to your local environment, do the following:

in your component shell: bower link. this creates a symlink.
Make sure both servers are running
in your client shell: bower link [name-of-component].
you will have to restart your server any time you want to see the changes locally, as it's only run once on build.

Decorator Pattern

The decorator pattern attaches additional responsibilities to an object dynamically. Decorators provide a flexible alternative to sub-classing for extending functionality.

Aims to avoid 'class chaos'. Uses open / closed principle. Add new behaviour, but without implementing regression. Uses delegation and composition.

Do a blog post on this, as it’s so annoying to re-remember!

1 Set up libraries & dependencies

Set up blank project folder:

npm init (and follow the prompts)
npm install react react-dom —save
npm install webpack webpack-dev-server -g
npm install babel -g

	// Base types

	val a: Int = 10

	// Functions
	// first class citizens - can be passed as values.

	def add(a: Int, b:Int): Int = {
	a + b
	}

	// add an option to your query, which forces apollo to make the request on the client.

	export default graphql(Query, {
	options: { ssr: false }
	});

	#!/bin/bash
	wget https://wordpress.org/latest.tar.gz
	yum install mysql-server mysql php php-mysql mysql-devel mysql-libs httpd -y
	tar xvfz latest.tar.gz -C /var/www/html/
	service httpd start
	service mysqld start
	chown -R apache /var/www/html

	const avengers = ['Natasha Romanoff', 'Tony Stark', 'Steve Rogers'];

	const ['blackWidow', ...theOthers] = avengers;

	// blackWidow = 'Natasha Romanoff
	// theOthers = ['Tony Stark', 'Steve Rogers']