Stated implementing Admin UI. SASS Fix for admin UI
* App changes from grid system to full page app when visiting
  admin interface
* Category editor sass is now using foundation sass var for primary color
CSS Fixes for admin ui side navigation
* Fixing overflow-y for sidebar
Temporarily removing auth from board/thread import.
Import on API atomic per model.
Import should error with actual error.
Extracted header, footer, admin header/sidebar into partials
* Moved header,footer,modals into partial templates loaded with
  ng-include
* Using ng-switch instead of ng-show this will prevent the loading of
  unused partials
Moved pre and configs/handlers for api routes into single files
* This fixes unnecessary nesting of the api folder
CSS fix for admin sidebar
Protect admin routes with authentication
* Requiring user to be logged in to see admin routes
* Still need to implement check for if user is admin
* User is redirected to / if they are not authenticated and try to visit
  the admin routes
* Adding 'protect' boolean to routeProvider route will now redirect the
  user from that route if they are not authenticated
Added logic to check if user is admin before loading admin partials
* Prevents requests from downloading admin partial templates when
  user is not authenticated as admin
* TODO: need to add check to see if user is an administrator, currently
  only checking if a user is authenticated.
Updated posts pre-processing image hotlinking

Update the posts pre-processing image hotlinking to replace the image
src with a url that points to the image cdn. The image src is only
substituted if the cdnUrl config option is setup.
Image Cdn server

Added an image cdn server that is run along with the main epochtalk
server. This image cdn server basically serves to act as a proxy to
route hotlinked images from another domain. This adds a layer of
security by putting all hotlinked images behind another domain. The
hotlink image urls are generated by the posts pre-processor. The url
scheme for images turns the generated urls into a url for the server to
retrieve the images from and pass on to the user.

The url scheme is as such /images/{method hash}/{url cipher}
The method hash indicates if this image is a hotlinked image. It is
basically just the word 'hotlink' with a sha256 hash.
The url cipher is the url of the image encrypted with AES256. This was
chosen because it can then be decrypted on the image cdn and the url can
be routed through the image server.
Updated post validation for merge conflict

There was a merge conflict for post validation. This fixes it to use the
proper syntax.
Expanded the editor to handle file uplaods

The Editor has been rewritten to allow more content and tools to fix
into the directive. The first step was to update the CSS to utilize
foundation. The second step was to updated the HTML and pull in the
editor and preview titles into the editor rather than have them defined
outside the editor every time.

One service and one extra directive was created to support file uploads.
The directive allows access to HTML5's File API to keep track of files
selected by the user from their hard drive. The service is a generic
upload service that uses FormData to upload the file to the image cdn
server. This may be removed later so that uploads go directly to s3.
Updated new Thread for updated editor

This commit updates the editor used on the new Thread page to match the
new version of the editor.
Removed upload to image cdn server code

Removing all code related to uploading straight to the image cdn server
in favor of starting work on uploading directly to s3 from the client.
Removed ng-cookies

It is not being used at all right now.
Removed the file_model directive

Removed the file model directive because the model for input type=file
is being handled by the editor directive itself
Updated the editor directive to handle s3 uploads

Updated the editor to handle s3 uploads.
Pulled s3 policy creation into main server

Moved the s3 policy creation route into the main server from the image
cdn server. This is to avoid issuing CORS from the image cdn server.
Also, authentication and configurations can all be kept on ther main
server.

The image cdn server was also updated to handle s3 uploaded image urls.
The image cdn server also replaced request with hapi.proxy because it
can be set to pass along the header from s3. The image module has also
switched to sha1 for image method param generation and the handling of
the image proxying has been tighten up a little bit as well.