Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Dec 05 2018 09:17
    dimthe closed #294
  • Dec 05 2018 09:17
    dimthe closed #293
  • Oct 24 2018 08:19
    debo labeled #305
  • Oct 24 2018 08:18
    debo opened #305
  • Oct 24 2018 08:18

    debo on improvements

    Remove deprecated and unsupport… Add UI support for latest PHP v… (compare)

  • Sep 17 2018 10:32
    debo commented #185
  • Sep 17 2018 10:31
    reneweteling commented #185
  • Sep 17 2018 10:03
    debo commented #185
  • Sep 17 2018 06:50
    reneweteling closed #185
  • Sep 17 2018 06:50
    reneweteling commented #185
  • Mar 18 2018 22:19
    InFog commented #299
  • Mar 16 2018 23:46
    debo assigned #292
  • Mar 16 2018 23:44
    debo commented #292
  • Mar 16 2018 22:45
    debo assigned #295
  • Mar 16 2018 22:45
    debo closed #295
  • Mar 16 2018 22:45
    debo commented #295
  • Mar 16 2018 22:44
    debo assigned #299
  • Mar 16 2018 22:44
    debo commented #299
  • Mar 16 2018 22:42
    debo closed #304
  • Mar 16 2018 22:42
    debo assigned #304
Patrick Heneghan
@discopatrick
got it! here's how i did it: ansible-playbook --private-key=../.vagrant/machines/default/virtualbox/private_key -u vagrant backup.yml
Marco "Debo" De Bortoli
@debo
Hi @discopatrick what's the trellis project? And what are you exactly trying to achieve?
Patrick Heneghan
@discopatrick
https://github.com/roots/trellis is another ansible starter project, but focussed on WordPress
all I was trying to do was run the a playbook directly via ansible instead of via vagrant - which i succeeded in doing with the second example above
Marco "Debo" De Bortoli
@debo
Yes I got that, my question was more about why were you trying to run them manually bypassing vagrant automation?
Patrick Heneghan
@discopatrick
ah i see - because they you can add options to the ansible-playbook command, e.g. --ask-vault-pass, --private-key, etc... it may be possible to do that in the Vagrantfile too though!
Marco "Debo" De Bortoli
@debo
The vault pass is automatically asked if you are trying to access a vault resource if I recall correctly, for the private key the path can be specified as well in the playbook
Patrick Heneghan
@discopatrick

I don't get asked, unfortunately, I'm just told "ERROR! Decryption failed"

Hmm, running vagrant up or vagrant provision, I see the message: "No config file found; using defaults" - so it appears to be looking for a config file. I have an ansible.cfg file inside the ansible directory, which contains all my settings like vault password location, inventory, etc. Any idea if I can tell vagrant to use that config file?

ah ha - if I add ansible.ask_vault_pass = true to my Vagrantfile, then I do get asked. However, I would prefer to set the location of my password in ansible.cfg.

In the meantime, I will continue to use ansible-playbook playbook.yml

Marco "Debo" De Bortoli
@debo
@discopatrick yes you can specify the password file via vagrant. Have a look at the bottom of this link https://www.vagrantup.com/docs/provisioning/ansible_common.html
Patrick Heneghan
@discopatrick
Thanks @debo - I had been looking for a page of options like that.
Marco "Debo" De Bortoli
@debo
And now you found it :)
Patrick Heneghan
@discopatrick
hi all, another question for the phansible team. I notice that your ansible starter projects use the default 'vagrant' user during provisioning. I wondered whether you had any opinions or advice on what to do when using the same playbook on a remote staging or production server. it seems odd to have a user called 'vagrant' on these servers, so I was wondering if I should change vagrant's default username to whatever I'll call it on production, e.g. 'admin'? Will Vagrant kick up a fuss if I do this? Or perhaps I'm thinking about this the wrong way, and I should be changing the config value for 'remote_user' depending on whether I'm targeting the local Vagrant box or a remote box?
Ignacio Tolstoy
@naxhh

@discopatrick Are you talking about phansible website provisioning? Or I'm missing something? I'm a bit rusty on some phansible parts.

For phansible website you can check our group_vars:

The default ones are being used in staging and prod
https://github.com/phansible/phansible/blob/0059a03bd69eee676b9fa51e50a5d9075b8d1d52/ansible/group_vars/all#L5

But for dev (vagrant) we use the vagrant user
https://github.com/phansible/phansible/blob/0059a03bd69eee676b9fa51e50a5d9075b8d1d52/ansible/group_vars/devservers#L12

does that helps?
If you check the dates you can see this was done by erika a lot of time ago. We should update the phansible provisioning at some point as it help's as reference for new users :)
Patrick Heneghan
@discopatrick
hi @naxhh - ah, interesting, I don't have group_vars in my project that I generated via the website, so I guess this is a new or upcoming feature?
hmm, no, this was done 2 years ago!
oh wait, I think we've got crossed wires :)
I'm not developing Phansible, I'm an end user. I generated my project via phansible.com
Ignacio Tolstoy
@naxhh
The ansible folder inside the phansible/phansible project is what get's executed when you do a vagrant provision. It's also what we use to deploy to staging/production https://github.com/phansible/phansible/tree/master/ansible
ooh. ok
sorry for that :P
Patrick Heneghan
@discopatrick
no worries! I could have been clearer!
Ignacio Tolstoy
@naxhh
Anyway. That could help you with an example on how we manage the multi-environment setup
Patrick Heneghan
@discopatrick
but yes, I want to do a similar thing to what you're doing, in my own ansible project - so I'll take a look at the source code and see what you do
Ignacio Tolstoy
@naxhh
we try to encourage people learning ansible with a working base. So, feel free to extend the features of your provisioning as you wish :)
anything you need. we will try to help you
Marco "Debo" De Bortoli
@debo
@discopatrick I think that what you are getting wrong is using vagrant to do something remote, in that case you should and I would recommend you to use just ansible playbooks and properly configured inventory files
Patrick Heneghan
@discopatrick
@debo I totally get that vagrant is for local only... But I'm trying to make my playbook work on both a local vagrant box and a remote server. vagrant does some specific things like create a 'vagrant' user, already set up with an ssh key, which is handy... but, I'm considering skipping using the 'vagrant' user entirely, and just creating my own 'admin' user. this should give me more parity between dev and remote servers.
Marco "Debo" De Bortoli
@debo
@discopatrick that's not entirely correct. Vagrant support several providers some of which remote ones. As per the vagrant user vagrant doesn't create any vagrant user but it expects one which is slightly different. You have to add such user and key when you pack the box but vagrant doesn't create it. As per the parity you will obtain the same parity using the right provisioner for your needs
Patrick Heneghan
@discopatrick
interesting, didn't know that about vagrant... but as you recommended, i'm using purely ansible for remote anyway.
Marco "Debo" De Bortoli
@debo
You can read more about providers here https://www.vagrantup.com/docs/providers/ and if you happen to use AWS for example, there is a custom provider for it too, just scroll down the link and go for custom providers
dimthe
@dimthe
hello
anyone here
Marco "Debo" De Bortoli
@debo
Me... kinf of...
dimthe
@dimthe
hi
Marco "Debo" De Bortoli
@debo
@/all we are planning to archive/close this channel due to inactivity, I will give it a couple of weeks lead time and if no activity will happen till then I'll proceed.
mnivoliez
@mnivoliez
Hello
Marco "Debo" De Bortoli
@debo
Hey @mnivoliez how things? How can I help?
mnivoliez
@mnivoliez
@debo Thanks for asking, I have already solve my issue though ^^' sorry for having bother you
Marco "Debo" De Bortoli
@debo
@mnivoliez no problem. What was the issue if you don't mind me asking? If it is something that need fixing it would be nice to have it logged in GitHub
mnivoliez
@mnivoliez
I change the network of my vm to public network and the provisionner could not connect to it. Then I realized that the vm was not in the same network group as my host
Marco "Debo" De Bortoli
@debo
Oh ok... so nothing directly connected to a bug. Whew :)
mnivoliez
@mnivoliez
not at all
mnivoliez
@mnivoliez
The issue was quite misleading though
Marco "Debo" De Bortoli
@debo
In which way?
mnivoliez
@mnivoliez
in the way it was subtile and not easy to discover.
Marco "Debo" De Bortoli
@debo
Oh right, yes, that can be a tricky one. Unfortunately neither Vagrant can really help you debugging, it could warn you, but it doesn't as far as I know. Network configuration is something that "users" needs to be aware of.
mnivoliez
@mnivoliez
Yeah.