+ My name is Mitchell and I have a passion for software development. I am currently a software engineer and enjoy working on personal projects in my free time.
+
;
diff --git a/client/js/redux/actions.js b/client/js/redux/actions.js
new file mode 100644
index 0000000..47adfdd
--- /dev/null
+++ b/client/js/redux/actions.js
@@ -0,0 +1,53 @@
+import * as types from "./constants";
+import marked from 'marked';
+import 'whatwg-fetch';
+
+function initPreview(posts) {
+ return {
+ type: types.INIT_PREVIEW,
+ posts
+ }
+}
+
+function loadPost(post){
+ return {
+ type: types.LOAD_POST,
+ post
+ }
+}
+
+function fetching(){
+ return{
+ type: types.FETCHING
+ }
+}
+
+//using redux-thunk we can modify actions before they get called
+//in this case we can send the http request here rather in the react component
+export function fetchPreview() {
+ return (dispatch) => {
+ dispatch(fetching());
+ return fetch('/public/metadata.json')
+ .then(response => response.json())
+ .then(json => {
+ dispatch(initPreview(json));
+ })
+ .catch(error => {
+ console.log(error);
+ });
+ }
+}
+
+export function fetchPost(category, post) {
+ return (dispatch) => {
+ dispatch(fetching());
+ return fetch(`/public/posts/${category}/${post}.md`)
+ .then(response => response.text())
+ .then(response => {
+ dispatch(loadPost(response));
+ })
+ .catch(error => {
+ console.log(error);
+ });
+ }
+}
diff --git a/client/js/redux/constants.js b/client/js/redux/constants.js
new file mode 100644
index 0000000..d9cc693
--- /dev/null
+++ b/client/js/redux/constants.js
@@ -0,0 +1,5 @@
+//constants
+export const INIT_PREVIEW = 'INIT_PREVIEW';
+export const FILTER_PREVIEW = 'FILTER_PREVIEW';
+export const LOAD_POST = 'LOAD_POST';
+export const FETCHING = 'FETCHING';
\ No newline at end of file
diff --git a/client/js/redux/reducers.js b/client/js/redux/reducers.js
new file mode 100644
index 0000000..37bfec8
--- /dev/null
+++ b/client/js/redux/reducers.js
@@ -0,0 +1,61 @@
+//just using one reducer - use combineReducers from redux to modularize things
+import {
+ combineReducers
+} from 'redux';
+import {
+ routerReducer
+} from 'react-router-redux';
+
+//import typs
+import * as types from './constants';
+
+//defaults -
+const defaultState = {
+ preview: {
+ posts: []
+ },
+ filteredPreview: {
+ posts: []
+ },
+ post: "",
+ fetched: false,
+ fetching: false
+};
+
+//default reducer
+function reducer(state = defaultState, action) {
+ //every reducer gets called when an action is called - we check for the type to modify our state accordingly
+ switch (action.type) {
+ case types.INIT_PREVIEW:
+ return Object.assign({}, state, {
+ preview: Object.assign({}, state.preview, action.posts),
+ fetched: true,
+ fetching: false
+ });
+ case types.FILTER_PREVIEW:
+ return Object.assign({}, state, {
+ filteredPreview: Object.assign({}, state.filteredPreview, action.posts)
+ });
+ case types.LOAD_POST:
+ return Object.assign({}, state, {
+ post: action.post,
+ fetched: true,
+ fetching: false
+ });
+ case types.FETCHING:
+ return Object.assign({}, state, {
+ fetched : false,
+ fetching: true
+ });
+ }
+
+ //return present state if no actions get called
+ return state;
+}
+
+const allReducers = combineReducers({
+ reducer,
+ routing: routerReducer
+});
+
+export default allReducers;
diff --git a/client/js/redux/store.js b/client/js/redux/store.js
new file mode 100644
index 0000000..fc5dc04
--- /dev/null
+++ b/client/js/redux/store.js
@@ -0,0 +1,16 @@
+import {applyMiddleware, createStore} from 'redux';
+import {syncHistoryWithStore} from 'react-router-redux';
+import {browserHistory} from 'react-router';
+import thunk from 'redux-thunk';
+import logger from 'redux-logger';
+
+import reducers from './reducers';
+
+const middleware = applyMiddleware(thunk, logger());
+
+//create the new store with default state as an empty object
+const store = createStore(reducers, {}, middleware);
+
+export const history = syncHistoryWithStore(browserHistory, store);
+
+export default store;
\ No newline at end of file
diff --git a/config-template.json b/config-template.json
deleted file mode 100644
index b53d7fb..0000000
--- a/config-template.json
+++ /dev/null
@@ -1,12 +0,0 @@
-{
- "database": {
- "url": "",
- "database": ""
- },
- "api": {
- "key": ""
- },
- "server": {
- "port": ""
- }
-}
\ No newline at end of file
diff --git a/config.template.json b/config.template.json
new file mode 100644
index 0000000..a987565
--- /dev/null
+++ b/config.template.json
@@ -0,0 +1,12 @@
+{
+ "database": {
+ "url": "",
+ "database": "",
+ "username": "",
+ "password": ""
+ },
+ "api": {
+ "key": ""
+ },
+ "port": 8080
+}
diff --git a/db/driver.go b/db/driver.go
deleted file mode 100644
index c5c877b..0000000
--- a/db/driver.go
+++ /dev/null
@@ -1,54 +0,0 @@
-package db
-
-import (
- "gopkg.in/mgo.v2"
- "log"
- "time"
-)
-
-var Mongo Driver
-
-type Driver struct {
- Session *mgo.Session
- Info DatabaseInfo
-}
-
-type DatabaseInfo struct {
- URL string `json:"url"`
- Database string `json:"database"`
- Username string `json:"username,omitempty"`
- Password string `json:"password,omitempty"`
-}
-
-func Configure(d DatabaseInfo) {
- Mongo.Info = d
-}
-
-func (d *Driver) Connect() {
- // Connect to MongoDB
- s, err := mgo.DialWithTimeout(d.Info.URL, 5*time.Second)
-
- if err != nil {
- log.Println("MongoDB Driver Error", err)
- return
- }
-
- d.Session = s
-
- // Prevents these errors: read tcp 127.0.0.1:27017: i/o timeout
- d.Session.SetSocketTimeout(10 * time.Second)
-
- // Check if is alive
- if err = d.Session.Ping(); err != nil {
- log.Println("Database Error", err)
- }
-
- log.Println("Connected to database")
-}
-
-func (d *Driver) Connected() bool {
- if d.Session != nil {
- return true
- }
- return false
-}
diff --git a/index.html b/index.html
new file mode 100644
index 0000000..dcfec5c
--- /dev/null
+++ b/index.html
@@ -0,0 +1,31 @@
+
+
+
+
+
+
+
+
+
+ mitchel.io
+
+
+
+
+
+
+
+
+
diff --git a/main.go b/main.go
deleted file mode 100644
index ca9cdf9..0000000
--- a/main.go
+++ /dev/null
@@ -1,66 +0,0 @@
-package main
-
-import (
- "encoding/json"
- "fmt"
- "io/ioutil"
- "log"
- "net/http"
- "os"
-
- "github.com/mgerb42/mywebsite/controller/api"
- "github.com/mgerb42/mywebsite/db"
- "github.com/mgerb42/mywebsite/route"
-)
-
-//structure for application configurations
-type Config struct {
- Database db.DatabaseInfo `json:"database"`
- Api api.ApiInfo `json:"api"`
- Server ServerConfig `json:"server"`
-}
-
-//configuration settings for the web
-type ServerConfig struct {
- Port string `json:"port"`
-}
-
-func main() {
-
- configurations := readConfig()
-
- db.Configure(configurations.Database)
- api.Configure(configurations.Api)
-
- db.Mongo.Connect()
-
- log.Println("Starting Server...")
- log.Println(http.ListenAndServe(":"+configurations.Server.Port, route.Routes()))
-}
-
-//read the config file and return JsonObject struct
-func readConfig() Config {
-
- log.Println("Reading config file...")
-
- file, e := ioutil.ReadFile("./config.json")
-
- if e != nil {
- fmt.Printf("File error: %v\n", e)
- os.Exit(1)
- }
-
- fmt.Printf("%s\n", string(file))
-
- //m := new(Dispatch)
- //var m interface{}
- var result Config
-
- err := json.Unmarshal(file, &result)
-
- if err != nil {
- fmt.Println(err)
- }
-
- return result
-}
diff --git a/metadata.js b/metadata.js
new file mode 100644
index 0000000..6762140
--- /dev/null
+++ b/metadata.js
@@ -0,0 +1,71 @@
+/*
+ This script runs through each markdown post and scrapes out the title and intro.
+ folder/files within posts are scanned recursively
+ each post is contained within category, which is supplied by the direct parent folder
+ Posts are sorted by date
+ Stores all metadata in ./public/metadata.json
+ Client uses metadata to display posts on preview page
+*/
+
+import fs from 'fs';
+import ncp from 'ncp';
+import marked from 'marked';
+import highlight from 'highlight.js';
+
+marked.setOptions({
+ header: true,
+ highlight: (code) => {
+ return highlight.highlightAuto(code).value;
+ }
+});
+
+const dir = './posts/';
+const json = {
+ posts: []
+};
+
+//do everything synchronously to keep posts ordered
+function parse_dir(dir, folder_name){
+ const posts = fs.readdirSync(dir);
+
+ for(let post of posts){
+ const stats = fs.statSync(dir + post);
+
+ if(stats.isDirectory()){
+ parse_dir(dir + post + '/', post);
+ } else {
+ const file = fs.readFileSync(dir+post, 'utf8');
+ const tokens = marked.lexer(file, null);
+ const temp = {
+ filename: post.slice(0, post.length - 3),
+ category: folder_name,
+ date: post.slice(0, 10),
+ title: tokens[0].text,
+ intro: tokens[1].text
+ }
+ json.posts.push(temp);
+ }
+ }
+}
+
+//recursively parse posts directory for all markdown files
+parse_dir(dir, 'posts');
+
+//sort posts by date
+json.posts.sort((a, b) => {
+ return new Date(b.date) - new Date(a.date);
+});
+
+//output to public path
+fs.writeFile('./public/metadata.json', JSON.stringify(json,null,4), (err) => {
+ if (err) throw err;
+ console.log("Saved metadata.json");
+})
+
+//copy posts folder to public
+ncp('./posts', './public/posts', (err) => {
+ if (err) {
+ return console.error(err);
+ }
+ console.log('copied');
+});
diff --git a/package.json b/package.json
new file mode 100644
index 0000000..b0cfce2
--- /dev/null
+++ b/package.json
@@ -0,0 +1,60 @@
+{
+ "name": "mywebsite",
+ "version": "1.0.0",
+ "description": "My personal website built with React and Go",
+ "main": "index.js",
+ "scripts": {
+ "build": "webpack && babel-node metadata.js",
+ "c9": "webpack-dev-server --port $PORT --host $IP --hot --content-base dist --history-api-fallback",
+ "dev": "webpack-dev-server --content-base public --inline --hot --history-api-fallback",
+ "prod": "export NODE_ENV=production && webpack -p && babel-node metadata.js",
+ "prod-win": "set NODE_ENV=production && webpack -p && babel-node metadata.js"
+ },
+ "repository": {
+ "type": "git",
+ "url": "git+https://github.com/mgerb/mywebsite.git"
+ },
+ "author": "Mitchell Gerber",
+ "license": "ISC",
+ "bugs": {
+ "url": "https://github.com/mgerb/mywebsite/issues"
+ },
+ "homepage": "https://github.com/mgerb/mywebsite#readme",
+ "dependencies": {
+ "babel": "^6.5.2",
+ "babel-cli": "^6.11.4",
+ "babel-core": "^6.13.2",
+ "babel-loader": "^6.2.4",
+ "babel-plugin-react-html-attrs": "^2.0.0",
+ "babel-plugin-transform-class-properties": "^6.11.5",
+ "babel-plugin-transform-decorators-legacy": "^1.3.4",
+ "babel-polyfill": "^6.13.0",
+ "babel-preset-es2015": "^6.13.2",
+ "babel-preset-react": "^6.11.1",
+ "babel-preset-stage-0": "^6.5.0",
+ "css-loader": "^0.23.1",
+ "exports-loader": "^0.6.3",
+ "file-loader": "^0.9.0",
+ "font-awesome": "^4.6.3",
+ "highlight.js": "^9.6.0",
+ "html-webpack-plugin": "^2.22.0",
+ "marked": "^0.3.6",
+ "ncp": "^2.0.0",
+ "node-sass": "^3.8.0",
+ "react": "^15.3.0",
+ "react-dom": "^15.3.0",
+ "react-redux": "^4.4.5",
+ "react-router": "^2.6.1",
+ "react-router-redux": "^4.0.5",
+ "redux": "^3.5.2",
+ "redux-logger": "^2.6.1",
+ "redux-thunk": "^2.1.0",
+ "sass-loader": "^4.0.0",
+ "style-loader": "^0.13.1",
+ "url-loader": "^0.5.7",
+ "webpack": "^1.13.1",
+ "webpack-dev-server": "^1.14.1",
+ "whatwg-fetch": "^1.0.0",
+ "wowjs": "^1.1.3"
+ }
+}
diff --git a/posts/Old Posts/2015-07-21-first-post.md b/posts/Old Posts/2015-07-21-first-post.md
new file mode 100644
index 0000000..e47d5d8
--- /dev/null
+++ b/posts/Old Posts/2015-07-21-first-post.md
@@ -0,0 +1,45 @@
+
+# First Blog Post
+
+My first blog post introduces this website and the motives behind it. I discuss setting up a Node.js webserver for the first time and my experiences with it thus far.
+
+I have had this site up for awhile now, but I've decided to turn it into a blog style website, more or less. I first started working on the site because I wanted to learn new web development tools, in this case, Node.js and MongoDB.
+
+I already had previous experience with SQL databases and other server side scripting languages such as PHP and JSP, but I heard good things about Node.js and I wanted to familiarize myself with a NoSQL database. At first, Node.js was a bit confusing to work with and figure everything out. Now that I am starting to get the hang of Node and MongoDB I am enjoying them more and more.
+
+---
+
+## Setting up Node.js for the first time
+
+There are multiple ways to get up and running with Node. Node uses "modules" and has some that are already built in. Others need to be installed with the NPM package manager, which will become your friend. I am going focus on installing Node.js with Express, which is a web framework for Node.js.
+
+```bash
+$ sudo apt-get install nodejs
+
+$ sudo apt-get install npm
+```
+
+Once you have both Node.js and NPM installed, install Express and MongoDB. We are going to install and use express generator to easily create a skeleton that we can work from.
+
+```bash
+$ npm install express-generator -g
+```
+Based on your system, installing MongoDB may be a bit different. [Here is a guide on how to install.](http://docs.mongodb.org/manual/) Once express generator is installed, it is extremely simple to set up a new Node application.
+
+```bash
+$ express myapp
+```
+
+This will generate a new folder myapp with prebuild folders and files.
+
+```bash
+$ cd myapp
+$ npm install
+$ npm start
+```
+
+Now as easy as that sounds, you have a Node web application running on your machine. You can navigate to your web app at localhost:3000 (It's configured to use port 3000 by default)
+
+Express organizes everything nicely in the [Model View Controller](https://en.wikipedia.org/wiki/Model%E2%80%93view%E2%80%93controller) software pattern. Folders are split up into views, routes, and public files. If you are implementing a database, you would also create a "models" folder. There is also a folder which contains Node modules. When you use NPM to install new modules this is where they will be located.
+
+Node is a very powerful tool that I plan on exploring more in the future. As development of this site continues, I plan to submit more content similar to this.
diff --git a/posts/Old Posts/2015-07-28-how-to-use-git.md b/posts/Old Posts/2015-07-28-how-to-use-git.md
new file mode 100644
index 0000000..2c9aa45
--- /dev/null
+++ b/posts/Old Posts/2015-07-28-how-to-use-git.md
@@ -0,0 +1,123 @@
+# How do I use git?
+
+Git is a very useful file management system that you will find very handy. There are many services that host git repositories and it can also be installed on a personal server if you so choose. I'm going to explain how to set up git and discuss some useful commands and what they do.
+
+---
+
+Throughout this tutorial I am going to be focusing on [Github](http://www.github.com), because I find it easy to use and it is what I use most of the time. Github is just one of the many web-based git repository hosting services. It also has a nice GUI interface that may be useful to beginners, but I will mainly be focusing on git via command line. I have used both in the past and although command line may seem intimidating at first, it becomes easier and more powerful over time.
+
+What exactly does git do? Git is basically a cloud service that you can use for your coding projects. You may be wondering why use git over other cloud hosting services such as dropbox? Git is essentially the same thing, but has many built-in utilities for coding projects specifically. For example, you can see the changes between each commit (or each time you save new changes) displayed in each file. Github has a nice web interface that displays of this information. This helps with version control and it allows you to see which users have made what changes.
+
+## How to set up git
+
+```bash
+$ Sudo apt-get install git
+```
+
+In linux just use the command above to install git. You will then run all git commands within the terminal. If you are on a Windows machine you can install git [here](http://git-scm.com/download/win). Once git is installed you can start using it immediately.
+
+```bash
+$ cd Desktop && mkdir testgit && cd testgit && git init
+```
+
+Executing the above command will create a folder on the desktop and initialize a git repository. It also creates a .git folder that contains the settings of the repository. If you have already created a project and want to set it up as a git repository just simply navigate to the root directory and use `$ git init`.
+
+```bash
+$ echo "testgit" >> README.md
+```
+
+You must create a readme file within the directory to be able to push to github. You can put anything in the readme, but github uses this file to display information about your repository on the main page.
+
+You must also first register with Github before you can create your own repositories. When pushing to your repository, you will be asked for your login credentials. You can globally configure these if you do not wish to be asked every time.
+
+```bash
+$ git config --global user.name "John Doe"
+$ git config --global user.email johndoe@example.com
+```
+
+Now that you have initialized your git repository, you can start on your project and begin adding files. When you wish to save your files to the repository, you must first add all of the changes. YOU MUST ADD CHANGES BEFORE YOU COMMIT!! I have commited and pushed without adding changes multiple times before so do not forget!
+
+```bash
+$ git add -A
+```
+
+This will add all changes of all files in the directory. Once you have added all of the changes you can now commit.
+
+```bash
+$ git commit -m "First Commit"
+```
+
+Committing your changes does NOT push them to Github. It just saves all of the new changes and sets them up to be pushed. The above command will make a commit with the message "First Commit". You must have a message with each commit! The -m parameter allows you to put a message in quotes without opening it up with an editor.
+
+Now everything is ready to be pushed to Github. We first need to create a repository on Github that we can push to. You can simply do this by clicking the "New Repository" button on Github's website. Once the repository is created, we need to attach our newly created repository to it. We can do this by using the `remote` command.
+
+
+```bash
+$ git remote add origin https://github.com/username/repositoryname.git
+```
+
+Replace "username" and "repositoryname" with your username and the name of your newly created repository and now your local repository should be attached to Github. Now we can finally push all changes to Github.
+
+```bash
+$ git push origin master
+```
+
+You should be prompted to enter your username and password, unless you configured that globally before. Now, each time you want to save your changes to github, execute the follwoing commands.
+
+```bash
+$ git add -A
+$ git commit -m "Commit Message"
+$ git push origin master
+```
+
+If you ever lose files, or want to work on this same project on another machine you can simply clone the entire repository and continue working on it from the last time you pushed. Just navite to your repository on Github's website and copy the URL.
+
+```bash
+$ git clone https://github.com/username/repositoryname.git
+```
+
+This will copy the entire repository into its own folder. If you implement changes on one machine and you want to update the repository on another, you can pull all of the most recent changes.
+
+```bash
+$ git pull
+```
+
+Note: You must do this in the directory of the repository you wish to pull the changes.
+
+This is just a beginner guide on how to use git for the first time. There are still many other things that git has to offer, but these are the basic commands to get you started and using git.
+
+## Edit 10/27/15: More information on Git
+
+I would like to discuss a few more things about git that I have learned and become familiar with. I am hosting this website on an Ubuntu VPS from Digital Ocean and I rely heavily on git to update and make changes. I've recently added a new "working" branch to my repository. This makes it easier to work on changes while not breaking the master branch. Another branch can be made on github and you can base it off another branch. I started a "working" branch and copied the master branch.
+
+```bash
+$ git checkout working
+```
+
+Now, after cloning my repository I can switch to my new working branch with the checkout command. Keep in mind that if I was working on my master branch with uncommited changes, I cannot checkout to another branch without commiting current changes to the master branch. After making new changes to my new "working" branch I can add, commit, and push them to Github. If and when I want to update my master branch I can checkout to my master branch, merge changes with "working" and push changes to Github. The master branch should then be up to date with the "working" branch.
+
+```bash
+$ git add -A
+$ git commit -m "commit message"
+$ git push origin working
+$ git checkout master
+$ git merge working
+$ git push origin master
+```
+
+At any time you can check to see which branch you are working on and if any files have been updated/are ready to commit by using the status command:
+
+```bash
+$ git status
+```
+
+Now that my changes with "working" are updated on "master" I can pull the changes to my server on Digital Ocean. I sometimes have to log into my server and make minor updates to the code. This can cause merge conflicts with git and I may be unable to pull the master branch. To resolve this issue I must reset the master branch so that I can pull new changes.
+
+```bash
+$ git reset --hard
+$ git pull
+```
+
+This will reset the branch to the last commit and get rid of any uncommited changes. Only do this if you have not made changes that you want to save. Because it is running on my server, I want to overwrite any changes anyway.
+
+These are a few more git commands that I have learned since working on this project. As I become more familiar with git I will continue to update this post
diff --git a/posts/Old Posts/2015-08-13-esp8266.md b/posts/Old Posts/2015-08-13-esp8266.md
new file mode 100644
index 0000000..687f3f5
--- /dev/null
+++ b/posts/Old Posts/2015-08-13-esp8266.md
@@ -0,0 +1,47 @@
+# ESP8266 - Cheap Wifi Microcontroller
+
+I've recently started playing around with microcontrollers, or more specifically arduinos. I have always had some projects in mind that require the use of some sort of microcontroller, most of which requred a wifi connection. There are a few wifi options availabe for the arduino, some of which can be very expensive. I eventually stumbled upon the ESP8266, which I have finally figured out... mostly.
+
+## Why the ESP8266?
+
+It is extremely cheap! They can be found for roughly $3 apiece whereas the wifi arduino shield is around $70! I figured I would take my chances with the cheaper option and I ordered [three of these](http://www.banggood.com/ESP8266-Remote-Serial-Port-WIFI-Transceiver-Wireless-Module-p-947259.html). After frying two of these in process of trying to figure the darn things out, I ordered a [5 pack of the ESP-07 version.](http://www.banggood.com/ESP8266-ESP-07-Remote-Serial-Port-WIFI-Transceiver-Wireless-Module-p-968190.html) Banggood also sent me 7 of them which was a bonus.
+
+## Why the ESP-07 version?
+
+The ESP8266 can be programmed as a stand alone device with the [Arduino IDE!](https://github.com/esp8266/Arduino) That's right, you don't even need an arduino! Also, most of the arduino libraries work with it! I went this direction after exeriencing many frustrations using the ESP8266 in conjunction with an arduino. The ESP-07 version has more GPIO pins and is about the same price, whereas the ESP-01 only has two GPIO pins, one of which much be grounded to program the device.
+
+## First experiences with the ESP8266
+
+After playing around with this microcontroller for some time now, I have concluded that it can be finicky at times. Documentation for the device can also be difficult to find, especially if you run into problems. I am going to discuss what I went through to finally get the device fully working, along with the frustrations that I experienced.
+
+When you first get the device, make sure to have solid connections to each one of the pins. You will need an FTDI programmer to connect to USB. [This is the one that I have and it works fine.](http://www.banggood.com/FT232RL-FTDI-USB-To-TTL-Serial-Converter-Adapter-Module-For-Arduino-p-917226.html) Just make sure you have one that is 3.3v capable or it will not work! The ESP8266 can draw over 200 mA at times and the FTDI programmer simply does not provide enough power. [This is the power supply I used.](http://www.banggood.com/3Pcs-MB102-Breadboard-Module-Adapter-Shield-3_3V5V-For-Arduino-Board-p-957095.html)
+
+## Wiring
+Wiring is pretty much the same across different versions of the ESP8266. Connect VCC and CH_PD to power at all times. Gnd to gnd and on the ESP-07 GPIO15 must also go to gnd. When you program the device, you must have GPIO0 to ground for programming mode. You must also connect RX on the ESP8266 to TX on the FTDI programmer and vice versa. Make sure to connect all of the power and ground wires to the power supply and NOT the FTDI programmer. The only two wires you should have connected to the FTDI programmer are RX and TX.
+
+## Testing the ESP8266
+To test out the device, plug it into your computer and use a serial monitor. You can use the arduino serial monitor, or you can also use putty. Make sure to select the correct COM port and the right baud rate. Baud rates can vary. I have had some that are 9600 and others have been 115200. Just change the baud rate until you see text that you can actually read. Once connected, you can change the baud rate of the ESP8266.
+
+There is a set of AT commands to communicate with the ESP8266. The documentation of these commands is descent although some commands were a bit hard to find. [Here is a list of most of the commands.](https://nurdspace.nl/ESP8266) A few important commands that are often missed are to change the baud rate and update the firmware on the device. You can update the firmware by using AT+CIUPDATE. You can also change the baud rate by using AT+CIOBAUD=9600, or whatever baud rate you desire.
+
+These commands can be used to test the ESP8266, but they are also the same commands if you wanted to use it with an arduino. Simply wire it up to serial on an arduino and print out the commands. I played around with this for a bit, but not long enough to get it fully working. This is how I was originally going to use the device, but I found it to be much easier programming the ESP8266 directly as a standalone device.
+
+## Programming ESP8266 with Arduino IDE
+
+A major advantage of programming the ESP8266 is that it is more powerful, yet much smaller in size. It uses a 32 bit processor and also has 1mb of ram (on the newer versions). [Link to Github ESP8266 Arduino IDE.](https://github.com/esp8266/Arduino) You can install this in your Arduino IDE by File > preferences and adding `http://arduino.esp8266.com/package_esp8266com_index.json` to Additional Boards Manager URLs. Now you can go to Sketch > Libraries > Manage Libraries and add the ESP8266 library.
+
+Select an example sketch (WIFIScan) and make sure your ESP8266 is plugged in with GPIO0 to ground! It must be to ground to enter programming mode! Select Generic ESP8266 Module for the board and the right port. It shouldn't matter which programmer is selected. Compile and upload your sketch and it is as simple as that!
+
+
+## Complications
+
+I just want to reiterate some of my complications that I ran into throughout this process. The biggest thing to keep in mind it to check your connections! The first time I soldered all of the connections I couldn't figure out why it wasn't working. I checked each connection with a meter only to find out one of them was bad. Another thing is to make sure you use an external power supply! Connect all power and ground connections to these! Also connect the ground of your FTDI programmer to the ground of your power supply. Make sure the voltage of your power supply and FTDI programmer are 3.3v! Remember to connect GPIO0 to ground ONLY when uploading to the ESP8266.
+
+## Sources
+
+[https://www.sparkfun.com/products/13678](https://www.sparkfun.com/products/13678)
+[http://www.esp8266.com/](http://www.esp8266.com/)
+[https://github.com/esp8266/Arduino](https://github.com/esp8266/Arduino)
+[http://www.pridopia.co.uk/pi-doc/ESP8266ATCommandsSet.pdf](http://www.pridopia.co.uk/pi-doc/ESP8266ATCommandsSet.pdf)
+[https://nurdspace.nl/ESP8266](https://nurdspace.nl/ESP8266)
+[http://www.electrodragon.com/w/ESP8266](http://www.electrodragon.com/w/ESP8266)
\ No newline at end of file
diff --git a/posts/Old Posts/2015-10-28-wifi-led.md b/posts/Old Posts/2015-10-28-wifi-led.md
new file mode 100644
index 0000000..bf6e98e
--- /dev/null
+++ b/posts/Old Posts/2015-10-28-wifi-led.md
@@ -0,0 +1,54 @@
+# Wifi Controlled LED Lights
+
+LED lights can be used for many different things. I have used LED lights in the past in my computer and even on my desk. They have always been wired to a physical switch. I now have LED lights that I can turn on and off and even change color from a simple web page that I can access with my phone.
+
+* * *
+
+For this project I used the ESP8266 microcontroller to connect to my wireless network, run a web server, and control an RGB LED strip based on inputs from a web form. I followed [this guide](https://learn.adafruit.com/rgb-led-strips), but incorporated Wifi to control the LEDs.
+
+Required Components
+
+ESP8266
+12v Powersupply 1.2 Amps per meter (Keep in mind the ESP8266 can draw 200-400ma)
+
+Wiring
+[TIP120 Transistors](http://www.banggood.com/10-Pcs-TIP120-NPN-TO-220-Darlington-Transistors-p-932779.html)
+12v to 3.3 volt converter
+
+Code can be found [here](https://github.com/mgerb/wifi_leds/blob/master/wifi_RGB_strip.ino).
+
+## Code
+
+Depending on which version of ESP8266 you have, this might not work. You need at least 3 GPIO pins. I used version ESP-07, which has plenty of usable GPIO pins. The code is fairly simple. Basic functionality includes connecting to my Wifi network and starting up a web server. I was able to log into my router after the ESP connected to assign it a static IP. This way I could always access the web server with the same IP address.
+
+The main program loop listens for an http request on the web server. If the cycle parameter is set to true, the color cycle function will continue to run until the server gets another HTTP request. The color cycle function happens to be a problem because it does not run asynchronously. This means that the whole color cycle must complete before it can respond to another HTTP request. This can cause delays when accessing the web page. Because this is a small personal project I didn't look into fixing this issue.
+
+All data from the web page is passed to the server through get parameters. The program parses through these parameters and checks to see if any of the colors are out of range. If they are out of range it either sets them to a max value of 250 or a min value of 0 (off). The changeColor method is called with paramters from the web form.
+
+## Changing Colors
+
+The changeColor function takes in 6 parameters; one for current color and one for each color passed from the web form. This function needs the current color because it implements the changing of colors gradually. Again, it is all synchronous so during the changing of colors the web server will not be able to respond to requests.
+
+## Cycling Colors
+
+The color cycle function is a bit more confusing than the changeColor function. This function cycles through each color once. The delay can be adjusted to how fast you would like the cycle to last. This function will continuously get called as long as the cycle boolean is true. After each cycle the server will still check for an http request. Like I mentioned above this function is synchronous so it must complete a full cycle before any other code is executed.
+
+This function is only chaning 2 RGB values at any one time. It contains two loops, one of which is nested. The first loop selects two pins to be cycled at one time: rgbColor[decColor] and rgbColor[incColor]. For example, it will first select Red and Green, then Green and Blue, and finally Blue and Red. During each selection, a nested loop is run, which cycles the color values of selected color pins. Red starts at 250 where Green starts at 0\. The nested loop cycles Red to 0 while cycling Green to 250, exits the nested loop, and then proceeds to cycle Green and Blue, and finally Blue and Red.
+
+## Wiring
+
+The wiring for this project is fairly straight forward. The image below is from Adafruit's website and it illustrates the wiring for an Arduino. The ESP8266 wiring is fairly similar, but because it runs on 3.3 volts, I have used two regulators to convert 12 volts. I used a 5v and 3.3v regulator because the 3.3v regulator could not take 12v as an input. You could also just get a 12v to 3.3v converter but I used what I had on hand.
+
+12v PSU > 5v > 3.3v > ESP8266
+
+The power on the LED strip is wired straight to the positive connections on the 12v power supply.
+
+
+
+The image below is how I have my ESP8266 wired under my desk to control my led lights. As you can see the power comes in from the top right and the output for each RGB pin is on the left where the black is the 12v.
+
+
+
+A picture of the final setup. I have one long LED strip along the back of the desk and two smaller strips on the back of each of the monitors.
+
+
\ No newline at end of file
diff --git a/posts/Old Posts/2015-12-18-temperature-sensor.md b/posts/Old Posts/2015-12-18-temperature-sensor.md
new file mode 100644
index 0000000..1d82591
--- /dev/null
+++ b/posts/Old Posts/2015-12-18-temperature-sensor.md
@@ -0,0 +1,261 @@
+# Temperature Sensor on the Web
+
+The temperature readings that are displayed on this site come from the ESP8266 with a DHT11 sensor attached to it. I am going to explain the steps in the entire process. I will split it up into two parts. In this post I will focus on programming the ESP8266 and how to send data to a web server.
+
+* * *
+
+Update: I have updated some information regarding this project. Refer to these other posts.
+
+[ESP8266 temperature sensor updates and difficulties](/?post=12-29-15.html)
+[Temperatue Sensor - Server Side](/?post=1-1-2016.html)
+
+For this project you will need an ESP8266 and a DHT temperature sensor. For prototyping purposes I prefer to use the [NodeMCU module](http://www.banggood.com/NodeMcu-Lua-ESP-12E-WIFI-Development-Board-p-985891.html). There are a variety of temperature sensors that you could use, but I prefer the DHT11 because it is easy to use and it is cheap! I ordered a 5 pack of them from [Banggood](http://www.banggood.com/5Pcs-KY-015-DHT11-Temperature-Humidity-Sensor-Module-For-Arduino-p-983263.html). The source code for this project can be found on [Github](https://github.com/mgerb/esp8266-HTTPTempSensor).
+
+## How it works
+
+When the ESP first boots up, it reads WiFi credentials from the EEPROM and tries to connect to an access point using those credentials. If no connection is made, it starts up it's own access point and runs a web server with a captive portal. This means that when anyone connects to it, it will redirect any dns request to itself, which forces anyone to the configuration page. The user can connect to the access point and enter in the ssid, password, and preferred sensor name. This information will be saved into EEPROM and the ESP will then reboot and start sending sensor data to the server.
+
+
+
+## ESP8266 File System
+
+To run the web server, I used the file system library within the arduino ESP library. This is how I store the web content in flash on the chip. It allows me to modify all of the necessary web files without having to deal with sending them as strings from the arduino code.
+
+To use the file system, you must download the tool [here](https://github.com/esp8266/arduino-esp8266fs-plugin/releases/download/0.1.3/ESP8266FS-0.1.3.zip) to upload your files to the ESP. Once downloaded, store it in a tools folder in the arduino folder (path "/Arduino/tools/ESP8266FS/tool/esp8266fs.jar"). Now when you create a new sketch go to the sketch folder and create a "data" folder. To upload data to this folder select "Tools > ESP8266 Sketch Data Upload" and the files will be uploaded to the ESP and will be ready to use within the program. More information on the ESP8266 file system can be found [here](http://esp8266.github.io/Arduino/versions/2.0.0/doc/filesystem.html).
+
+## Sending data to the server
+
+There are many ways to send the data to a server, but I implemented data transfer with a simple get request. I chose this route because it is extremely simple to create a REST API in Node.js. I will cover this in a nother post. If you are unfamiliar with a get request, it is a way a web server can receive a request, and also parameters within that request. In this case, I send temperature, humidity, location, and a key as parameters in the request.
+
+If this were a full production application, this would not be the ideal way to handle data transfer to a server because it is not encrypted. A better practice would be to implement this using another TCP transfer protocol. In my case, it would be better to send a POST request over SSL, but I have not looked into that for this project yet as the method I am currently using seems to work just fine.
+
+## Code
+
+```arduino
+#include
+#include
+#include
+#include
+#include
+#include
+#include
+#include
+
+DHT dht(5, DHT11);
+
+char ssid[32] = "";
+char password[32] = "";
+char sensorName[32] = "";
+
+//key used by web server to prevent unnecessary http requests
+const String server_password = "";
+
+const int httpPort = 80;
+const char* host = "162.243.16.83";
+
+boolean connected;
+
+// DNS server
+const byte DNS_PORT = 53;
+
+// Web server
+ESP8266WebServer server(80);
+DNSServer dnsServer;
+WiFiClient client;
+
+/* Soft AP network parameters */
+IPAddress apIP(192, 168, 1, 1);
+IPAddress netMsk(255, 255, 255, 0);
+
+void setup() {
+ // put your setup code here, to run once:
+ Serial.begin(115200);
+
+ delay(1000);
+
+ loadCredentials();
+
+ //try to connect to access point
+ WiFi.disconnect();
+ WiFi.begin(ssid,password);
+
+ int connRes = WiFi.waitForConnectResult();
+ Serial.print ( "connRes: " );
+ Serial.println ( connRes );
+
+ Serial.println("Connecting");
+
+ for (int i = 0; WiFi.status() != WL_CONNECTED && i <10; i++){
+ Serial.print(".");
+ delay(1000);
+ }
+
+ //if connected skip setting up access point
+ if(WiFi.status() != WL_CONNECTED){
+ connected = false;
+
+ WiFi.mode(WIFI_AP);
+ WiFi.softAPConfig(apIP, apIP, netMsk);
+ WiFi.softAP("Sensor Config");
+
+ delay(500);
+
+ server.on("/", handleRoot);
+ server.on("/config", handleConfig);
+ server.on("/bootstrap.min.css", handleBootstrap);
+ server.on("/style.css", handleCss);
+ server.onNotFound(handleNotFound);
+
+ SPIFFS.begin();
+ dnsServer.start(DNS_PORT, "*", apIP);
+ server.begin();
+ }
+ else{
+ connected = true;
+ WiFi.mode(WIFI_STA);
+ dht.begin();
+ }
+
+}
+
+void loop() {
+ //if could not connect to access point
+ if (!connected){
+ dnsServer.processNextRequest();
+ server.handleClient();
+ }
+ else{
+ if (!client.connect(host, httpPort)) {
+ return;
+ }
+
+ float temp = dht.readTemperature(true);
+ float humidity = dht.readHumidity();
+
+ // We now create a URI for the request
+ String url = "/temperature";
+ url += "?temperature=";
+ url += temp;
+ url += "&humidity=";
+ url += humidity;
+ url += "&key=";
+ url += server_password;
+ url += "&location=";
+ url += sensorName;
+
+ url.replace(" ", "+");
+
+ Serial.println("URL: " + url);
+ client.print(String("GET ") + url + " HTTP/1.1\r\n" +
+ "Host: " + host + "\r\n" +
+ "Connection: close\r\n\r\n");
+ delay(100);
+
+ while(client.available()){
+ String line = client.readStringUntil('\r');
+ Serial.print("Response: " + line);
+ }
+
+ //delay(10000);
+ ESP.deepSleep(120 * 1000000, WAKE_RF_DEFAULT);
+ }
+}
+
+void handleRoot(){
+ if(SPIFFS.exists("/index.html")){
+
+ File file = SPIFFS.open("/index.html", "r");
+
+ server.streamFile(file, "text/html");
+
+ file.close();
+ }
+ else{
+ server.send(404, "file doesn't exist");
+ }
+}
+
+void handleBootstrap(){
+ if(SPIFFS.exists("/bootstrap.min.css")){
+
+ File file = SPIFFS.open("/bootstrap.min.css", "r");
+
+ server.streamFile(file, "text/css");
+
+ file.close();
+ }
+ else{
+ server.send(404, "file doesn't exist");
+ }
+}
+
+void handleConfig(){
+
+ if (server.arg("password") != "" && server.arg("ssid") != "" && server.arg("name") != ""){
+
+
+ server.arg("ssid").toCharArray(ssid, sizeof(ssid) -1);
+ server.arg("password").toCharArray(password, sizeof(password) -1);
+ server.arg("name").toCharArray(sensorName, sizeof(sensorName) -1);
+
+ saveConfig();
+
+ server.send(200, "text/html", "Config successful. Rebooting");
+
+ ESP.restart();
+ }
+
+ server.send(200, "text/html", "");
+}
+
+void handleCss(){
+ if(SPIFFS.exists("/style.css")){
+
+ File file = SPIFFS.open("/style.css", "r");
+
+ server.streamFile(file, "text/css");
+
+ file.close();
+ }
+ else{
+ server.send(404, "file doesn't exist");
+ }
+}
+
+void handleNotFound(){
+ if(SPIFFS.exists("/index.html")){
+
+ File file = SPIFFS.open("/index.html", "r");
+
+ server.streamFile(file, "text/html");
+
+ file.close();
+ }
+ else{
+ server.send(404, "file doesn't exist");
+ }
+}
+
+/** Store WLAN credentials to EEPROM */
+void saveConfig() {
+ EEPROM.begin(512);
+ EEPROM.put(0, ssid);
+ EEPROM.put(0+sizeof(ssid), password);
+ EEPROM.put(0+sizeof(ssid)+sizeof(password), sensorName);
+ EEPROM.commit();
+ EEPROM.end();
+}
+
+void loadCredentials() {
+ EEPROM.begin(512);
+ EEPROM.get(0, ssid);
+ EEPROM.get(0+sizeof(ssid), password);
+ EEPROM.get(0+sizeof(ssid)+sizeof(password), sensorName);
+ EEPROM.end();
+
+ Serial.println("Recovered credentials:");
+ Serial.println(ssid);
+ Serial.println(password);
+ Serial.println(sensorName);
+}
+```
\ No newline at end of file
diff --git a/posts/Old Posts/2015-12-29-esp8266-updates.md b/posts/Old Posts/2015-12-29-esp8266-updates.md
new file mode 100644
index 0000000..3a6b0c6
--- /dev/null
+++ b/posts/Old Posts/2015-12-29-esp8266-updates.md
@@ -0,0 +1,45 @@
+# ESP8266 temperature sensor updates and difficulties
+
+I'm working on setting up new sensors now that I have been developing the back end of my website to display sensor information. Throughout this process I made updates to the current code for the project. As I continue to make progress I am overcoming obstacles as they show up.
+
+* * *
+
+I changed the way that the ESP8266 sends web pages to the user via HTTP requests. Previously I made use of the file system in the ESP8266, but I changed the way I did this because I noticed that it was a bit slow handling all the requests, especially because I used bootstrap to make the user interface look pretty. Although I cut down the bootstrap to only the pieces that I needed, it was still slower than I wanted.
+
+I decided to not use the file system and handle the html pages within header files. I found a fairly nice way of doing this. To do this, declare a new character array, store it in flash memory with "PROGMEM", and use the raw string literal functionality of C to escape all characters in a string as show below. This is not quite as nice a dealing with an HTML file in memory, but it is easier because you do not have to upload the files to the file system every time, which takes a good amount of time.
+
+`const char page_html[] PROGMEM = R"=====(/*insert html here*/)=====";`
+
+This newly created page can now be sent back to the user upon an HTTP request.
+
+`server.send(200, "text/html", page_html);`
+
+There were a few other updates that I made. I realized that if the access point the ESP was connected to goes down, it would not try to reconnect. It will now check if it is connected to the access point every time it tries to take a temperature reading and send data. If it is not connected to the access point it will reboot. Now that it reboots, if it still cannot connect to the access point it will be stuck in config mode. I fixed this by creating a timeout. If it has been sitting in config mode for 10 minutes the device will reboot.
+
+These example are show below. Keep in mind that this is not the entire program, but just the new functionality that I mentioned. The source code for the project can be found [here](https://github.com/mgerb/esp8266-HTTPTempSensor/tree/working).
+
+## Problems flashing the ESP
+
+I previously used the ESP-07, but recently got some new ESP-12e's because of the higher flash size. I thought this would be great if I was going to make use of the file system. After spending hours and hours trying to flash these chips, I came to the conclusion that I need a better serial to USB programmer. The current one that I use came from China and was very cheap.
+
+With the new version of ESP Arduino software (2.0.0), you get the option of flashing with the ck mode. This requires GPI0 > DHT and RESET > RST. My FTDI programmer did not have an RTS pin, but rather a CTS. I found that I could flash one of my chips with this and the other I could not. After doing some research I found that it may be a problem with my Mac. Unfortunately my Ubuntu image that I usually dual boot with acted up and would not boot. This left me without any other operating system to try at the time.
+
+
+
+Because I was experiencing problems flashing with the new ESP8266 Arduino software, I reverted to an older version (1.6.5). In this version I was able to put GPI0 > Ground and start the ESP8266 in flash mode. This is the part where I realized I have a bad FTDI programmer. When I flash the device, it will get stuck every once in awhile. I then have to unplug everything and try again. I then tried a different programmer and it was able to work every time.
+
+After a good amount of frustration I was able to get my ESP8266 flashed with my new program and I got another temperature sensor set up. Here is the wiring that I used in the sensor. Keep in mind the DHT11 sensors that I used had a 10k resistor built into them.
+
+GND > GND
+
+GPI15 > GND
+
+VCC > 3.3v
+
+EN (CH_PD) > 3.3v
+
+GPIO5 > Sensor Data
+
+The sensor VCC and Ground then were hooked up accordingly. I used an 800ma 3.3v regulator to power everything and it is working fine.
+
+
\ No newline at end of file
diff --git a/posts/Old Posts/2016-01-01-temperature-sensor-server.md b/posts/Old Posts/2016-01-01-temperature-sensor-server.md
new file mode 100644
index 0000000..46786f5
--- /dev/null
+++ b/posts/Old Posts/2016-01-01-temperature-sensor-server.md
@@ -0,0 +1,35 @@
+# Temperature Sensor - Server Side
+
+The server side coding is a bit more complicated than programming the ESP8266 itself. I use a NoSQL database to store the information and some of the queries are complex and can be confusing to understand. I also make use of REST API's to send the data to the client side.
+
+* * *
+
+## Storing Information
+
+For this project I am using MongoDB to store all of my information because it goes well with my server, which is coded in Node.js, but any database could be used. I also wanted to learn about NoSQL databases because I already have experience with SQL databases. Information on coding the ESP8266 can be found [here](/?post=12-18-2015.html) in a previous post.
+
+`mitchellg.me/temperature?temperature=0&humidity=0&location=0&key=0`
+
+Above is the GET request that is sent to the server from the ESP8266\. Data is transferred through GET parameters. The key is an authentication code that I set to prevent unwanted HTTP requests. This is similar to an API key. Below is the code implemented to handle the HTTP request from the ESP8266.
+
+## Creating the REST API
+
+There are many ways that I could display the temperature information on a graph, but I was trying to come up with a quick and easy way that was also efficient. I also wanted reusability in case I wanted to add or change things down the road. I decided I was going to use [Chart.js](http://www.chartjs.org/) because it is open source and free. These graphs are implemented on the front end using javascript. Because of this I needed to figure out a way to send the sensor data to the client side. I felt that the best way for me to do it would be creating a REST API. I plan on making another post in the future explaining all of my client side code along with how to use Chart.js.
+
+Now that I know how I want to display my information I just need to think of what information I want to display. I thought it would be cool to display a few different graphs. As of right now I have one graph that displays data by the year and one that displays by each month. The maximum and minimum temperature of each day are displayed as well as the average humidity for that day. The user can also select which year or which month to display and the graph will adjust accordingly.
+
+Now that I know what information I need I can start developing my REST API. I have a MongoDB collection called "temperature", which stores temperature, humidity, location, and time updated. Updated is a type of Date, which I will use in all of the queries to group by each day. To do the grouping in MongoDB I needed to use the [aggregation functionality](https://docs.mongodb.org/v3.0/aggregation/) of MongoDB. Aggregation allows me to essentially perform queries on top of queries using the MongoDB "pipeline". This is similar to an SQL query when a selection is performed within a selection.
+
+## Explanation of MongoDB Queries
+
+The first function takes in a location and year and returns maximum and minimum temperature readings as well as average humidity for each day in the selected year. The results are also returned sorted from newest to oldest.
+
+In the first part of the aggregation pipeline, which is $project, I am just selecting the temperature, humidity, year, month, and day. This part is important because it allows me to pull the year, month, and day from the date that is stored in the database. This way I do not have to store each of these entries separately in the database.
+
+This data is then passed to the next part of the aggregation pipeline. The $match pipeline stage selects out information from the collection which match with the selected year and location.
+
+The $group aggregation operator is the stage in which I actually group the data by the location, year, month, and day. For each group I also take the max and min temperatures along with the average humidity by using the correct accumulator operators. Now that I have the appropriate information I need, I just use the $sort pipeline operator to sort the data based on time updated.
+
+The function to display by month is the exact same, except I take in the month attribute and add it to the $match operator within the aggregation pipeline. Just like that the query is complete and all I need to do is send the response back to the client. Chart.js uses JSON format, which makes things extremely easy because MongoDB query results are in JSON. I set the content type to JSON, and use JSON.stringify() to convert the JSON to a readable format for debugging purposes. An example API request can be tested out here.
+
+[/api/sensorbylocation/year?location=Winona%20Apartment&year=2016](/api/sensorbylocation/year?location=Winona%20Apartment&year=2016)
diff --git a/posts/Old Posts/2016-01-04-hosting-digital-ocean.md b/posts/Old Posts/2016-01-04-hosting-digital-ocean.md
new file mode 100644
index 0000000..8159f23
--- /dev/null
+++ b/posts/Old Posts/2016-01-04-hosting-digital-ocean.md
@@ -0,0 +1,93 @@
+# Hosting a Node.js Web Server on Digital Ocean
+
+A VPS or "Virtual Private Server" is a nice way to host a web server. Digital Ocean provides a great service based on my experiences. I recently rebuilt a new server to host this site and I will go over the entire setup process.
+
+* * *
+
+## Creating a Droplet
+
+Digital Ocean calls their VPS's "Droplets" and they are very simple to set up. Create an account on the site and attach a credit card. You are now ready to create a droplet. In my case I use an Ubuntu server but Digital Ocean offers a variety of linux operating systems. Select the size, location, and name and the server is up and running! You will be emailed with the login information.
+
+## Login with SSH
+
+Select your newly created droplet and navigate to console access. You will be prompted to change your password. Once the password is changed you can connect to the root user account via SSH.
+
+`$ ssh root@`
+
+If you are using a Windows machine you can download [putty](http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html) to connect with SSH. If you choose not to use SSH you can just use the console access on the Digital Ocean website.
+
+## Firewall
+
+The very next thing I do is set up the firewall. I only want to open ports that need to be open. I use the built in firewall tool in Ubuntu called UFW.
+
+`$ ufw enable`
+
+Now that UFW is enabled I can start opening the necessary ports. I must open 22 if I want to continue to SSH into the server.
+
+`$ ufw allow 22/tcp`
+
+This will open TCP port 22 for SSH. I also open port 80 because that is the port in which the web server will run on.
+
+## Network Monitoring
+
+`$ sudo apt-get install vnstat`
+
+VNStat is a nice tool that will allow me to monitor the bandwidth my server consumes both outbound and inbound. Simply use the command "vnstat" to check the bandwidth. Note that it takes awhile for vnstat to capture bandwidth data if you just upon first installing it.
+
+## Terminal Multitasking
+
+`$ sudo apt-get install screen`
+
+Screen is a really nice tool too use when dealing with multiple terminal windows. Simply use the command `$ screen` to start screen. Press CTRL>A then C to open another screen window. Navigate between screens by pressing CTRL>A then N. To check if scren is attached or detached simply use the command `$ screen -ls`. Reattach to screen by using `$ screen -r` and detach with `$ screen -d`. If screen is open and already attached, but you wish to attach to it, simply use the command `$ screen -d -r`.
+
+## NPM
+
+Now that I have the basics set up on my server I can start installing the dependencies for my Node.js web server. NPM is a package manager that is needed for Node.js. It makes things very easy when used properly.
+
+```bash
+$ sudo apt-get install npm
+$ sudo npm update npm -g
+```
+
+The package manager on ubuntu does not have the most recent NPM packge as of right now but it is very easy to update with NPM itself. The second command listed above will download the newest version of NPM and update itself.
+
+## Node.js
+
+Now that NPM is installed I can use it to install Node.js.
+
+```bash
+$ sudo npm cache clean -f
+$ sudo npm install -g n
+$ sudo n stable
+$ sudo ln -sf /usr/local/n/versions/node//bin/node /usr/bin/node
+```
+
+This will install the latest version of Node.js.
+
+## MongoDB
+
+Installing MongoDB used to be very simple, but now they do not include the init scripts with the newest version. Installation instructions can be found [here](https://docs.mongodb.org/manual/tutorial/install-mongodb-on-ubuntu/).
+
+Once MongoDB is installed it can be run by using the command `$ mongod`, but I am going to show an easier way using the startup script. This way MongoDB will start when the VPS boots and it can also be monitored with the `$ service` linux command.
+
+```bash
+$ cd /etc/init.d
+$ sudo nano mongod
+```
+
+Once here copy the contents of [this file](https://github.com/mongodb/mongo/blob/master/debian/init.d) into mongod. We now have the startup script, but we need to change some permissions first before it can run.
+
+```bash
+$ sudo chmod 755 /etc/init.d/mongod
+$ sudo chown root:root /etc/init.d/mongod
+```
+
+And to run MongoDB upon system startup.
+
+```bash
+$ update-rc.d mongod defaults
+```
+
+## Restoring Database Files
+
+The web server is almost ready, but first I need to make sure all of my previous records are stored in the database. To do this I navigate to the folder which my records are stored in, which is contained in my git repository. I then use the command `$ mongorestore`, which loads everything from the dump into the freshly installed MongoDB. To backup MongoDB simply navigate to the desired folder to store the backup and issue the command `$ mongodump`.
diff --git a/posts/Old Posts/2016-05-22-flashing-esp8266.md b/posts/Old Posts/2016-05-22-flashing-esp8266.md
new file mode 100644
index 0000000..ad93be9
--- /dev/null
+++ b/posts/Old Posts/2016-05-22-flashing-esp8266.md
@@ -0,0 +1,102 @@
+# Flashing the ESP8266 with the Arduino IDE
+
+Flashing the ESP8266 with the newest version of the ESP8266/Arduino can be tedious with the off brand FTDI programmers.
+
+* * *
+
+## Problems with knockoff FTDI programmers
+
+The new version of ESP8266/Arduino offers different flashing methods than the previous versions, which are the CK and NodeMCU methods. These new methods allow the flashing tool to automatically reset the ESP8266 into boot loader mode. This is convenient if you have a NodeMCU or the right FTDI programmer. I have a cheap knock off FTDI programmer in which the CK flashing method does not work with.
+
+The table below shows the correct connections for using the esptool-ck method of flashing. The FTDI programmer that I use does not have the "RTS" pin. Alternatively it has a "CTS" pin. I figured the FTDI programmers were the exact same, but after attempting to flash with this method I was convinced otherwise.
+
+[The current version of ESP8266/Arduino uses the esptool-ck flashing method](https://github.com/igrr/esptool-ck)
+
+
+
+
+
+
+
+
Name
+
+
Description
+
+
+
+
+
+
+
+
+
+
none
+
+
No DTR/RTS manipulation
+
+
+
+
+
+
ck
+
+
RTS controls RESET or CH_PD, DTR controls GPIO0
+
+
+
+
+
+
wifio
+
+
TXD controls GPIO0 via PNP transistor and DTR controls RESET via a capacitor
+
+
+
+
+
+
nodemcu
+
+
GPIO0 and RESET controlled using two NPN transistors as in [NodeMCU devkit](https://raw.githubusercontent.com/nodemcu/nodemcu-devkit/master/Documents/NODEMCU_DEVKIT_SCH.png).
+
+
+
+
+
+
+
+
+
+## The Solution
+
+Unfortunately the current version of ESP8266/Arduino does not offer alternative methods of flashing. After hours of frustration I finally figured out a solution to the problem.
+
+The methods to flash the ESP8266 within the Arduino IDE can be adjusted. I first thought I needed to download another method to flash with such as the [esptool.py](https://github.com/themadinventor/esptool), but I found a much easier solution. The "boards.txt" file can be edited, which allowed more customization to the flashing settings within the Arduino IDE. This is the path on my system.
+
+/Users/$USER/Library/Arduino15/packages/esp8266/hardware/esp8266/2.1.0/boards.txt
+
+The reset method needs to be changed from "ck" to "none" in order for this to work properly.
+
+```bash
+generic.upload.resetmethod=ck
+```
+
+to
+
+```bash
+generic.upload.resetmethod=none
+```
+
+Because we are not using the CK flashing method, we need to boot up the ESP8266 into boot loader mode manually.
+
+```bash
+ GPIO0 -> gnd
+ VCC -> 3.3v
+ CH_PD -> 3.3v
+ GND -> gnd
+ TX -> RX
+ RX -> TX
+```
+
+The ESP8266 must be powered by an external 3.3v power supply, because the FTDI programmer cannot supply enough current. Also keep in mind that the ground of the FTDI programmer MUST be connected to the same ground that the ESP8266 is connected to. If this is not done it will not flash.
+
+This should solve any problems flashing with a knockoff FTDI programmer.
diff --git a/posts/Web Stuff/2016-08-25-redoing-website.md b/posts/Web Stuff/2016-08-25-redoing-website.md
new file mode 100644
index 0000000..dee5800
--- /dev/null
+++ b/posts/Web Stuff/2016-08-25-redoing-website.md
@@ -0,0 +1,27 @@
+# Redoing this website for the third time
+
+New web technologies never cease to amaze me. Every time I learn a new technology used in the web my mind is blown. Shortly after this happens
+I discover something newer that is just bigger and better. Because of this, I am always learning, which is awesome!
+
+***
+
+## It's been awhile
+
+It has been quite a long time since I posted anything on this site. Since the last post I've graduated college and started a career as a software engineer.
+I'm currently mainly working on front end development with AngularJS, which is pretty exciting! I previously used Angular on this site to help myself learn the framework.
+Angular is pretty great, but I've found a new web framework that I'm absolutely loving so far! It's a framework developed by Facebook called [ReactJS](https://facebook.github.io/react/).
+
+I've decided to completely redo this site again because I know I can do it better as I learn more and more. Credit for most of my design can be given to [Nikolay](http://nikolay.rocks).
+I love the simple design that he has come up with on his site. Some of the site is open source, but I am redoing a lot of it to my liking;
+
+The source code for this site can be found on GitHub [here](https://github.com/mgerb/mywebsite) (currently developing on the react branch);
+
+Here are some of the core items that I'm using to develop this site:
+- [Go](https://golang.org/)
+- [React](https://facebook.github.io/react/)
+- [Redux](http://redux.js.org/docs/introduction/)
+- [MongoDB](https://www.mongodb.com/)
+- [App Engine](https://cloud.google.com/appengine/)
+
+There are many other tools here and there such as [MarkedJS](https://github.com/chjj/marked) and [HighlightJS](https://highlightjs.org/)
+that I've also used in the process. I am excited to discuss my thoughts and experiences with many other technologies like this.
diff --git a/posts/resume.md b/posts/resume.md
new file mode 100644
index 0000000..e5c6a50
--- /dev/null
+++ b/posts/resume.md
@@ -0,0 +1,55 @@
+## Mitchell Gerber
+
+Hello, my name is Mitchell and I am pursuing a career in software engineering. I have a passion for creating things and learning new technologies.
+
+I always find enjoyment in building things, whether it's computers, drones, or software. I started programming upon entering college and I have been hooked ever since. Programming has become a hobby of mine and it has opened up many opportunities.
+
+My primary strengths include server side development in Java as well as Node.js. I have experience working with relational databases such as MySQL. I've recently become familiar working with MongoDB as well. I helped develop a web application for Digi International that is used to debug embedded devices for testing purposes. I worked with Java/JSP, which ran on a Jetty web server and used an H2 SQL database.
+
+My interest in developing things follows me home after work hours. I often lose track of time working on personal projects. I'm currently working on this personal website to learn Node.js and familiarize myself with newer web development technologies. In my free time I enjoy building and flying radio controlled unmanned aerial systems. I've also recently gained an interest in programming microcontrollers.
+
+
+
+
[](/?post=12-18-2015.html) [Sensor Project with ESP8266](/?post=12-18-2015.html)
+
+
+UAS Footage from one of my drone projects
+
+
+
+## Technical Skills
+
+I started with Java and have been working with it since the end of 2012\. I consider myself experienced in Java as I have used it for numerous projects throughout college as well as at my job as a Software Tester/Developer. I found my interest in web development in late 2014\. Since then I've become familiar with different back end languages including Node.js, PHP, and Java. I've also worked with MongoDB as well as relational databases such as MySQL.
+
+Beginning of Summer 2015 I started venturing into the category of microcontrollers. I've become familiar with programming the Arduino as well as a microcontroller called the ESP8266\. Throughout this process I've gained knowledge of working with C.
+
+As of late 2014 I've been using Linux as my primary operating system for software development, which has allowed me to become more familiar with Unix systems. I've also worked with Ubuntu server, which is used to host this website.
+
+## Related Experience
+
+* 2014-Present Software Developer/Tester - Digi International, WSU, Winona, MN
+
+ > * Conduct manual system tests on software.
+ > * Develop testing tools for debugging embedded devices
+ > * Develop firmware for an embedded system.
+ > * Participate in weekly conference calls and produce weekly status reports
+ > * Collaborate with others on software development projects.
+
+* 2011-2014 Technical Assistant - South Central Education Consortium, Grand Meadow, MN
+
+ > * Support 10-20 faculty and staff with software and hardware issues.
+ > * Set up and image computer labs
+
+## Education
+
+* 2012-2016 Bachelor of Science, Magna Cum Laude
+ Winona State University, Winona, MN
+ Major: Computer Science
+ Major GPA: 3.68
+ Dean's List: 6 semesters
+
+## Contacts
+
+* [mgerb42@gmail.com](mailto:mgerb42@gmail.com)
+* [GitHub](https://github.com/mgerb)
+* [LinkedIn](https://www.linkedin.com/in/mitchell-gerber-125391b3)
diff --git a/public/css/style.css b/public/css/style.css
deleted file mode 100644
index 56f4923..0000000
--- a/public/css/style.css
+++ /dev/null
@@ -1,338 +0,0 @@
-html {
- overflow-y: scroll;
-}
-
-body {
- font-family: Century Gothic,CenturyGothic,AppleGothic,sans-serif;
-}
-
-a {
- color: #00B7FF;
-}
-
-.textCenter {
- text-align: center;
-}
-
-.resume{
- font-size: 12pt;
- font-weight: 400;
-}
-.header {
- height: 400px;
- background: url("/public/images/headerBackground.jpg") center no-repeat;
- background-size: cover;
-}
-
-.headerText{
- font-size: 80px;
- color: white;
- margin-top: 0px;
-}
-
-.large-text{
- font-size: 100px;
-}
-
-.centerDiv{
- position: relative;
- top: 50%;
- transform: translateY(-50%);
-}
-
-.form-signin {
- max-width: 500px;
- padding: 15px;
- margin: 0 auto;
-}
-.form-signin .form-control {
- position: relative;
- height: auto;
- -webkit-box-sizing: border-box;
- -moz-box-sizing: border-box;
- box-sizing: border-box;
- padding: 10px;
- font-size: 16px;
-}
-
-.form-file {
- max-width: 500px;
- padding: 15px;
- margin: 0 auto;
-}
-.form-file .form-control {
- position: relative;
- height: 34px;
- -webkit-box-sizing: border-box;
- -moz-box-sizing: border-box;
- box-sizing: border-box;
- padding: 10px;
- font-size: 16px;
-}
-
-.colorRed {
- color: red;
-}
-.colorGreen {
- color: green;
-}
-
-.timeForm {
- width: 30%;
- display: inline;
-}
-
-.aboutMeImage {
- width: 100%;
- height: 100%;
-}
-
-.center {
- margin-left: auto;
- margin-right: auto;
- display: block;
-}
-
-/*
- * Override Bootstrap's default container.
- */
-
-@media (min-width: 1200px) {
- .container {
- width: 970px;
- }
-}
-
-
-/*
- * Masthead for nav
- */
-
-.blog-masthead {
- background-color: #428bca;
- -webkit-box-shadow: inset 0 -2px 5px rgba(0,0,0,.1);
- box-shadow: inset 0 -2px 5px rgba(0,0,0,.1);
-}
-
-/* Nav links */
-.blog-nav-item {
- position: relative;
- display: inline-block;
- padding: 10px;
- font-weight: 500;
- color: #cdddeb;
-}
-.blog-nav-item:hover,
-.blog-nav-item:focus {
- color: #fff;
- text-decoration: none;
-}
-
-/* Active state gets a caret at the bottom */
-.blog-nav .active {
- color: #fff;
-}
-.blog-nav .active:after {
- position: absolute;
- bottom: 0;
- left: 50%;
- width: 0;
- height: 0;
- margin-left: -5px;
- vertical-align: middle;
- content: " ";
- border-right: 5px solid transparent;
- border-bottom: 5px solid;
- border-left: 5px solid transparent;
-}
-
-
-/*
- * Blog name and description
- */
-
-.blog-header {
- padding-top: 20px;
- padding-bottom: 20px;
-}
-.blog-title {
- margin-top: 30px;
- margin-bottom: 0;
- font-size: 60px;
- font-weight: normal;
-}
-.blog-description {
- font-size: 20px;
- color: #999;
-}
-
-
-/*
- * Main column and sidebar layout
- */
-
-.blog-main {
- font-size: 18px;
- line-height: 1.5;
-}
-
-/* Sidebar modules for boxing content */
-.sidebar-module {
- padding: 15px;
- margin: 0 -15px 15px;
-}
-.sidebar-module-inset {
- padding: 15px;
- background-color: #f5f5f5;
- border-radius: 4px;
-}
-.sidebar-module-inset p:last-child,
-.sidebar-module-inset ul:last-child,
-.sidebar-module-inset ol:last-child {
- margin-bottom: 0;
-}
-
-
-/* Pagination */
-.pager {
- margin-bottom: 60px;
- text-align: left;
-}
-.pager > li > a {
- width: 140px;
- padding: 10px 20px;
- text-align: center;
- border-radius: 30px;
-}
-
-
-/*
- * Blog posts
- */
-
-.blog-post {
- margin-bottom: 60px;
-}
-.blog-post-title {
- margin-bottom: 5px;
- font-size: 40px;
-}
-.blog-post-meta {
- margin-bottom: 20px;
- color: #999;
-}
-
-
-/*
- * Footer
- */
-
-.blog-footer {
- padding: 40px 0;
- color: #999;
- text-align: center;
- background-color: #f9f9f9;
- border-top: 1px solid #e5e5e5;
-}
-.blog-footer p:last-child {
- margin-bottom: 0;
-}
-
-
-.lowerLeft{
- color: white;
- display: table-cell;
- vertical-align: bottom;
- height: 400px;
- width: 800px;
-}
-
-.colorWhite{
- color: white;
-}
-
-.mitchell-navbar{
- border-radius: 0 !important;
- background-color: #262626;
- border: 0;
-}
-
-.gist {
- width:600px !important;
-}
-
-.gist-file{
-
-}
-
-.gist-data{
- max-height: 500px;
- max-width: 600px;
-}
-
-.chart-legend li span{
- display: inline-block;
- width: 12px;
- height: 12px;
- margin-right: 5px;
-}
-
-.modal {
- display: none;
- position: fixed;
- z-index: 1000;
- top: 0;
- left: 0;
- height: 100%;
- width: 100%;
- background: rgba( 255, 255, 255, .8 )
- url('http://i.stack.imgur.com/FhHRx.gif')
- 50% 50%
- no-repeat;
-}
-
-/* When the body has the loading class, we turn
- the scrollbar off with overflow:hidden */
-body.loading {
- overflow: hidden;
-}
-
-/* Anytime the body has the loading class, our
- modal element will be visible */
-body.loading .modal {
- display: block;
-}
-
-.btn-file {
- position: relative;
- overflow: hidden;
-}
-
-.btn-file input[type=file] {
- position: absolute;
- top: 0;
- right: 0;
- min-width: 100%;
- min-height: 100%;
- font-size: 100px;
- text-align: right;
- filter: alpha(opacity=0);
- opacity: 0;
- outline: none;
- background: white;
- cursor: inherit;
- display: block;
-}
-
-input[readonly] {
- background-color: white !important;
- cursor: text !important;
-}
-
-.hide {
- display: none;
-}
-
-.show {
- display: inline;
-}
\ No newline at end of file
diff --git a/public/favicon.ico b/public/favicon.ico
deleted file mode 100644
index 5c788a8..0000000
Binary files a/public/favicon.ico and /dev/null differ
diff --git a/public/images/headerBackground.jpg b/public/images/headerBackground.jpg
deleted file mode 100644
index 352000e..0000000
Binary files a/public/images/headerBackground.jpg and /dev/null differ
diff --git a/public/images/headerBackground1.jpg b/public/images/headerBackground1.jpg
deleted file mode 100644
index 6270e9e..0000000
Binary files a/public/images/headerBackground1.jpg and /dev/null differ
diff --git a/public/images/loading.gif b/public/images/loading.gif
deleted file mode 100644
index e71ec0a..0000000
Binary files a/public/images/loading.gif and /dev/null differ
diff --git a/public/images/sensors.png b/public/images/sensors.png
deleted file mode 100644
index 5f406b8..0000000
Binary files a/public/images/sensors.png and /dev/null differ
diff --git a/public/js/IndexController.js b/public/js/IndexController.js
deleted file mode 100644
index 46b0523..0000000
--- a/public/js/IndexController.js
+++ /dev/null
@@ -1,36 +0,0 @@
-app.controller('IndexController', function($scope, $http) {
-
- var title = ["5-22-16", "1-4-16", "1-1-16", "12-29-15", "12-18-15", "10-28-15", "8-13-15", "7-28-15", "7-21-15"];
- $scope.posts = [];
-
- for (p in title) {
-
- var postName = title[p];
-
- //use anonymous function calls to pass
- //postName to the http callback function
- //pass value p to make sure $scope.posts is in order due to asynch function
- $http({
- method: 'GET',
- url: '/public/posts/' + postName + '.html'
- }).then((function(postName, p) {
- return function(response) {
-
- var html = response.data;
- var partial = {};
-
- partial.name = postName;
- partial.title = $(html).find('#title').html();
- partial.date = $(html).find('#date').html();
- partial.intro = $(html).find('#intro').html();
-
- $scope.posts[p] = partial;
- }
- })(postName, p), function errorCallback(response) {
- // called asynchronously if an error occurs
- // or server returns response with an error status.
- console.log("Error Loading Post");
- });
- }
-
-});
diff --git a/public/js/SensorInfoController.js b/public/js/SensorInfoController.js
deleted file mode 100644
index 3e8d05a..0000000
--- a/public/js/SensorInfoController.js
+++ /dev/null
@@ -1,202 +0,0 @@
-app.controller('SensorInfoController', function($scope, $http, $routeParams) {
-
- $scope.location = $routeParams.location;
-
- $http({
- method: 'GET',
- url: '/api/sensor/' + $scope.location
- }).then(function successCallback(response) {
- $scope.list = createYearObjects(response.data);
-
- if ($scope.list.length > 0) {
- $scope.selectedObject = $scope.list[0];
- $scope.selectedMonth = $scope.list[0].months[$scope.list[0].months.length - 1];
-
- $scope.loadingMonth = true;
- $scope.loadingYear = true;
-
- displayChart("info-chart-year", "legend-year", $scope.location, $scope.list[0].year, null, function() {
- $scope.$apply(function() {
- $scope.loadingYear = false;
- });
- });
- displayChart("info-chart-month", "legend-month", $scope.location, $scope.list[0].year, $scope.selectedMonth, function() {
- $scope.$apply(function() {
- $scope.loadingMonth = false;
- });
- });
-
- } else {
- $scope.selectedObject = {};
- $scope.selectedMonth = "";
- }
-
-
- }, function errorCallback(response) {});
-
- $scope.onYearChange = function() {
- resetCanvas("info-chart-year", "canvas1-id");
- resetCanvas("info-chart-month", "canvas2-id");
-
- $scope.loadingMonth = true;
- $scope.loadingYear = true;
-
- displayChart("info-chart-year", "legend-year", $scope.location, $scope.selectedObject.year, null, function() {
- $scope.$apply(function() {
- $scope.loadingYear = false;
- });
- });
-
- displayChart("info-chart-month", "legend-month", $scope.location, $scope.selectedObject.year, $scope.selectedObject.months[0], function() {
- $scope.$apply(function() {
- $scope.loadingMonth = false;
- });
- });
- }
-
- $scope.onMonthChange = function() {
- resetCanvas("info-chart-month", "canvas2-id");
- $scope.loadingMonth = true;
-
- displayChart("info-chart-month", "legend-month", $scope.location, $scope.selectedObject.year, $scope.selectedMonth, function() {
- $scope.$apply(function() {
- $scope.loadingMonth = false;
- });
- });
- }
-});
-
-function createYearObjects(data) {
- var list = [];
-
- for (i in data) {
-
- var exists = false,
- index = 0;
-
- for (j in list) {
-
- if (data[i].year == list[j].year) {
- exists = true;
- index = j;
- break;
- }
-
- }
-
- if (exists == true) {
-
- if (list[index].months.indexOf(data[i].monthname) < 0) {
- list[index].months.push(data[i].monthname);
- }
-
- } else {
- list.push({ year: data[i].year, months: [data[i].monthname] });
- }
-
- }
-
- return list;
-}
-
-function resetCanvas(canvas_id, container_id) {
- $("#" + canvas_id).remove(); // this is my
+ 
+