Please get back with me if anyone has ran across a "FULL" and accurate
install guide for commcarehq.
I have seen and tried many different avenues on this but it is still not
behaving.
production install instructions on github are not up to date........
Docker seemed to be the way to go but it does not have cloud care
active........
I just finished getting an ansible/vagrant install up to the
email/inventory updates on the control box and it hung up.
Ubuntu 12.04 repositories are out dated........and the github install is
way past this i believe.
Can someone give me a hand on this..........just some updates on the
deviations from the install docs would help. my company is not going to
spring for a ongoing license cost on the commcarehq.org with as many users
that I currently have running ODK xforms now........
This is a priority for me to get a working pilot box up and
functional.....{incentive$$$} let me know if someone can give me a hand.
Thanks for your help in advance.
I am just looking for the easiest route for a pilot machine......not a
monster hosted network.......lol.
Please get back with me if anyone has ran across a "FULL" and accurate
install guide for commcarehq.
Unfortunately I don't think such a thing exists. The dimagi team uses
our ansible
repo https://github.com/dimagi/commcarehq-ansible to manage our
production environments so that is as-close to a "standard" installation
setup/documentation as we have. That said it definitely is specifically
tied to our own internal way of doing things and we don't currently have
the resources to invest in modifying it or documenting it to be easily used
by other organizations.
If you have specific issues you are running into then we might be able to
help with those.
Cory
···
On Sat, Aug 13, 2016 at 4:23 AM, John Harper <john.harper@grableservices.com wrote:
Please get back with me if anyone has ran across a "FULL" and accurate
install guide for commcarehq.
I have seen and tried many different avenues on this but it is still not
behaving.
production install instructions on github are not up to date........
Docker seemed to be the way to go but it does not have cloud care
active........
I just finished getting an ansible/vagrant install up to the
email/inventory updates on the control box and it hung up.
Ubuntu 12.04 repositories are out dated........and the github install is
way past this i believe.
Can someone give me a hand on this..........just some updates on the
deviations from the install docs would help. my company is not going to
spring for a ongoing license cost on the commcarehq.org with as many
users that I currently have running ODK xforms now........
This is a priority for me to get a working pilot box up and
functional.....{incentive$$$} let me know if someone can give me a hand.
Thanks for your help in advance.
I am just looking for the easiest route for a pilot machine......not a
monster hosted network.......lol.
I am going through the ansible route right now......still not sure what is
giving me the most reason to continue........my pride or my project
dollars......
I have two vagrant VM's stood up , Control and Commcare-ansible. all going
okay in that respect. when I got to the part on redirecting the monolith
inventories I ran into a permission denied error when connecting to the
control VM as below.
I was looking at the host files but not sure what to make of the privot key
pairs.......etc/ansible/hosts or is it on the local folder i should be
looking?
The other thing is the ANSIBLE-DEPLOY-CONTROL command......
su to root user........what user is vagrant using as root?......Thanks for
any help.......
like I said .......its a pride thing now........I will get this to
work....lol.
ansible-deploy-control - deploy changes to users on this control machine
(ansible) vagrant@control:~/commcarehq-ansible/ansible$
(ansible) vagrant@control:~/commcarehq-ansible/ansible$
ansible-deploy-control
You must be root to deploy the control machine
Run su to become the root user, then paste in this command to deploy:
USER=vagrant && ANSIBLE_DIR=/home/$USER/commcarehq-ansible/ansible &&
/home/$USER/.virtualenvs/ansible/bin/ansible-playbook -u root -i
$ANSIBLE_DIR/inventories/localhost $ANSIBLE_DIR/deploy_control.yml -e
@$ANSIBLE_DIR/vars/production/production_vault.yml -e
@$ANSIBLE_DIR/vars/production/production_public.yml --diff --ask-vault-pass
(ansible) vagrant@control:~/commcarehq-ansible/ansible$ su
Password:
···
On Saturday, August 13, 2016 at 8:08:03 AM UTC-7, Cory Zue wrote:
>
> Hi John,
>
> Please get back with me if anyone has ran across a "FULL" and accurate
>> install guide for commcarehq.
>
>
> Unfortunately I don't think such a thing exists. The dimagi team uses our ansible
> repo to manage our
> production environments so that is as-close to a "standard" installation
> setup/documentation as we have. That said it definitely is specifically
> tied to our own internal way of doing things and we don't currently have
> the resources to invest in modifying it or documenting it to be easily used
> by other organizations.
>
> If you have specific issues you are running into then we might be able to
> help with those.
>
> Cory
>
> On Sat, Aug 13, 2016 at 4:23 AM, John Harper <john....@grableservices.com > wrote:
>
>> Please get back with me if anyone has ran across a "FULL" and accurate
>> install guide for commcarehq.
>>
>> I have seen and tried many different avenues on this but it is still not
>> behaving.
>>
>> production install instructions on github are not up to date........
>>
>> Docker seemed to be the way to go but it does not have cloud care
>> active........
>>
>> I just finished getting an ansible/vagrant install up to the
>> email/inventory updates on the control box and it hung up.
>>
>> Ubuntu 12.04 repositories are out dated........and the github install is
>> way past this i believe.
>>
>> Can someone give me a hand on this..........just some updates on the
>> deviations from the install docs would help. my company is not going to
>> spring for a ongoing license cost on the commcarehq.org with as many
>> users that I currently have running ODK xforms now........
>>
>> This is a priority for me to get a working pilot box up and
>> functional.....{incentive$$$} let me know if someone can give me a hand.
>>
>> Thanks for your help in advance.
>>
>>
>>
>> I am just looking for the easiest route for a pilot machine......not a
>> monster hosted network.......lol.
>>
>> --
>>
>> ---
>> You received this message because you are subscribed to the Google Groups
>> "CommCare Developers" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to commcare-developers+unsubscribe@googlegroups.com .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
You don't need to run ansible-deploy-control for the Vagrant setup. We
use that to bootstrap our production control machines with usernames and
user keys.
···
On 15 August 2016 at 23:03, John Harper wrote:
Cory, thanks for the response..........
I am going through the ansible route right now......still not sure what is
giving me the most reason to continue........my pride or my project
dollars......
I have two vagrant VM's stood up , Control and Commcare-ansible. all
going okay in that respect. when I got to the part on redirecting the
monolith inventories I ran into a permission denied error when connecting
to the control VM as below.
I was looking at the host files but not sure what to make of the privot
key pairs.......etc/ansible/hosts or is it on the local folder i should be
looking?
The other thing is the ANSIBLE-DEPLOY-CONTROL command......
su to root user........what user is vagrant using as root?......Thanks for
any help.......
like I said .......its a pride thing now........I will get this to
work....lol.
ansible-deploy-control - deploy changes to users on this control machine
(ansible) vagrant@control:~/commcarehq-ansible/ansible$
(ansible) vagrant@control:~/commcarehq-ansible/ansible$
ansible-deploy-control
You must be root to deploy the control machine
Run su to become the root user, then paste in this command to deploy:
USER=vagrant && ANSIBLE_DIR=/home/$USER/commcarehq-ansible/ansible &&
/home/$USER/.virtualenvs/ansible/bin/ansible-playbook -u root -i
$ANSIBLE_DIR/inventories/localhost $ANSIBLE_DIR/deploy_control.yml -e
@$ANSIBLE_DIR/vars/production/production_vault.yml -e
@$ANSIBLE_DIR/vars/production/production_public.yml --diff
--ask-vault-pass
(ansible) vagrant@control:~/commcarehq-ansible/ansible$ su
Password:
On Saturday, August 13, 2016 at 8:08:03 AM UTC-7, Cory Zue wrote:
Hi John,
Please get back with me if anyone has ran across a "FULL" and accurate
install guide for commcarehq.
Unfortunately I don't think such a thing exists. The dimagi team uses our ansible
repo https://github.com/dimagi/commcarehq-ansible to manage our
production environments so that is as-close to a "standard" installation
setup/documentation as we have. That said it definitely is specifically
tied to our own internal way of doing things and we don't currently have
the resources to invest in modifying it or documenting it to be easily used
by other organizations.
If you have specific issues you are running into then we might be able to
help with those.
Please get back with me if anyone has ran across a "FULL" and accurate
install guide for commcarehq.
I have seen and tried many different avenues on this but it is still not
behaving.
production install instructions on github are not up to date........
Docker seemed to be the way to go but it does not have cloud care
active........
I just finished getting an ansible/vagrant install up to the
email/inventory updates on the control box and it hung up.
Ubuntu 12.04 repositories are out dated........and the github install is
way past this i believe.
Can someone give me a hand on this..........just some updates on the
deviations from the install docs would help. my company is not going to
spring for a ongoing license cost on the commcarehq.org with as many
users that I currently have running ODK xforms now........
This is a priority for me to get a working pilot box up and
functional.....{incentive$$$} let me know if someone can give me a hand.
Thanks for your help in advance.
I am just looking for the easiest route for a pilot machine......not a
monster hosted network.......lol.
dev, production, test and localhost....... should I deploy localhost? or
Dev? which would be easier......would localhost remove the permission
denied error perhaps?
at my onset I will only be having a small group prove the system will be a
good or better than our current SMAP ODK platform we are currently running.
This is for rounds, readings and asset assessments on hospital buildings
and equipment..........not 100% in dimagi's core group of clients per say
but just a different market.
I will let you know if I run into anything else........
···
On Tue, Aug 16, 2016 at 5:58 AM, Simon Kelly wrote:
Hi John
You don't need to run ansible-deploy-control for the Vagrant setup. We
use that to bootstrap our production control machines with usernames and
user keys.
I am going through the ansible route right now......still not sure what
is giving me the most reason to continue........my pride or my project
dollars......
I have two vagrant VM's stood up , Control and Commcare-ansible. all
going okay in that respect. when I got to the part on redirecting the
monolith inventories I ran into a permission denied error when connecting
to the control VM as below.
I was looking at the host files but not sure what to make of the privot
key pairs.......etc/ansible/hosts or is it on the local folder i should be
looking?
The other thing is the ANSIBLE-DEPLOY-CONTROL command......
su to root user........what user is vagrant using as root?......Thanks
for any help.......
like I said .......its a pride thing now........I will get this to
work....lol.
ansible-deploy-control - deploy changes to users on this control machine
(ansible) vagrant@control:~/commcarehq-ansible/ansible$
(ansible) vagrant@control:~/commcarehq-ansible/ansible$
ansible-deploy-control
You must be root to deploy the control machine
Run su to become the root user, then paste in this command to deploy:
USER=vagrant && ANSIBLE_DIR=/home/$USER/commcarehq-ansible/ansible &&
/home/$USER/.virtualenvs/ansible/bin/ansible-playbook -u root -i
$ANSIBLE_DIR/inventories/localhost $ANSIBLE_DIR/deploy_control.yml -e
@$ANSIBLE_DIR/vars/production/production_vault.yml -e
@$ANSIBLE_DIR/vars/production/production_public.yml --diff
--ask-vault-pass
(ansible) vagrant@control:~/commcarehq-ansible/ansible$ su
Password:
On Saturday, August 13, 2016 at 8:08:03 AM UTC-7, Cory Zue wrote:
Hi John,
Please get back with me if anyone has ran across a "FULL" and accurate
install guide for commcarehq.
Unfortunately I don't think such a thing exists. The dimagi team uses
our ansible repo https://github.com/dimagi/commcarehq-ansible to
manage our production environments so that is as-close to a "standard"
installation setup/documentation as we have. That said it definitely is
specifically tied to our own internal way of doing things and we don't
currently have the resources to invest in modifying it or documenting it to
be easily used by other organizations.
If you have specific issues you are running into then we might be able
to help with those.
Please get back with me if anyone has ran across a "FULL" and accurate
install guide for commcarehq.
I have seen and tried many different avenues on this but it is still
not behaving.
production install instructions on github are not up to date........
Docker seemed to be the way to go but it does not have cloud care
active........
I just finished getting an ansible/vagrant install up to the
email/inventory updates on the control box and it hung up.
Ubuntu 12.04 repositories are out dated........and the github install
is way past this i believe.
Can someone give me a hand on this..........just some updates on the
deviations from the install docs would help. my company is not going to
spring for a ongoing license cost on the commcarehq.org with as many
users that I currently have running ODK xforms now........
This is a priority for me to get a working pilot box up and
functional.....{incentive$$$} let me know if someone can give me a hand.
Thanks for your help in advance.
I am just looking for the easiest route for a pilot machine......not a
monster hosted network.......lol.
···
On 16 August 2016 at 17:55, John Harper wrote:
very good.
there are several playbooks available......
dev, production, test and localhost....... should I deploy localhost? or
Dev? which would be easier......would localhost remove the permission
denied error perhaps?
at my onset I will only be having a small group prove the system will be a
good or better than our current SMAP ODK platform we are currently running.
This is for rounds, readings and asset assessments on hospital buildings
and equipment..........not 100% in dimagi's core group of clients per say
but just a different market.
I will let you know if I run into anything else........
On Tue, Aug 16, 2016 at 5:58 AM, Simon Kelly skelly@dimagi.com wrote:
Hi John
You don't need to run ansible-deploy-control for the Vagrant setup. We
use that to bootstrap our production control machines with usernames and
user keys.
I am going through the ansible route right now......still not sure what
is giving me the most reason to continue........my pride or my project
dollars......
I have two vagrant VM's stood up , Control and Commcare-ansible. all
going okay in that respect. when I got to the part on redirecting the
monolith inventories I ran into a permission denied error when connecting
to the control VM as below.
I was looking at the host files but not sure what to make of the privot
key pairs.......etc/ansible/hosts or is it on the local folder i should be
looking?
The other thing is the ANSIBLE-DEPLOY-CONTROL command......
su to root user........what user is vagrant using as root?......Thanks
for any help.......
like I said .......its a pride thing now........I will get this to
work....lol.
ansible-deploy-control - deploy changes to users on this control machine
(ansible) vagrant@control:~/commcarehq-ansible/ansible$
(ansible) vagrant@control:~/commcarehq-ansible/ansible$
ansible-deploy-control
You must be root to deploy the control machine
Run su to become the root user, then paste in this command to deploy:
USER=vagrant && ANSIBLE_DIR=/home/$USER/commcarehq-ansible/ansible &&
/home/$USER/.virtualenvs/ansible/bin/ansible-playbook -u root -i
$ANSIBLE_DIR/inventories/localhost $ANSIBLE_DIR/deploy_control.yml -e
@$ANSIBLE_DIR/vars/production/production_vault.yml -e
@$ANSIBLE_DIR/vars/production/production_public.yml --diff
--ask-vault-pass
(ansible) vagrant@control:~/commcarehq-ansible/ansible$ su
Password:
On Saturday, August 13, 2016 at 8:08:03 AM UTC-7, Cory Zue wrote:
Hi John,
Please get back with me if anyone has ran across a "FULL" and accurate
install guide for commcarehq.
Unfortunately I don't think such a thing exists. The dimagi team uses
our ansible repo https://github.com/dimagi/commcarehq-ansible to
manage our production environments so that is as-close to a "standard"
installation setup/documentation as we have. That said it definitely is
specifically tied to our own internal way of doing things and we don't
currently have the resources to invest in modifying it or documenting it to
be easily used by other organizations.
If you have specific issues you are running into then we might be able
to help with those.
Please get back with me if anyone has ran across a "FULL" and accurate
install guide for commcarehq.
I have seen and tried many different avenues on this but it is still
not behaving.
production install instructions on github are not up to date........
Docker seemed to be the way to go but it does not have cloud care
active........
I just finished getting an ansible/vagrant install up to the
email/inventory updates on the control box and it hung up.
Ubuntu 12.04 repositories are out dated........and the github install
is way past this i believe.
Can someone give me a hand on this..........just some updates on the
deviations from the install docs would help. my company is not going to
spring for a ongoing license cost on the commcarehq.org with as many
users that I currently have running ODK xforms now........
This is a priority for me to get a working pilot box up and
functional.....{incentive$$$} let me know if someone can give me a hand.
Thanks for your help in advance.
I am just looking for the easiest route for a pilot machine......not a
monster hosted network.......lol.
I seem to have something missing on the ansible set up.
fatal: [192.168.33.15] => SSH Error: Permission denied (publickey,password).
while connecting to 192.168.33.15:22
when I run ssh -A control
i get an error.........unable to add key to known-hosts
any ideas?
···
On 08/17/2016 06:00 AM, Simon Kelly wrote:
> If you're doing the vagrant setup you should run the command from
> README.md:
>
> ansible-playbook -i inventories/development -e
> '@vars/dev/dev_private.yml' -e '@vars/dev/dev_public.yml' deploy_stack.yml
>
> On 16 August 2016 at 17:55, John Harper <john.harper@grableservices.com > wrote:
>
> very good.
>
> there are several playbooks available......
>
> dev, production, test and localhost....... should I deploy
> localhost? or Dev? which would be easier......would localhost
> remove the permission denied error perhaps?
>
>
>
> at my onset I will only be having a small group prove the system
> will be a good or better than our current SMAP ODK platform we are
> currently running.
>
> This is for rounds, readings and asset assessments on hospital
> buildings and equipment..........not 100% in dimagi's core group
> of clients per say but just a different market.
>
>
> I will let you know if I run into anything else........
>
>
>
> On Tue, Aug 16, 2016 at 5:58 AM, Simon Kelly <skelly@dimagi.com > wrote:
>
> Hi John
>
> You don't need to run `ansible-deploy-control` for the Vagrant
> setup. We use that to bootstrap our production control
> machines with usernames and user keys.
>
> On 15 August 2016 at 23:03, John Harper <jharper1986@gmail.com > wrote:
>
> Cory, thanks for the response..........
>
> I am going through the ansible route right now......still
> not sure what is giving me the most reason to
> continue........my pride or my project dollars......
>
> I have two vagrant VM's stood up , Control and
> Commcare-ansible. all going okay in that respect. when I
> got to the part on redirecting the monolith inventories I
> ran into a permission denied error when connecting to the
> control VM as below.
>
> $ vagrant ssh control
> ...
> $ ansible-playbook -i inventories/monolith -e
> '@vars/dev/dev_private.yml' -e '@vars/dev/dev_public.yml'
> deploy_stack.yml
>
>
> I was looking at the host files but not sure what to make
> of the privot key pairs.......etc/ansible/hosts or is it
> on the local folder i should be looking?
>
>
> The other thing is the ANSIBLE-DEPLOY-CONTROL command......
>
> su to root user........what user is vagrant using as
> root?......Thanks for any help.......
>
> like I said .......its a pride thing now........I will get
> this to work....lol.
>
>
>
>
> ansible-deploy-control - deploy changes to users on this
> control machine
> (ansible) vagrant@control:~/commcarehq-ansible/ansible$
> (ansible) vagrant@control:~/commcarehq-ansible/ansible$
> ansible-deploy-control
> You must be root to deploy the control machine
> Run `su` to become the root user, then paste in this
> command to deploy:
> USER=vagrant &&
> ANSIBLE_DIR=/home/$USER/commcarehq-ansible/ansible &&
> /home/$USER/.virtualenvs/ansible/bin/ansible-playbook -u
> root -i $ANSIBLE_DIR/inventories/localhost
> $ANSIBLE_DIR/deploy_control.yml -e
> @$ANSIBLE_DIR/vars/production/production_vault.yml -e
> @$ANSIBLE_DIR/vars/production/production_public.yml --diff
> --ask-vault-pass
> (ansible) vagrant@control:~/commcarehq-ansible/ansible$ su
> Password:
>
>
>
>
> On Saturday, August 13, 2016 at 8:08:03 AM UTC-7, Cory Zue wrote:
>
> Hi John,
>
> Please get back with me if anyone has ran across a
> "FULL" and accurate install guide for commcarehq.
>
> Unfortunately I don't think such a thing exists. The
> dimagi team uses our ansible repo
> to
> manage our production environments so that is as-close
> to a "standard" installation setup/documentation as we
> have. That said it definitely is specifically tied to
> our own internal way of doing things and we don't
> currently have the resources to invest in modifying it
> or documenting it to be easily used by other
> organizations.
>
> If you have specific issues you are running into then
> we might be able to help with those.
>
> Cory
>
> On Sat, Aug 13, 2016 at 4:23 AM, John Harper wrote:
>
> Please get back with me if anyone has ran across a
> "FULL" and accurate install guide for commcarehq.
>
> I have seen and tried many different avenues on
> this but it is still not behaving.
>
> production install instructions on github are not
> up to date........
>
> Docker seemed to be the way to go but it does not
> have cloud care active........
>
> I just finished getting an ansible/vagrant install
> up to the email/inventory updates on the control
> box and it hung up.
>
> Ubuntu 12.04 repositories are out dated........and
> the github install is way past this i believe.
>
> Can someone give me a hand on this..........just
> some updates on the deviations from the install
> docs would help. my company is not going to
> spring for a ongoing license cost on the
> commcarehq.org with as
> many users that I currently have running ODK
> xforms now........
>
> This is a priority for me to get a working pilot
> box up and functional.....{incentive$$$} let me
> know if someone can give me a hand.
>
> Thanks for your help in advance.
>
>
>
> I am just looking for the easiest route for a
> pilot machine......not a monster hosted
> network.......lol.
> --
>
> ---
> You received this message because you are
> subscribed to the Google Groups "CommCare
> Developers" group.
> To unsubscribe from this group and stop receiving
> emails from it, send an email to
> commcare-developers+unsubscribe@googlegroups.com.
> For more options, visit
> https://groups.google.com/d/optout
> .
>
>
> --
>
> ---
> You received this message because you are subscribed to
> the Google Groups "CommCare Developers" group.
> To unsubscribe from this group and stop receiving emails
> from it, send an email to
> commcare-developers+unsubscribe@googlegroups.com
> .
> For more options, visit https://groups.google.com/d/optout
> .
>
>
>
>
> --
> Simon Kelly
> Senior Engineer | Dimagi South Africa
> --
>
> ---
> You received this message because you are subscribed to a
> topic in the Google Groups "CommCare Developers" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/commcare-developers/0CaJGB67hyM/unsubscribe
> .
> To unsubscribe from this group and all its topics, send an
> email to commcare-developers+unsubscribe@googlegroups.com
> .
> For more options, visit https://groups.google.com/d/optout
> .
>
>
> --
>
> ---
> You received this message because you are subscribed to the Google
> Groups "CommCare Developers" group.
> To unsubscribe from this group and stop receiving emails from it,
> send an email to commcare-developers+unsubscribe@googlegroups.com
> .
> For more options, visit https://groups.google.com/d/optout
> .
>
>
>
>
> --
> Simon Kelly
> Senior Engineer | Dimagi South Africa
> --
>
> ---
> You received this message because you are subscribed to a topic in the
> Google Groups "CommCare Developers" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/commcare-developers/0CaJGB67hyM/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> commcare-developers+unsubscribe@googlegroups.com
> .
> For more options, visit https://groups.google.com/d/optout.
dev, production, test and localhost....... should I deploy localhost? or
Dev? which would be easier......would localhost remove the permission
denied error perhaps?
at my onset I will only be having a small group prove the system will be
a good or better than our current SMAP ODK platform we are currently
running.
This is for rounds, readings and asset assessments on hospital buildings
and equipment..........not 100% in dimagi's core group of clients per say
but just a different market.
I will let you know if I run into anything else........
On Tue, Aug 16, 2016 at 5:58 AM, Simon Kelly skelly@dimagi.com wrote:
Hi John
You don't need to run ansible-deploy-control for the Vagrant setup.
We use that to bootstrap our production control machines with usernames and
user keys.
I am going through the ansible route right now......still not sure what
is giving me the most reason to continue........my pride or my project
dollars......
I have two vagrant VM's stood up , Control and Commcare-ansible. all
going okay in that respect. when I got to the part on redirecting the
monolith inventories I ran into a permission denied error when connecting
to the control VM as below.
I was looking at the host files but not sure what to make of the privot
key pairs.......etc/ansible/hosts or is it on the local folder i should be
looking?
The other thing is the ANSIBLE-DEPLOY-CONTROL command......
su to root user........what user is vagrant using as root?......Thanks
for any help.......
like I said .......its a pride thing now........I will get this to
work....lol.
ansible-deploy-control - deploy changes to users on this control machine
(ansible) vagrant@control:~/commcarehq-ansible/ansible$
(ansible) vagrant@control:~/commcarehq-ansible/ansible$
ansible-deploy-control
You must be root to deploy the control machine
Run su to become the root user, then paste in this command to deploy:
USER=vagrant && ANSIBLE_DIR=/home/$USER/commcarehq-ansible/ansible &&
/home/$USER/.virtualenvs/ansible/bin/ansible-playbook -u root -i
$ANSIBLE_DIR/inventories/localhost $ANSIBLE_DIR/deploy_control.yml -e
@$ANSIBLE_DIR/vars/production/production_vault.yml -e
@$ANSIBLE_DIR/vars/production/production_public.yml --diff
--ask-vault-pass
(ansible) vagrant@control:~/commcarehq-ansible/ansible$ su
Password:
On Saturday, August 13, 2016 at 8:08:03 AM UTC-7, Cory Zue wrote:
Hi John,
Please get back with me if anyone has ran across a "FULL" and accurate
install guide for commcarehq.
Unfortunately I don't think such a thing exists. The dimagi team uses
our ansible repo https://github.com/dimagi/commcarehq-ansible to
manage our production environments so that is as-close to a "standard"
installation setup/documentation as we have. That said it definitely is
specifically tied to our own internal way of doing things and we don't
currently have the resources to invest in modifying it or documenting it to
be easily used by other organizations.
If you have specific issues you are running into then we might be able
to help with those.
Please get back with me if anyone has ran across a "FULL" and
accurate install guide for commcarehq.
I have seen and tried many different avenues on this but it is still
not behaving.
production install instructions on github are not up to date........
Docker seemed to be the way to go but it does not have cloud care
active........
I just finished getting an ansible/vagrant install up to the
email/inventory updates on the control box and it hung up.
Ubuntu 12.04 repositories are out dated........and the github install
is way past this i believe.
Can someone give me a hand on this..........just some updates on the
deviations from the install docs would help. my company is not going to
spring for a ongoing license cost on the commcarehq.org with as many
users that I currently have running ODK xforms now........
This is a priority for me to get a working pilot box up and
functional.....{incentive$$$} let me know if someone can give me a hand.
Thanks for your help in advance.
I am just looking for the easiest route for a pilot machine......not
a monster hosted network.......lol.
this would not run on the control server.........permission denied to host
I updated my .ssh/config on my linux host (local machine hosting my
virtualbox environment)
host *
ForwardAgent yes
and i got a little farther....
now I get
cannot read file /dev/dev_private.yml
permissions on the host?
···
On Wednesday, August 17, 2016 at 7:32:15 AM UTC-7, Simon Kelly wrote:
>
> if you're trying to SSH from your local machine you should use "vagrant
> ssh control"
>
> On 17 August 2016 at 16:03, John Harper <john....@grableservices.com > wrote:
>
>> That is the one I was trying to set up........
>>
>> I seem to have something missing on the ansible set up.
>>
>> fatal: [192.168.33.15] => SSH Error: Permission denied
>> (publickey,password).
>> while connecting to 192.168.33.15:22
>>
>> when I run ssh -A control
>>
>> i get an error.........unable to add key to known-hosts
>>
>>
>> any ideas?
>>
>>
>> On 08/17/2016 06:00 AM, Simon Kelly wrote:
>>
>> If you're doing the vagrant setup you should run the command from
>> README.md:
>>
>> ansible-playbook -i inventories/development -e '@vars/dev/dev_private.yml' -e '@vars/dev/dev_public.yml' deploy_stack.yml
>>
>>
>> On 16 August 2016 at 17:55, John Harper <john....@grableservices.com > wrote:
>>
>>> very good.
>>>
>>> there are several playbooks available......
>>>
>>> dev, production, test and localhost....... should I deploy localhost?
>>> or Dev? which would be easier......would localhost remove the permission
>>> denied error perhaps?
>>>
>>>
>>>
>>> at my onset I will only be having a small group prove the system will be
>>> a good or better than our current SMAP ODK platform we are currently
>>> running.
>>>
>>> This is for rounds, readings and asset assessments on hospital buildings
>>> and equipment..........not 100% in dimagi's core group of clients per say
>>> but just a different market.
>>>
>>>
>>> I will let you know if I run into anything else........
>>>
>>>
>>>
>>> On Tue, Aug 16, 2016 at 5:58 AM, Simon Kelly <ske...@dimagi.com > wrote:
>>>
>>>> Hi John
>>>>
>>>> You don't need to run `ansible-deploy-control` for the Vagrant setup.
>>>> We use that to bootstrap our production control machines with usernames and
>>>> user keys.
>>>>
>>>> On 15 August 2016 at 23:03, John Harper < jharp...@gmail.com > wrote:
>>>>
>>>>> Cory, thanks for the response..........
>>>>>
>>>>> I am going through the ansible route right now......still not sure
>>>>> what is giving me the most reason to continue........my pride or my project
>>>>> dollars......
>>>>>
>>>>> I have two vagrant VM's stood up , Control and Commcare-ansible. all
>>>>> going okay in that respect. when I got to the part on redirecting the
>>>>> monolith inventories I ran into a permission denied error when connecting
>>>>> to the control VM as below.
>>>>>
>>>>> $ vagrant ssh control
>>>>> ...
>>>>> $ ansible-playbook -i inventories/monolith -e
>>>>> '@vars/dev/dev_private.yml' -e '@vars/dev/dev_public.yml' deploy_stack.yml
>>>>>
>>>>>
>>>>> I was looking at the host files but not sure what to make of the
>>>>> privot key pairs.......etc/ansible/hosts or is it on the local folder i
>>>>> should be looking?
>>>>>
>>>>>
>>>>> The other thing is the ANSIBLE-DEPLOY-CONTROL command......
>>>>>
>>>>> su to root user........what user is vagrant using as root?......Thanks
>>>>> for any help.......
>>>>>
>>>>> like I said .......its a pride thing now........I will get this to
>>>>> work....lol.
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> ansible-deploy-control - deploy changes to users on this control
>>>>> machine
>>>>> (ansible) vagrant@control:~/commcarehq-ansible/ansible$
>>>>> (ansible) vagrant@control:~/commcarehq-ansible/ansible$
>>>>> ansible-deploy-control
>>>>> You must be root to deploy the control machine
>>>>> Run `su` to become the root user, then paste in this command to deploy:
>>>>> USER=vagrant && ANSIBLE_DIR=/home/$USER/commcarehq-ansible/ansible &&
>>>>> /home/$USER/.virtualenvs/ansible/bin/ansible-playbook -u root -i
>>>>> $ANSIBLE_DIR/inventories/localhost $ANSIBLE_DIR/deploy_control.yml -e
>>>>> @$ANSIBLE_DIR/vars/production/production_vault.yml -e
>>>>> @$ANSIBLE_DIR/vars/production/production_public.yml --diff --ask-vault-pass
>>>>> (ansible) vagrant@control:~/commcarehq-ansible/ansible$ su
>>>>> Password:
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> On Saturday, August 13, 2016 at 8:08:03 AM UTC-7, Cory Zue wrote:
>>>>>>
>>>>>> Hi John,
>>>>>>
>>>>>> Please get back with me if anyone has ran across a "FULL" and
>>>>>>> accurate install guide for commcarehq.
>>>>>>
>>>>>>
>>>>>> Unfortunately I don't think such a thing exists. The dimagi team uses
>>>>>> our ansible repo to
>>>>>> manage our production environments so that is as-close to a "standard"
>>>>>> installation setup/documentation as we have. That said it definitely is
>>>>>> specifically tied to our own internal way of doing things and we don't
>>>>>> currently have the resources to invest in modifying it or documenting it to
>>>>>> be easily used by other organizations.
>>>>>>
>>>>>> If you have specific issues you are running into then we might be
>>>>>> able to help with those.
>>>>>>
>>>>>> Cory
>>>>>>
>>>>>> On Sat, Aug 13, 2016 at 4:23 AM, John Harper < john....@grableservices.com> wrote:
>>>>>>
>>>>>>> Please get back with me if anyone has ran across a "FULL" and
>>>>>>> accurate install guide for commcarehq.
>>>>>>>
>>>>>>> I have seen and tried many different avenues on this but it is still
>>>>>>> not behaving.
>>>>>>>
>>>>>>> production install instructions on github are not up to date........
>>>>>>>
>>>>>>> Docker seemed to be the way to go but it does not have cloud care
>>>>>>> active........
>>>>>>>
>>>>>>> I just finished getting an ansible/vagrant install up to the
>>>>>>> email/inventory updates on the control box and it hung up.
>>>>>>>
>>>>>>> Ubuntu 12.04 repositories are out dated........and the github
>>>>>>> install is way past this i believe.
>>>>>>>
>>>>>>> Can someone give me a hand on this..........just some updates on the
>>>>>>> deviations from the install docs would help. my company is not going to
>>>>>>> spring for a ongoing license cost on the commcarehq.org with as
>>>>>>> many users that I currently have running ODK xforms now........
>>>>>>>
>>>>>>> This is a priority for me to get a working pilot box up and
>>>>>>> functional.....{incentive$$$} let me know if someone can give me a hand.
>>>>>>>
>>>>>>> Thanks for your help in advance.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> I am just looking for the easiest route for a pilot machine......not
>>>>>>> a monster hosted network.......lol.
>>>>>>> --
>>>>>>>
>>>>>>> ---
>>>>>>> You received this message because you are subscribed to the Google
>>>>>>> Groups "CommCare Developers" group.
>>>>>>> To unsubscribe from this group and stop receiving emails from it,
>>>>>>> send an email to commcare-developers+unsubscribe@googlegroups.com
>>>>>>> .
>>>>>>> For more options, visit
>>>>>>> https://groups.google.com/d/optout.
>>>>>>>
>>>>>>
>>>>>> --
>>>>>
>>>>> ---
>>>>> You received this message because you are subscribed to the Google
>>>>> Groups "CommCare Developers" group.
>>>>> To unsubscribe from this group and stop receiving emails from it, send
>>>>> an email to commcare-developers+unsubscrib
>>>>> e@googlegroups.com .
>>>>> For more options, visit
>>>>> https://groups.google.com/d/optout.
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Simon Kelly
>>>> Senior Engineer | Dimagi South Africa
>>>> --
>>>>
>>>> ---
>>>> You received this message because you are subscribed to a topic in the
>>>> Google Groups "CommCare Developers" group.
>>>> To unsubscribe from this topic, visit
>>>>
>>>> https://groups.google.com/d/to
>>>> pic/commcare-developers/0CaJGB67hyM/unsubscribe.
>>>> To unsubscribe from this group and all its topics, send an email to
>>>> commcare-developers+unsubscrib e@googlegroups.com
>>>> .
>>>> For more options, visit
>>>> https://groups.google.com/d/optout.
>>>>
>>>
>>> --
>>>
>>> ---
>>> You received this message because you are subscribed to the Google
>>> Groups "CommCare Developers" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to commcare-developers+unsubscribe@googlegroups.com
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>>
>> --
>> Simon Kelly
>> Senior Engineer | Dimagi South Africa
>> --
>>
>> ---
>> You received this message because you are subscribed to a topic in the
>> Google Groups "CommCare Developers" group.
>> To unsubscribe from this topic, visit
>> https://groups.google.com/d/topic/commcare-developers/0CaJGB67hyM/unsubscribe
>> .
>> To unsubscribe from this group and all its topics, send an email to
>> commcare-developers+unsubscribe@googlegroups.com .
>> For more options, visit https://groups.google.com/d/optout.
>>
>>
>> --
>>
>> ---
>> You received this message because you are subscribed to the Google Groups
>> "CommCare Developers" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to commcare-developers+unsubscribe@googlegroups.com .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> --
> Simon Kelly
> Senior Engineer | Dimagi South Africa
>
dev, production, test and localhost....... should I deploy localhost?
or Dev? which would be easier......would localhost remove the permission
denied error perhaps?
at my onset I will only be having a small group prove the system will
be a good or better than our current SMAP ODK platform we are currently
running.
This is for rounds, readings and asset assessments on hospital
buildings and equipment..........not 100% in dimagi's core group of clients
per say but just a different market.
I will let you know if I run into anything else........
On Tue, Aug 16, 2016 at 5:58 AM, Simon Kelly ske...@dimagi.com wrote:
Hi John
You don't need to run ansible-deploy-control for the Vagrant setup.
We use that to bootstrap our production control machines with usernames and
user keys.
I am going through the ansible route right now......still not sure
what is giving me the most reason to continue........my pride or my project
dollars......
I have two vagrant VM's stood up , Control and Commcare-ansible. all
going okay in that respect. when I got to the part on redirecting the
monolith inventories I ran into a permission denied error when connecting
to the control VM as below.
I was looking at the host files but not sure what to make of the
privot key pairs.......etc/ansible/hosts or is it on the local folder i
should be looking?
The other thing is the ANSIBLE-DEPLOY-CONTROL command......
su to root user........what user is vagrant using as
root?......Thanks for any help.......
like I said .......its a pride thing now........I will get this to
work....lol.
ansible-deploy-control - deploy changes to users on this control
machine
(ansible) vagrant@control:~/commcarehq-ansible/ansible$
(ansible) vagrant@control:~/commcarehq-ansible/ansible$
ansible-deploy-control
You must be root to deploy the control machine
Run su to become the root user, then paste in this command to
deploy:
USER=vagrant && ANSIBLE_DIR=/home/$USER/commcarehq-ansible/ansible
&& /home/$USER/.virtualenvs/ansible/bin/ansible-playbook -u root -i
$ANSIBLE_DIR/inventories/localhost $ANSIBLE_DIR/deploy_control.yml
-e @$ANSIBLE_DIR/vars/production/production_vault.yml -e
@$ANSIBLE_DIR/vars/production/production_public.yml --diff
--ask-vault-pass
(ansible) vagrant@control:~/commcarehq-ansible/ansible$ su
Password:
On Saturday, August 13, 2016 at 8:08:03 AM UTC-7, Cory Zue wrote:
Hi John,
Please get back with me if anyone has ran across a "FULL" and
accurate install guide for commcarehq.
Unfortunately I don't think such a thing exists. The dimagi team
uses our ansible repo https://github.com/dimagi/commcarehq-ansible to
manage our production environments so that is as-close to a "standard"
installation setup/documentation as we have. That said it definitely is
specifically tied to our own internal way of doing things and we don't
currently have the resources to invest in modifying it or documenting it to
be easily used by other organizations.
If you have specific issues you are running into then we might be
able to help with those.
Please get back with me if anyone has ran across a "FULL" and
accurate install guide for commcarehq.
I have seen and tried many different avenues on this but it is
still not behaving.
production install instructions on github are not up to date........
Docker seemed to be the way to go but it does not have cloud care
active........
I just finished getting an ansible/vagrant install up to the
email/inventory updates on the control box and it hung up.
Ubuntu 12.04 repositories are out dated........and the github
install is way past this i believe.
Can someone give me a hand on this..........just some updates on
the deviations from the install docs would help. my company is not going
to spring for a ongoing license cost on the commcarehq.org with as
many users that I currently have running ODK xforms now........
This is a priority for me to get a working pilot box up and
functional.....{incentive$$$} let me know if someone can give me a hand.
Thanks for your help in advance.
I am just looking for the easiest route for a pilot
machine......not a monster hosted network.......lol.