lwndev / vagrant-yeoman-env

A vagrant dev environment for yeoman (http://yeoman.io)
44 stars 10 forks source link

permission or $PATH? #9

Closed tsvetkovpro closed 11 years ago

tsvetkovpro commented 11 years ago

Good afternoon, thank you for your work. Help, the problem is this: I do everything in instructions: $ git clone https://github.com/lwndev/vagrant-yeoman-env.git $ cd vagrant-yeoman-env/vagrant $ vagrant up

then I want to set the generator-angular to me is such a mistake as her win? err

with "sudo npm install -g generator-angular" it is ok , but is set on grunt gives a whole bunch of errors that are missing modules and in recent vsremya generally writes that there is no grunt err2 errors

lwndev commented 11 years ago

For your first issue, are you logged into the VM via ssh?

For your second issue, you may need to run the following commands before grunt will work and the angular generator site will appear properly:

    $ npm install
    $ bower install
lwndev commented 11 years ago

I started up the VM and logged in and I think I see the issue you're having with the angular generator.

Unfortunately, short of updating the base box to not require sudo to access /bin I'm not sure there's much else I can do. My suggestion is to install the generators using 'sudo npm install -g generator-angular'

tsvetkovpro commented 11 years ago

Thank you a lot for your help, but first I logged via ssh protocol tool putty , the second angular here as an example, any generator produces the same example ember. It turns out all the generators need to put as root?

lwndev commented 10 years ago

I believe that you do need to operate as root to install any generator globally. I don't think this is an issue if you use the 'vagrant ssh' command as that "vagrant" user on the VM has sudo permissions.