rapp 0.2.2 → 0.2.3

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: c296df48d1c482b07ddf0e3d09092bad7966b3e7
-  data.tar.gz: 5d4a5c69a4b7a0fd42cc8baaadf4ab4950de7e8f
+  metadata.gz: 5bd904e61a3025abe32f14c1250c8473efff3127
+  data.tar.gz: 53181c8dec42473a235b304ac37864d8bc5f5ddb
 SHA512:
-  metadata.gz: 4212bda2d439e05d0c0ade2d93aa2c9cc47996483a83d63cfd9ffdb403897fd1aeb3b8cb762a9e47ceb6279e976e48721d4ed93dc4fcfe60d9a7cdfaf9163d7a
-  data.tar.gz: cac8b975f8e35fb4ff8261152e4a8ac9b7219716a1a52fe1b799328459722652d3020fbedd5fbd2534275792ea5109a8a9399e0f2c02c7741f8769db49021e9f
+  metadata.gz: 4051322416bc5853c94304bf34bdd3932e9546597eb59c19410e86c8d8b8f7dd1e2580f851de1134195e5aa7ab928b6825a5c56b2474785c278668e78e3ab37f
+  data.tar.gz: ab248896fa572d189784b90f85d7338fa307e6a29507b49d993ca4f7c5dd96bd71fb6fee7f6b479d0dd6c080da64fb78a05e81fabcb97bf69044658d9607c619

data/README.md

@@ -30,15 +30,15 @@ Currently, Rapp is in early development, and additional features are forthcoming
 
 ### Ethos
 
-Rapp is not a framework for running an app. In the future, there may be additional helpers to configure very common components in the ruby community, but the overall goal is to hand you a working application with a few common niceties, then get out of your way. Once you've generated the Rapp, the project is yours to do with as you see fit - the gem itself is not a dependency of the app you create.
+Rapp is not a framework for running an app. In the future, there may be additional helpers to configure very common components in the ruby community, but the overall goal is to hand you a working application with a few common niceties, then get out of your way. Once you've generated the Rapp project, ir is yours to do with as you see fit - the gem itself is not a dependency of the app you create.
 
-Rapps are shells to house your app, in a familiar layout, to prevent you from having to write the same boring boilerplate time and time again.
+Rapp projects are shells to house your app, in a familiar layout, to prevent you from having to write the same boring boilerplate time and time again.
 
 Rapp is in no way shape or form meant for building web applications. You are free to attempt this if you wish, but if thats your goal, you're much better off with Rails, Sinatra, pure Rack, or any number of alternatives.
 
-### Creating a new Rapp
+### Creating a new Rapp project
 
-Creating a new Rapp is simple
+Creating a new Rapp project is simple
 
 ```shell
 rapp my_new_rapp
@@ -50,11 +50,11 @@ If the command executed successuflly, you should see a report displaying the fol
 
 ### Dependencies
 
-Rapp only installs 2 dependencies into your application - bundler and rake. Eventually, It will also include rspec, as well as a suite of specs for you to run to validate that the core underpinnings of Rapp are working as expected, in addition to your own custom specs.
+Rapp projects only have 2 dependencies - bundler and rake. Optionally, it will also include rspec, as well as a suite of specs for you to run to validate that the core underpinnings of the project are working as expected, in addition to your own custom specs.
 
 ### Layout
 
-Rapp application structure looks like the following:
+Rapp project structure looks like the following:
 
 * app/
 * app/models/
@@ -66,7 +66,7 @@ Rapp application structure looks like the following:
 * config/initializers/
 * lib/
 * lib/tasks/
-* spec/
+* spec/ (optional)
 * {app_name}.rb
 * {app_name}_base.rb
 * Gemfile
@@ -113,19 +113,15 @@ These are loaded after Bundler, but before anything in app/
 
 Used for the same purpose as a Rails app or Ruby gem. Any code that falls outside of the norms of app/ would be placed here. Additionally, you may place tasks in lib/tasks/, and they will be registered via the Rake integration
 
-### Spec directory
-
-Mostly reserved for future use, this is where both Rapp specific specs to ensure the well-being of your core application will reside, as well as application specific specs that you write to ensure your custom logic and behaviors are working correctly (You are writing tests... right?)
-
 ### Rake
 
 Currently, Rapp comes with 1 predefined rake task, which is "console". This will boot up irb while loading your {app_name}.rb, which will load the rest of your app. This is aliased to "c" for convenience.
 
-### Specs
+### Specs (Optional)
 
-Optionally you can generate specs for your app to test the underpinnings of what Rapp has created. You can do this by specifying the ```--specs``` or ```-s``` flags on the command line.
+You can generate specs for your app to test the underpinnings of what Rapp has created. You can do this by specifying the ```--specs``` or ```-s``` flags on the command line.
 
-These specs aim to not be in the way of you writing your own specs, and so the spec_helper is sparse, and the generated specs attempt to not include a test for {app_name}, but rather {app_name}_base, so that you can do any {app_name} specific testing in that file yourself.
+These specs aim to not be in the way of you writing your own specs, and so the spec_helper is sparse, and the generated specs attempt to not include a test for {app_name}, but rather {app_name}_base, so that you can do any {app_name} specific testing in that file yourself if you so choose.
 
 Mainly, these are here to help you make changes to a Rapp project once it's been generated if you so need, being able to verify that the core behaviors still function.
 
@@ -135,7 +131,9 @@ At the moment, this gem serves to fit a need that I found myself having and figu
 
 1. Generate increased / improved specs for the users application
 2. General code cleanup. Much of the code is prototypical and is not as DRY as it could be (ex: the builder class)
-3. Test ease of use integrating Chore / Sidekiq like job systems
+3. Dotenv integration for ease of local development w/ sample file containing all env vars
+4. Configurable logging level from the environment
+5. Test ease of use integrating Chore / Sidekiq like job systems
 
 ## Contributing
 

data/lib/rapp/builder.rb

@@ -15,6 +15,7 @@ module Rapp
     "config/initializers",
     "lib",
     "lib/tasks",
+    "log"
   ]
 
   SpecStructure = [

data/lib/rapp/templates/app_name_base.rb.erb

@@ -1,4 +1,5 @@
 require 'env'
+require 'logger'
 
 module <%= class_name %>Base
   
@@ -15,8 +16,8 @@ module <%= class_name %>Base
     end
   
     def logger
-      @logger ||= Logger.new(ENV['APP_LOG_PATH'] || "./log/app.log").tap do |l|
-        l.level = Logger::DEBUG
+      @logger ||= ::Logger.new(ENV['APP_LOG_PATH'] || "./log/<%= app_name %>.log").tap do |l|
+        l.level = ::Logger::DEBUG
         l.formatter = lambda do |severity, datetime, progname, msg|
            "[#{datetime} (#{Process.pid})] #{severity} : #{msg}\n"
         end

data/lib/rapp/version.rb

@@ -1,3 +1,3 @@
 module Rapp
-  VERSION = "0.2.2"
+  VERSION = "0.2.3"
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: rapp
 version: !ruby/object:Gem::Version
-  version: 0.2.2
+  version: 0.2.3
 platform: ruby
 authors:
 - StabbyCutyou
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2015-01-19 00:00:00.000000000 Z
+date: 2015-01-21 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: bundler