fredit 0.1.7 → 0.1.8

data/Gemfile

@@ -1,4 +1,5 @@
 source "http://rubygems.org"
+source "http://gems.github.com"
 
 gemspec
 

data/README.md

@@ -1,10 +1,10 @@
 # fredit: front-end edit
 
-`fredit` is a very simple, no-frills Rails 3 Engine that lets you edit your
+fredit is a very simple, no-frills Rails 3 Engine that lets you edit your
 Rails application's view templates, css stylesheets, and javascript
 files (a.k.a front-end files) through the browser.
 
-`fredit` injects an edit link into every view template. These edit links
+fredit injects an edit link into every view template. These edit links
 are visible wherever the template is rendered, whether it is a layout,
 a page, or a partial. 
 
@@ -17,10 +17,10 @@ and alter the underlying source files.
 <img style="width:300px" src="https://github.com/danchoi/fredit/raw/master/screens/fredit.png"/>
 
 In addition to view templates, stylesheets and javascript files are
-accessible through a file selection drop down at the top of the `fredit`
+accessible through a file selection drop down at the top of the fredit
 edit page. 
 
-You can also create and delete front-end files on the `fredit` edit page.
+You can also create and delete front-end files on the fredit edit page.
 
 **NOTE: Currently only the ERB Rails template handler is supported.**
 You are welcome to fork and add support for Haml and other template
@@ -54,19 +54,19 @@ addition to being quite heavyweight, this approach is too restrictive when
 you want to give your collaborator as much control over the front-end as
 he or she can handle.
 
-`fredit` lets a collaborator make significant front-end contributions to a Rails
-application without the hassles of having to set up and run a local
-instance of it on their computer. Just run a `fredit`-enabled instance of
-your Rails app on a server that your collaborator can access through his
-or her browser. This `fredit`-enabled instance can have its own Rails
+fredit lets a collaborator make significant front-end contributions to a
+Rails application without the hassles of having to set up and run a
+local instance of it. Just run a fredit-enabled instance of your Rails
+app on a server that your collaborator can access through his or her
+browser. This fredit-enabled instance can have its own Rails
 environment, database, and git branch. 
 
 
 ## Install and setup
 
-`fredit` requires Rails 3.
+fredit requires Rails 3.
 
-`fredit` works best as a gem you include in a specific Rails
+fredit works best as a gem you include in a specific Rails
 environment. Put something like this in the `Gemfile` of your Rails app:
 
     source 'http://rubygems.org'
@@ -80,28 +80,28 @@ environment. Put something like this in the `Gemfile` of your Rails app:
 and then run `RAILS_ENV=staging bundle install`, adjusting the
 `RAILS_ENV` to your target environment.
 
-To run your Rails app with `fredit`, just start it in the Rails
-environment Gemfile group you put the `fredit` gem in. When you hit the
+To run your Rails app with fredit, just start it in the Rails
+environment Gemfile group you put the fredit gem in. When you hit the
 app in the browser, you should see the injected view template links and
-be able to click through them to `fredit`'s source code editor.
+be able to click through them to fredit's source code editor.
 
 
 ## fredit with git 
 
-`fredit` assumes that the Rails instance it is running on is a cloned git
+fredit assumes that the Rails instance it is running on is a cloned git
 repository. **It also assumes that you have set the current branch of
 this git repository to the one you want your collaborator's changes
 committed to.**
 
-When your collaborator makes changes, `fredit` will commit those changes
+When your collaborator makes changes, fredit will commit those changes
 on the current git branch of this clone of the git repository. There is
-a form field in the `fredit` editor for the collaborator to enter git
+a form field in the fredit editor for the collaborator to enter git
 author information and a git log message. These bits of information
 will be added as metadata to the git commit.
 
 When you're ready to review and merge the changes your collaborator made
-via `fredit`, it's all just a matter of working with git commits and
-branches. You can set up client-side git hooks on the `fredit`-enabled
+via fredit, it's all just a matter of working with git commits and
+branches. You can set up client-side git hooks on the fredit-enabled
 clone to notify you when your collaborator has made changes, to
 automatically push those changes to the appropriate branch in the
 upstream repository, run a CI build server, etc.
@@ -109,10 +109,20 @@ upstream repository, run a CI build server, etc.
 
 ## Security
 
-`fredit` has basic security features, on top of which you can add anything
-you want. At a minimum, `fredit` will not allow any user to use the `fredit`
-web interface to edit a file above or outside the Rails application root
-directory of that Rails instance.  
+fredit has rudimentary security features. fredit will not allow any user
+to use the fredit web interface to edit a file above or outside the
+Rails application root directory of that Rails instance.  But this still
+leaves things like database.yml configurations accessible to the fredit
+editor. Anyone with access to the fredit editing interface will have the
+power to run arbitrary SQL on your environment's database.
+
+So please take additional precautions to make sure that your
+fredit-enabled Rails instance is not accessible by hostile strangers.
+At a minimum, use Apache Basic Authentication or the like to restrict
+access to this entire Rails instance. 
+
+It's probably not a good idea to run a fredit-enabled Rails app on a
+server with important stuff on it. Use a scratch staging server.
 
 
 ## Contribute

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: fredit
 version: !ruby/object:Gem::Version
-  version: 0.1.7
+  version: 0.1.8
   prerelease: 
 platform: ruby
 authors:
@@ -13,7 +13,7 @@ date: 2011-10-25 00:00:00.000000000Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: git
-  requirement: &76083830 !ruby/object:Gem::Requirement
+  requirement: &70153551354840 !ruby/object:Gem::Requirement
     none: false
     requirements:
     - - ! '>='
@@ -21,7 +21,7 @@ dependencies:
         version: '0'
   type: :runtime
   prerelease: false
-  version_requirements: *76083830
+  version_requirements: *70153551354840
 description: Edit the front end of Rails apps through the browser.
 email:
 - dhchoi@gmail.com
@@ -29,20 +29,20 @@ executables: []
 extensions: []
 extra_rdoc_files: []
 files:
-- app/views/layouts/fredit.html.erb
-- app/views/fredit/show.html.erb
-- app/views/fredit/revision.html.erb
 - app/controllers/fredit_controller.rb
-- lib/fredit.rb
-- lib/fredit/erb31.rb
-- lib/fredit/erb.rb
+- app/views/fredit/revision.html.erb
+- app/views/fredit/show.html.erb
+- app/views/layouts/fredit.html.erb
 - lib/fredit/engine.rb
+- lib/fredit/erb.rb
+- lib/fredit/erb31.rb
+- lib/fredit.rb
 - config/routes.rb
 - MIT-LICENSE
 - Rakefile
 - Gemfile
 - README.md
-homepage: 
+homepage: https://github.com/danchoi/fredit
 licenses: []
 post_install_message: 
 rdoc_options: []
@@ -56,7 +56,7 @@ required_ruby_version: !ruby/object:Gem::Requirement
       version: '0'
       segments:
       - 0
-      hash: -247553329
+      hash: -4259262550981050776
 required_rubygems_version: !ruby/object:Gem::Requirement
   none: false
   requirements:
@@ -65,10 +65,10 @@ required_rubygems_version: !ruby/object:Gem::Requirement
       version: '0'
       segments:
       - 0
-      hash: -247553329
+      hash: -4259262550981050776
 requirements: []
 rubyforge_project: 
-rubygems_version: 1.8.11
+rubygems_version: 1.8.6
 signing_key: 
 specification_version: 3
 summary: Edit the front end of Rails apps through the browser.