You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
*`hostname_append_id` Appends guest ID to its' hostname. Note that this effectively sets the hostname to ID, if it was empty beforehand.
149
147
*`full_clone` Creates full clone, instead of a linked one.
148
+
*`lxc_ssh_public_keys` public keys to be added to the authorized keys file of the machine, one key per line.
150
149
151
150
## Debug RestClient Communication with Proxmox-Node
152
151
@@ -158,7 +157,7 @@ $ RESTCLIENT_LOG=stdout vagrant up --provider proxmox
158
157
159
158
### Tips
160
159
161
-
* ensure your LXC-template is accessible from every proxmox node
160
+
* ensure your LXC-template is accessable from every proxmox node
162
161
* debug with `selected_node`-option enabled
163
162
164
163
## Build the plugin
@@ -171,11 +170,18 @@ $ rake build
171
170
172
171
For non-ruby folks. Needs `ruby` and `zlib` development headers (on Debian: `apt-get install ruby-dev zlib1g-dev`).
173
172
173
+
Use e.g. rvm to manage ruby versions. Do `rvm install "ruby-2.5.7"` to install the appropiate ruby version. Run `rvm use` then and check with `ruby --version` if it was properly activated. (If ruby complains about not using a login shell run `source ~/.rvm/scripts/rvm`)
174
+
175
+
You may then install dependencies and build with:
174
176
```bash
175
-
$ export GEM_HOME=~/.gem
176
177
$ gem install bundler rake
177
-
$ ~/.gem/bin/bundle
178
+
$ bundle install
178
179
$ rake build
180
+
```
181
+
182
+
You can install the vagrant plugin then with `vagrant plugin install ./vagrant-proxmox-0.2.2.gem` (you might run into problems if you run it on a shell where you ran `rvm use` previously).
183
+
184
+
Optionally run the rspec tests with `rake spec`. (Make sure, that vagrant is installed in the ruby env you are using.)
0 commit comments