search

ohnosequences / nisperoCLI-legacy

command line interface for nispero
0 stars 0 forks source link

nisperoCLI not in the path #3

Open marina-manrique opened 11 years ago

marina-manrique commented 11 years ago

I've installed nispero and nisperoCLI following these instructions nispero-usage.md#installing but it seems that neither nispero nor nisperoCLI are in the path,

any suggestion @evdokim ?

evdokim commented 11 years ago

Problem is that nisperoCLI is not supposed for running with sudo: after installing nispero it is not accessible from sudo.

Temporary workaround is following: sudo curl https://raw.github.com/n8han/conscript/master/setup.sh | sh; cs ohnosequences/nispero; nispero list

i.e. you should install cs and nispero for every run of nisperoCLI, I'm trying to find better solution now.

evdokim commented 11 years ago

@marina-manrique actually it is not installing: these command will reuse you already installed nispero

this is example for checking: `sudo curl https://raw.github.com/n8han/conscript/master/setup.sh | sh; cs ohnosequences/nispero; nispero check nispero.config -t tasks``

marina-manrique commented 11 years ago

Hey, when I try cs ohnosequences/nispero I get the following message

[ec2-user@ip-10-238-11-180 nispero-test]$ cs ohnosequences/nispero
No conscripts found in this repository
evdokim commented 11 years ago

@marina-manrique it is just bug of conscript, don't worry about it

evdokim commented 11 years ago

summary about nisperoCLI usage

deploy

nispero deploy nispero.config

list

nispero list (if you have access to credentials) nispero list nispro.config (if you have credentials in config)

check

here you need use sudo, if your scripts require root privileges. sudo curl https://raw.github.com/n8han/conscript/master/setup.sh | sh; cs ohnosequences/nispero; nispero check nispero.config -t tasks

undeploy

nispero undeploy <groupid> (if you have access to credentials) nispero undeploy nispero.config.generated (if you have credentials in you config, file nispero.config.generated will be generated in you dir after deployment)

how to fix credentials

I think it is easier to have configured credentials and don't use nispero.config for it. to fix credentials resolving you should change permission for file (/opt/init/aws_credentials??? I forgot which name has your AMI): sudo chmod a+r /opt/init/aws_credentials After it you will never get credentials resolving error.