Gem boilerplate

This commit is contained in:
Fabio Rehm 2013-02-25 20:09:32 -03:00
parent 5d36067c0b
commit 48c03d288d
6 changed files with 67 additions and 0 deletions

View file

@ -5,6 +5,8 @@ unless ENV['USER'] == 'vagrant'
exit 1
end
gemspec
gem 'vagrant', github: 'mitchellh/vagrant'
gem 'rake'
gem 'net-ssh'

22
LICENSE.txt Normal file
View file

@ -0,0 +1,22 @@
Copyright (c) 2013 Fábio Rehm
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.

View file

@ -2,12 +2,14 @@
Highly experimental, soon to come, Linux Containers support for the unreleased Vagrant 1.1
## WARNING
Please keep in mind that this is not even alpha software and things might go wrong.
Although I'm brave enough to use it on my physical machine, its recommended that you
try it out on the Vagrant dev box ;)
## Development
On your host:
@ -27,6 +29,7 @@ cd /tmp/vagrant-lxc
/vagrant/lib/provider ssh
```
## Troubleshooting
If your container / dev box start acting weird, run `vagrant reload` to see if
@ -35,3 +38,12 @@ things get back to normal.
In case `vagrant reload` doesn't work, restore the VirtualBox snapshot that was
created automagically right after `./setup-vagrant-dev-box` finished by running
the same script again and selecting the `[r]estore snapshot` option when asked.
## Contributing
1. Fork it
2. Create your feature branch (`git checkout -b my-new-feature`)
3. Commit your changes (`git commit -am 'Add some feature'`)
4. Push to the branch (`git push origin my-new-feature`)
5. Create new Pull Request

7
lib/vagrant-lxc.rb Normal file
View file

@ -0,0 +1,7 @@
require "vagrant-lxc/version"
module Vagrant
module LXC
# Your code goes here...
end
end

View file

@ -0,0 +1,5 @@
module Vagrant
module LXC
VERSION = "0.0.1"
end
end

19
vagrant-lxc.gemspec Normal file
View file

@ -0,0 +1,19 @@
# -*- encoding: utf-8 -*-
lib = File.expand_path('../lib', __FILE__)
$LOAD_PATH.unshift(lib) unless $LOAD_PATH.include?(lib)
require 'vagrant-lxc/version'
Gem::Specification.new do |gem|
gem.name = "vagrant-lxc"
gem.version = Vagrant::LXC::VERSION
gem.authors = ["TODO: Write your name"]
gem.email = ["TODO: Write your email address"]
gem.description = %q{TODO: Write a gem description}
gem.summary = %q{TODO: Write a gem summary}
gem.homepage = ""
gem.files = `git ls-files`.split($/)
gem.executables = gem.files.grep(%r{^bin/}).map{ |f| File.basename(f) }
gem.test_files = gem.files.grep(%r{^(test|spec|features)/})
gem.require_paths = ["lib"]
end