https://github.com/fnichol/opscode
Opscode - An Infrastructure Code Workflow Tool
https://github.com/fnichol/opscode
Last synced: 2 months ago
JSON representation
Opscode - An Infrastructure Code Workflow Tool
- Host: GitHub
- URL: https://github.com/fnichol/opscode
- Owner: fnichol
- License: other
- Created: 2014-04-01T15:26:09.000Z (about 11 years ago)
- Default Branch: master
- Last Pushed: 2014-04-11T20:17:04.000Z (about 11 years ago)
- Last Synced: 2025-04-10T09:57:03.992Z (2 months ago)
- Language: Ruby
- Homepage: http://fnichol.github.io/opscode
- Size: 609 KB
- Stars: 4
- Watchers: 3
- Forks: 1
- Open Issues: 1
-
Metadata Files:
- Readme: README.md
- License: LICENSE.txt
Awesome Lists containing this project
README
# Opscode: An Infrastructure Code Workflow Tool
[](http://badge.fury.io/rb/opscode)
[](https://travis-ci.org/fnichol/opscode)
[](https://codeclimate.com/github/fnichol/opscode)
[](https://gemnasium.com/fnichol/opscode)Unify your source code management tools into a single development/release workflow that can be used by your entire team. Opscode is a minimal, zero dependency Ruby library that screams simplicity. Currently most major SCM tools are supported, including:
* [Git](http://git-scm.com/)
* [Mercurial](http://mercurial.selenic.com/)
* [Darcs](http://darcs.net/)
* [Bazaar](http://bazaar.canonical.com/)
* [Fossil](http://www.fossil-scm.org/index.html/doc/tip/www/index.wiki)
* [Subversion](https://issues.apache.org/jira/plugins/servlet/mobile#issue/INFRA-7524)
* [CVS](http://www.nongnu.org/cvs/)
* [Perforce](http://www.perforce.com/)
* [Team Foundation Server](http://msdn.microsoft.com/en-us/vstudio/ff637362.aspx)
* [Visual SourceSafe](http://msdn.microsoft.com/en-us/library/3h0544kx.aspx)## Installation
Add this line to your application's Gemfile:
gem 'opscode'
And then execute:
$ bundle
Or install it yourself as:
$ gem install opscode
## Usage
After installation, you will have an `opscode` command to run your various workflows.
To check the installed version:
$ opscode version
Other commands depend on your chosen SCM tool. For example, using the default Git implementation:
$ opscode checkout https://github.com/opscode/chef.git
To use another SCM tool you will need to export an environment variable `OPSCODE_SCM`. For example, to use Subversion:
$ export OPSCODE_SCM=svn
$ opscode checkout https://github.com/opscode/chefMore detailed usage depends on your SCM tool, but most will provide more information with:
$ opscode help
## Development
* Source hosted at [GitHub][repo]
* Report issues/questions/feature requests on [GitHub Issues][issues]Pull requests are very welcome! Make sure your patches are well tested.
Ideally create a topic branch for every separate change you make. For
example:1. Fork the repo
2. Create your feature branch (`git checkout -b my-new-feature`)
3. Commit your changes (`git commit -am 'Added some feature'`)
4. Push to the branch (`git push origin my-new-feature`)
5. Create new Pull RequestCreated and maintained by [Fletcher Nichol][fnichol] ()
Apache 2.0 (see [LICENSE.txt][license])
## FAQ
* **"How would I start using this with my team?"**
Ummmmm... are you sure you want to?
* **"Is this legit?"**
Ummmmm... does it look legit?
* **"What features are on the roadmap?"**
Ummmmm... does this project need a roadmap?[license]: https://github.com/fnichol/opscode/blob/master/LICENSE.txt
[fnichol]: https://github.com/fnichol
[repo]: https://github.com/fnichol/opscode
[issues]: https://github.com/fnichol/opscode/issues
[contributors]: https://github.com/fnichol/opscode/contributors