Introducing Lotus::Environment as object who's responsbile to deal with env vars and cli options
Removed file commited by mistake
Let Lotus::Configuration to set the proper host/port according to the command line args that we pass to 'lotus server'
Lotus::Environment refactoring: extract private method for better readability
Make Lotus::Environment thread-safe
Ensure to reset env vars for Lotus::Configuration tests
Removed from configuration port conventions about the current scheme. Only let the current env and the explicit configuration to set this value.
Discard a 'let' declaration in server test, in favor of an inlined value
Merge pull request #39 from lotus/environment

Environment
Add a simple `lotus console` command

`lotus console` will spawn an IRB (or Pry, if bundled) session that
loads the application code. This is a very basic analogue to `rails
console` and would be nice for testing out code ideas or modifying the
database.

Signed-off-by: David Celis <me@davidcel.is>
Use `Environment` in the console command

Signed-off-by: David Celis <me@davidcel.is>
Merge pull request #37 from davidcelis/console-command

Add a simple `lotus console` command
Future proof code: stay with Minitest defaults
Added --engine option to 'lotus console' command. Lotus::Console cleanup. Don't require 'irb' while testing Lotus::Console.
Add a call to root in the microservices examples

The microservices example as documented will currently not work, as the load_paths references `controller` and `views` directories inside the microservice's directory without setting the root of the application properly.

This change updates the example to have it work correctly.
Merge pull request #41 from ryanbrunner/master

Add a call to root in the microservices examples
Handling different application configs per environment
Merge branch 'pkurek-config_per_env'
Refactoring for Lotus::Configuration's multiple environments support