Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

permission or $PATH? #9

Closed
tsvetkovpro opened this issue Nov 10, 2013 · 4 comments
Closed

permission or $PATH? #9

tsvetkovpro opened this issue Nov 10, 2013 · 4 comments

Comments

@tsvetkovpro
Copy link

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
Copy link
Owner

lwndev commented Nov 11, 2013

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
Copy link
Owner

lwndev commented Nov 11, 2013

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
Copy link
Author

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
Copy link
Owner

lwndev commented Dec 19, 2013

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants