vagrant-parallels 1.0.6.rc1 → 1.0.6

Sign up to get free protection for your applications and to get access to all the features.
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA1:
3
- metadata.gz: c81c8a8004ab4f04103fe026fe8336bceb20087d
4
- data.tar.gz: 7c35af159575f21dc35bea6d6b975ebb7e3449c8
3
+ metadata.gz: c730a520f86bd6a644552153dc93e37bb88e2101
4
+ data.tar.gz: e7a1c78c9bc2632dde5215ff010926beb7168a3d
5
5
  SHA512:
6
- metadata.gz: 761ef849dd461d789b1826e347c4e42278123995083a5bea95b88f05cf7a11ec1c62b5ee3cce359ee193769bbed5cf4f01e86bd7448d43dfc9a117425d0c7eac
7
- data.tar.gz: 658d8e9a2b6eebff58b9b343ebfedf33df44bbf6644ace802068c89668122826077e691b5bf6df811be0aabed5dc9fdbb294bdf37086972d5e5b1f6af9f170cf
6
+ metadata.gz: 7e9eff6c30ec5fb09d20b8b6422c92e0bd3d2869c56a89ab31e27938a62c4e9b0b97b634beb97ac35c00af25c0fb9fe9291a7af2d576d635aaf16bf90ed654d4
7
+ data.tar.gz: ac7b0e602a129cfc0075fbb68cc1e71f4f718d0bca81bdb3d14a45ac4d32019fa88955ef12a10a330a73510c469a5519bfa09464f396cd192a42ab858e56ba46
data/README.md CHANGED
@@ -15,7 +15,7 @@ If you're just getting started with Vagrant, it is highly recommended that you
15
15
  read the official [Vagrant documentation](http://docs.vagrantup.com/v2/) first.
16
16
 
17
17
  ## Features
18
- The Parallels provider supports all basic Vagrant features, except one:
18
+ The Parallels provider supports all basic Vagrant features, except the next:
19
19
  **"Forwarded ports" configuration is not available yet**.
20
20
 
21
21
  It might be implemented in the future, after the next release of Parallels
@@ -32,110 +32,17 @@ Since the Parallels provider is a Vagrant plugin, installing it is easy:
32
32
  $ vagrant plugin install vagrant-parallels
33
33
  ```
34
34
 
35
- #### Compatibility with Vagrant 1.4
36
- We recommend that you to use the latest version of [Vagrant](http://www.vagrantup.com/downloads.html).
37
- If for any reason you want to use a previous version of Vagrant (1.4.x), you
38
- should install a compatible version of the Parallels provider as described below:
35
+ ## Provider Documentation
39
36
 
40
- ```
41
- $ vagrant plugin install vagrant-parallels --plugin-version 0.2.2
42
- ```
43
-
44
- ## Usage
45
- Parallels provider is used just like any other provider. Please read the general
46
- [basic usage](http://docs.vagrantup.com/v2/providers/basic_usage.html) page for
47
- providers.
48
-
49
- The value to use for the `--provider` flag is `parallels`:
50
-
51
- ```
52
- $ vagrant init
53
- $ vagrant up --provider=parallels
54
- ...
55
- ```
56
-
57
- You need a Parallels compatible box specified in your `Vagrantfile`
58
- before doing `vagrant up`, please refer to the *Boxes* section for instructions.
59
-
60
- ### Default Provider
61
-
62
- You can use `VAGRANT_DEFAULT_PROVIDER` environment variable to specify the
63
- default provider. Just set it to `parallels` and then it will not be necessary
64
- to add the `--provider` flag to vagrant commands.
65
-
66
- ```
67
- export VAGRANT_DEFAULT_PROVIDER=parallels
68
- ```
69
-
70
- You can also add this command to the `~/.bashrc` file
71
- (or `~/.zshrc` if your shell is Zsh) to make this setting permanent.
72
-
73
- ## Boxes
74
-
75
- Every provider in Vagrant must introduce a custom box format.
76
-
77
- As with every provider, the Parallels provider has a custom box format.
78
- The following base boxes for Parallels provider are available:
79
-
80
- - Ubuntu 12.04 x86_64: `parallels/ubuntu-12.04`
37
+ More information about the Parallels provider is available in
38
+ [Vagrant Parallels Documentation](http://parallels.github.io/vagrant-parallels/docs/)
81
39
 
82
- - Ubuntu 13.10 x86_64: `parallels/ubuntu-13.10`
83
-
84
- - CentOS 6.5 x86_64: `parallels/centos-5.9`
85
-
86
- - CentOS 5.9 x86_64: `parallels/centos-6.5`
87
-
88
- You can add one of these boxes using the next command:
89
-
90
- ```
91
- $ vagrant box add parallels/centos-6.5
92
- ```
40
+ We recommend you to start from these pages:
41
+ * [Usage](http://parallels.github.io/vagrant-parallels/docs/usage.html)
42
+ * [Getting Started](http://parallels.github.io/vagrant-parallels/docs/getting-started.html)
43
+ * [Boxes](http://parallels.github.io/vagrant-parallels/docs/boxes/index.html)
93
44
 
94
- ## Networking
95
- By default, The Parallels provider uses the basic Vagrant networking
96
- approach. Initially, a virtual machine has one adapter assigned to the 'Shared'
97
- network in Parallels Desktop.
98
-
99
- In addition, you can add `:private_network` and `:public_network` adapters.
100
- These features are working the same way as in the basic Vagrant:
101
- - [Private Networks]
102
- (http://docs.vagrantup.com/v2/networking/private_network.html)
103
- - [Public Networks]
104
- (http://docs.vagrantup.com/v2/networking/public_network.html)
105
-
106
- ## Provider Specific Configuration
107
-
108
- Parallels Desktop has the `prlctl` command-line utility that can be used to make
109
- modifications to Parallels virtual machines.
110
-
111
-
112
- The Parallels provider allows to execute the prlctl command with any of
113
- avialable options just prior to starting a virtual machine:
114
-
115
- ```ruby
116
- config.vm.provider "parallels" do |v|
117
- v.customize ["set", :id, "--device-set", "cdrom0", "--image",
118
- "/path/to/disk.iso", "--connect"]
119
- end
120
- ```
121
-
122
- In the example above, the virtual machine is modified to have a specified ISO
123
- image mounted on it's virtual media device (cdrom). The `:id` parameter is
124
- replaced with the actual virtual machine ID.
125
-
126
- Multiple `customize` directives can be used. They will be executed in the
127
- given order.
128
-
129
- The virtual machine memory and CPU settings can be modified easily:
130
-
131
- ```ruby
132
- config.vm.provider "parallels" do |v|
133
- v.memory = 1024
134
- v.cpus = 2
135
- end
136
- ```
137
-
138
- ## Development
45
+ ## Contributing to the Parallels Provider
139
46
 
140
47
  To work on the `vagrant-parallels` plugin development, clone this repository:
141
48
 
@@ -144,61 +51,53 @@ $ git clone https://github.com/Parallels/vagrant-parallels
144
51
  $ cd vagrant-parallels
145
52
  ```
146
53
 
147
- Use [Bundler](http://gembundler.com) to get the dependencies (Ruby 2.0 is needed):
54
+ Use [Bundler](http://bundler.io/) to get the dependencies (Ruby 2.0 is needed)
55
+ and rake to run the unit test suit:
148
56
 
149
57
  ```
150
- $ bundle
58
+ $ bundle install
59
+ $ rake
151
60
  ```
152
61
 
153
- Once you have the dependencies, verify the unit tests pass with `rake`:
62
+ If it passes successfully, you're ready to start developing the plugin. Use
63
+ bundler to execute Vagrant and test the plugin without installing:
154
64
 
155
65
  ```
156
- $ bundle exec rake
66
+ $ bundle exec vagrant up --provider=parallels
157
67
  ```
158
68
 
159
- If they pass, you're ready to start developing the plugin. You can test
160
- the plugin without installing it into your Vagrant environment by simply
161
- creating a `Vagrantfile` in the top level of this directory (it is added
162
- to *.gitignore*) and add the following line to your `Vagrantfile`
69
+ ### Building Provider from Source
70
+ To build a `vagrant-parallels` gem just run this command:
163
71
 
164
- ```ruby
165
- Vagrant.require_plugin "vagrant-parallels"
166
72
  ```
167
-
168
- You need a compatible box file installed. Refer to the *Boxes* section.
169
-
170
- Use bundler to execute Vagrant:
171
-
172
- ```
173
- $ bundle exec vagrant up --provider=parallels
73
+ $ rake build
174
74
  ```
175
75
 
176
- ###Installing Parallels Provider From Source
76
+ The built "gem" package will appear in the `./pkg` folder.
177
77
 
178
- If you want to globally install your locally built plugin from source, use the
179
- following method:
78
+ Then, if you want to install plugin from your locally built "gem", use the
79
+ following commands:
180
80
 
181
81
  ```
182
- $ cd vagrant-parallels
183
- $ bundle install
184
- ...
185
- $ bundle exec rake build
186
- ...
82
+ $ vagrant plugin uninstall vagrant-parallels
187
83
  $ vagrant plugin install pkg/vagrant-parallels-<version>.gem
188
- ...
189
84
  ```
85
+
190
86
  Now that you have your own plugin installed, check it with the command
191
87
  `vagrant plugin list`
192
88
 
193
- ## Contributing
89
+ ### Sending a Pull Request
90
+ If you're ready to send your changes, please follow the next steps:
194
91
 
195
- 1. Fork it.
92
+ 1. Fork the 'vagrant-parallels' repository and ad it as a new remote (`git add
93
+ remote my-fork <fork_url>`)
196
94
  2. Create a branch (`git checkout -b my-new-feature`)
197
95
  3. Commit your changes (`git commit -am "Added a sweet feature"`)
198
- 4. Push to the branch (`git push origin my-new-feature`)
199
- 5. Create a pull request from your `my-new-feature` branch into master
96
+ 4. Push the branch to your fork (`git push fork my-new-feature`)
97
+ 5. Create a pull request from your `my-new-feature` branch into `master` of
98
+ `vagrant-parallels` repo
200
99
 
201
- ## Getting help
100
+ ## Getting Help
202
101
  Having problems while using the provider? Ask your question to our mailing list:
203
102
  [Google Group](https://groups.google.com/group/vagrant-parallels)
204
103
 
@@ -1,5 +1,5 @@
1
1
  module VagrantPlugins
2
2
  module Parallels
3
- VERSION = "1.0.6.rc1"
3
+ VERSION = "1.0.6"
4
4
  end
5
5
  end
metadata CHANGED
@@ -1,7 +1,7 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: vagrant-parallels
3
3
  version: !ruby/object:Gem::Version
4
- version: 1.0.6.rc1
4
+ version: 1.0.6
5
5
  platform: ruby
6
6
  authors:
7
7
  - Mikhail Zholobov
@@ -9,7 +9,7 @@ authors:
9
9
  autorequire:
10
10
  bindir: bin
11
11
  cert_chain: []
12
- date: 2014-03-24 00:00:00.000000000 Z
12
+ date: 2014-03-25 00:00:00.000000000 Z
13
13
  dependencies:
14
14
  - !ruby/object:Gem::Dependency
15
15
  name: bundler