github
Advanced Search
  • Home
  • Pricing and Signup
  • Explore GitHub
  • Blog
  • Login

fnando / pez

  • Admin
  • Watch Unwatch
  • Fork
  • Your Fork
  • Pull Request
  • Download Source
    • 3
    • 0
  • Source
  • Commits
  • Network (0)
  • Issues (0)
  • Downloads (0)
  • Wiki (1)
  • Graphs
  • Branch: master

click here to add a description

click here to add a homepage

  • Branches (1)
    • master ✓
  • Tags (0)
Sending Request…
Click here to lend your support to: pez and make a donation at www.pledgie.com ! Edit Pledgie Setup

Pledgie Donations

Once activated, we'll place the following badge in your repository's detail box:
Pledgie_example
This service is courtesy of Pledgie.

A simple tool to manage Ruby on Rails plugins from GIT and Subversion SCM — Read more

  cancel

http://github.com/fnando/pez

  cancel
  • Private
  • Read-Only
  • HTTP Read-Only

This URL has Read+Write access

Switched configuration checking; `config/pez.yml` first, then `~/.pezrc`. 
fnando (author)
Thu Oct 29 06:48:11 -0700 2009
commit  2044720413d9dcf066aee0a9251ab6561172aaba
tree    0b804f28a1cfd81421ae5abbd0c01dfa8958e199
parent  3f8f551766535ec9c45ee3ba97b8845387947101
pez /
name age
history
message
file .gitignore Loading commit data...
file History.txt
file README.markdown
file Rakefile
file VERSION
directory bin/
directory lib/
file pez.gemspec
directory templates/
README.markdown

Pez

  • http://github.com/fnando/pez

DESCRIPTION:

Pez is a simple tool to manage plugins from Git and Subversion repositories in a easy way. Instead of adding plugins to the project repository, Pez checkouts/clones the specified version to a temporary directory and creates a symlink to the Ruby on Rails plugin directory.

When Pez is asked to update the plugins, it runs the correct command in that directory, based on the repository type (Git or Subversion), which in turn is applied to the project through the symlink.

Pez allows different environments to update plugins from a different directory. So, when you deploy your Ruby on Rails application, you won't have to checkout/update all plugins again, unless you explicit say so.

Pez is based on Braid (which I never had it working) but way simpler.

INSTALLATION:

git clone git://github.com/fnando/pez.git
cd pez
rake gem:install

or

sudo gem install fnando-pez --source=http://gems.github.com

USAGE:

Run the command pez setup from your project root to create the file config/plugins.yml. Then you can manage plugins with the following commands:

# display general help
pez help

# display help for specific command
pez help [command]

# add a new plugin
pez add git://github.com/fnando/has_cache.git

# add a new plugin and specify repository type [svn, git]
pez add http://some-url.com/fnando/has_cache --type=svn

# update the repository
pez update has_cache

# update all repositories
pez update --all

# show info from all repositories
pez show --all

# remove plugin
pez remove has_cache

# remove all plugins
pez remove --all

# create symlink for plugins already added
pez symlink

# add plugin and track a specific branch (Git only)
pez add git://github.com/aslakhellesoy/cucumber -b html-visitor

# add plugin and freeze in a specific commit
pez add git://github.com/aslakhellesoy/cucumber \
    -r 32d4f03d19bf33172bb7b48fed48e906a56598a7

# add plugin and freeze in a specific revision
pez add svn://some/plugin -r 189

# specify the Rails environment.
# will set version following this order: 
# => RAILS_ENV, environment.rb version setting, defaults to 'development'
RAILS_ENV="production" pez add git://github.com/fnando/has_streams.git

# install, update and remove rails edge
pez add git://github.com/rails/rails.git --name=vendor/rails
pez update vendor/rails
pez remove vendor/rails

NOTE: If you specify a revision (-r or --revision), you won't be able to update the repository. To update it, edit the config/plugins.yml file and remove the revision option.

MAINTAINER

  • Nando Vieira (http://simplesideias.com.br)

CONTRIBUTORS

  • Arthur Zapparoli (http://arthurgeek.net)

LICENSE:

(The MIT License)

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the 'Software'), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED 'AS IS', WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

Blog | Support | Training | Contact | API | Status | Twitter | Help | Security
© 2010 GitHub Inc. All rights reserved. | Terms of Service | Privacy Policy
Powered by the Dedicated Servers and
Cloud Computing of Rackspace Hosting®
Dedicated Server