* backwards compatibility for settings refactor

* testing

* deprecation warnging

* Fix for docker deploy

* use version of current amber

* changed to lowercase

* formatting

Application controller was not being loaded in the correct order when using
`require "./src/controller/*"`.

To correct the error loaded application_controller first. Also did a little formatting for 
readability

The MIME media type for JSON text is application/json. The default encoding is UTF-8. (Source: RFC 4627).

Currently checking content_type with == will not match content type formats for `application/json;charset=UTF-8`

With this change the check for content type application/json should be correct.

* fix method signature to match Channel

* fix others as well

When defining a socket endpoint it withing route it currently
throws an error socket_endpoint method is not defined. This is due to
the fact that the socket_endpoint is not accessible through the routes

In order to correct the bug a websocket method was defined in place of
socket_endpoint in DSL::Router

Changes:

- Adds websocket as a  method instead of macro to Router DSL (See #224)
- Adds specs to ensure socket endpoint are defined
- Removes socker_endpoint from Amber::Server
- Makes socket_routes public

This changes the current API from socket_endpoint to websocket since
this naming was to honor proposed changes in
https://github.com/amber-crystal/amber/pull/224

* working

* added the right things to gitignore

* magic and trained dragons

* cleaned up specs

* ensure deletion of test files

* moved files to tmp

* test directory in tmp. also added to .gitignore

* tests encryption

* progress

* so much work

* left key_generator temporarily

* tests pass and settings load

* added ENV redis_url back

* loading settings from config file

* specs that test the environment loader

* tested how settings can be overridden.

* new commands encrypts production.yml by default

* fixed tests for encrypting by default

* encrypts only production on new and then tests if test can be encrypted

* debugging travis

* set env to test

* removed debugging code

* travis will probably pass at least

* travis will work now

* i hate order dependent tests

* add websocket macro

* specify module

* Fix quote

* Fix quote

* no longer needed

* no longer used

The current implementation of the command spec has a dependency on sed
command.

This addresses the issue by removing the sed dependency
Replaces the amber github string with a local path

With those changes we remove the external dependency on sed command and
allow us to run test consistently.

NOTE:

This test could serve as a regression test for the generated app.

* Cleaned up PR template.

* cleaned up templates

* Add ArchLinux on installation section

* Fix position of ArchLinux documentation

* Bumped version number to v0.2.0.

* updated readme to represent the current state of the project.

* fixed migration docs

* Removes and Adds helper server methods

- Why is this change necessary?

Some of the calls to the server instance was invoking multiple methods
for example Amber::Server.instance.pubsub_adapter.instance, with the
changes this now reads as Amber::Server.pubsub_adapter making it easy to
change without reworking the caller.

- How does it address the issue

The resulting changes tends to be more maintainable and adaptable making
the code more readable to the developer.

- What side effects does this change have?o

Narrow interfaces, giving access to only as much information as it needs to do
its job, as each method needs to know about a small set of methods of closely related objects

High number of class methods

* fixup! Removes and Adds helper server methods

* fixup! Removes and Adds helper server methods

* fixup! Removes and Adds helper server methods

* fixup! Removes and Adds helper server methods

* fixup! Removes and Adds helper server methods

* fixup! Removes and Adds helper server methods

* Bumped version number to v0.2.0.

* Bumped version number to v0.2.1.

one bug didn't get merged

* Remove amber directories from spec and src

Moves the cmd directory outside of the amber directory and renames
the core directory to Amber.

Modules namespaces conventions should follow a directory structure
where/when possible to keep the project cohesive and to understand
where things are. For instance Amber::Controller should point to
amber/controller directory.

Currently there is a mismatched directory to module structure because
of the core directory, amber/core/controller but the module is
still Amber::Controller I tried/consider renaming the modules to include
core, but it was just not right and the module namespacing became
unnecessarily too long eg Amber::Core::Controller. For this reason,
is better keep amber instead of core to maintain cohesion and logical
file structure.

This addresses the concern by

- Removes the extra amber directory from src and spec directory.
- Cleans and consolidates the specs
- Organizes the spec directories
- Changes namespace from Amber::CMD to Amber::CLI
- Adds Server directory for server related classes/modules
- It runs generated specs for the generated app
- Cleaner source dir
```crystal
-- src
  -- amber
  -- cli
  amber.cr
```

What side effect does this change have

- Since merging Amber::CLI with Amber CLI specs run with the Amber
suite causing it to be slower.

* minor bug fix

* another path issue

* fixes compilation issues

* run migrate and seed for auth generator

* fixed checkbox in template.k

* fixes compilation issues

* run migrate and seed for auth generator

Small controller generator change.