Installing protobox via gem

gem install protobox && protobox init

got this error: bash: protobox: command not found

-> actually not possible to install any box...

Hello,

I am trying to install protobox on Ubuntu 12.0.4 with no luck for some time. Can you please advise, i am following instructions as per the installation docs.

root@ubuntu:/usr/local/bin# vagrant -v Vagrant version 1.0.1

root@ubuntu:/usr/local/bin# gem install protobox && protobox init Successfully installed protobox-0.0.2 1 gem installed Installing ri documentation for protobox-0.0.2... Installing RDoc documentation for protobox-0.0.2... /var/lib/gems/1.8/gems/protobox-0.0.2/lib/protobox/commands.rb:37:in init': undefined methodrequire_relative' for Protobox::Commands:Module (NoMethodError) from /var/lib/gems/1.8/gems/protobox-0.0.2/lib/protobox/commands.rb:21:in send' from /var/lib/gems/1.8/gems/protobox-0.0.2/lib/protobox/commands.rb:21:inrun' from /var/lib/gems/1.8/gems/protobox-0.0.2/lib/protobox/cli.rb:16:in execute' from /var/lib/gems/1.8/gems/protobox-0.0.2/lib/protobox/cli.rb:12:inexecute' from /var/lib/gems/1.8/gems/protobox-0.0.2/bin/protobox:6 from /usr/local/bin/protobox:19:in `load' from /usr/local/bin/protobox:19

Please let me know how to proceed and i have the custom.yml and let me know which location i need to place on Ubuntu file system as well.

@patrickheeney Its been a while since I have spun up a new VM with protobox and I am unable to get nginx to work.

There have been loads of changes in the last month though (good work) so I may not be up to date with exactly the best workflow here now!

The simplest way to reproduce this is just to use the stock common.yml and just change nginx install=1 and apache `install=0``.

It gets most of the way through the install and then trips up with the following.

TASK: [php | ini | set nginx ini] ********************************************* 
failed: [localhost] => {"failed": true, "item": ""}
msg: Destination directory /etc/php5/fpm does not exist

FATAL: all hosts have already failed -- aborting

Here is the full output for reference https://gist.github.com/BenBish/8261564

First off, I love this concept. You saw the drawbacks with the already excellent puphpet and developed exactly what I wanted to be able to do with it. As a front end designer / dev, the common.yaml solution is the key to being the base for all my dev projects!

If I understand correctly, I should be able to set the Apache section to install: 0 and set the Nginx section to install: 1 to use nginx as the web server?

Unfortunately, its falling over when I try this though.

From the end of the output,

Finished running initial librarian-puppet
[default] Running provisioner: puppet...
Running Puppet with default.pp...
stdin: is not a tty
Warning: Could not retrieve fact fqdn
Error: Could not find class nginx::params for protobox on node protobox
Error: Could not find class nginx::params for protobox on node protobox
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

FACTER_ssh_username='vagrant' puppet apply --hiera_config /vagrant/puppet/hiera/hiera.yaml --parser future --modulepath /vagrant/puppet/modules:/etc/puppet/modules:/usr/share/puppet/modules --manifestdir /tmp/vagrant-puppet/manifests --detailed-exitcodes /tmp/vagrant-puppet/manifests/default.pp || [ $? -eq 2 ]

Stdout from the command:



Stderr from the command:

stdin: is not a tty
Warning: Could not retrieve fact fqdn
Error: Could not find class nginx::params for protobox on node protobox
Error: Could not find class nginx::params for protobox on node protobox

I've elected to install Xdebug, accepting the default configuration, but always see the following error:

TASK: [php | xdebug | set ini] ************************************************  
failed: [localhost] => {"failed": true, "item": ""}
msg: Destination directory /etc/php5/mods-available does not exist

FATAL: all hosts have already failed -- aborting

PLAY RECAP ******************************************************************** 
         to retry, use: --limit @/root/site.retry`

The operating system chosen is Ubuntu 10.04 Lucid x64.

in ansible/roles/php/tasks/xdebug.yml

- name: xdebug | enable xdebug config
  shell: >
    chdir=/etc/php5/mods-available
    php5enmod xdebug-options;
  sudo: yes
  when: not php_version_53
  notify:
    - php-restart

- name: xdebug | enable xdebug config on php 5.3
  file: >
    src=/etc/php5/mods-available/xdebug-options.ini
    dest=/etc/php5/conf.d/xdebug-options.ini
    state=link
  when: php_version_53
  notify:
    - php-restart

however during provisioning I get:

TASK: [php | xdebug | enable xdebug config] *********************************** 
skipping: [localhost]

TASK: [php | xdebug | enable xdebug config on php 5.3] ************************ 
skipping: [localhost]

and the file isn't linked in /etc/php5/conf.d/

Not sure how to go about debugging but happy to try if you point me in the right direction.

Mailcatcher no longer installs when provisioning citing ruby version requirements.

Below are my logs from the provisioning:

==> default: TASK: [php | mailcatcher | install packages] ********************************** ==> default: changed: [localhost] => (item=rdoc) ==> default: failed: [localhost] => (item=mailcatcher) => {"changed": true, "cmd": ["gem", "install", "mailcatcher", "--no-ri", "--no-rdoc"], "delta": "0:00:53.185896", "end": "2014-06-17 19:56:14.698558", "item": "mailcatcher", "rc": 1, "start": "2014-06-17 19:55:21.512662"} ==> default: stderr: ERROR: Error installing mailcatcher: ==> default: mime-types requires Ruby version >= 1.9.2. ==> default: stdout: Building native extensions. This could take a while... ==> default: ==> default: HEADS UP! Haml 4.0 has many improvements, but also has changes that may break ==> default: your application: ==> default: ==> default: * Support for Ruby 1.8.6 dropped ==> default: * Support for Rails 2 dropped ==> default: * Sass filter now always outputs