🤘 Yeah baby, we are getting to 1.0 🤘

This commit is contained in:
Fabio Rehm 2014-03-12 23:59:02 -03:00
parent c48261a5e5
commit 14430908f8
4 changed files with 10 additions and 6 deletions

View file

@ -1,4 +1,4 @@
## [0.8.1](https://github.com/fgrehm/vagrant-lxc/compare/v0.8.0...master) (unreleased) ## [1.0.0.beta1](https://github.com/fgrehm/vagrant-lxc/compare/v0.8.0...master) (unreleased)
DEPRECATIONS: DEPRECATIONS:

View file

@ -39,7 +39,7 @@ GIT
PATH PATH
remote: . remote: .
specs: specs:
vagrant-lxc (0.8.1.dev) vagrant-lxc (1.0.0.beta1.dev)
GEM GEM
remote: https://rubygems.org/ remote: https://rubygems.org/

View file

@ -9,14 +9,18 @@ as an alternative to the built in VirtualBox provider for Linux hosts. Check out
[this blog post](http://fabiorehm.com/blog/2013/04/28/lxc-provider-for-vagrant/) [this blog post](http://fabiorehm.com/blog/2013/04/28/lxc-provider-for-vagrant/)
to see it in action. to see it in action.
**NOTICE:** The master branch is targetting an initial beta for 1.0.0, for the
latest stable version of the plugin, please check the [0.8-stable](https://github.com/fgrehm/vagrant-lxc/tree/0.8-stable)
branch.
## Features / Limitations
## Features
* Provides the same workflow as the Vagrant VirtualBox provider * Provides the same workflow as the Vagrant VirtualBox provider
* Port forwarding via [`redir`](http://linux.die.net/man/1/redir) * Port forwarding via [`redir`](http://linux.die.net/man/1/redir)
* Does not support public / private networks
* Assumes you have a `lxcbr0` bridge configured on your host similar to [Ubuntu's built-in](https://help.ubuntu.com/lts/serverguide/lxc.html#lxcbr0)
As of now, it does not support public / private networks, but [private networks](https://github.com/fgrehm/vagrant-lxc/issues/120)
will be coming along _soon_.
## Requirements ## Requirements

View file

@ -1,5 +1,5 @@
module Vagrant module Vagrant
module LXC module LXC
VERSION = "0.8.1.dev" VERSION = "1.0.0.beta1.dev"
end end
end end