Much as I love Trellis sometimes I feel like I’ve missed an announcement. New Trellis install prompted me to update to Ansible 2.4, that’s fine, but now older projects won’t Provision/Deploy. Is there a guide to what exactly needs to be updated to correct this?

We definitely could do a better job at communicating things. Sorry :frowning: Short answer before I head to bed: You can use pip install ansible==2.3.2.0 to switch back to the older version. If you want to avoid switching between Ansible versions you’ll need to upgrade your older projects with @fu…

This was more an oversight than anything else. We (naively) forgot that making someone install Ansible 2.4 would obviously cause problems if you had multiple projects on different versions. Requiring a new version isn’t a big deal in itself, since we check for the version. But somehow this never re…

I wonder if it would be possible / worthwhile / prudent / whatever to run a check for Trellis version, and just install and run the appropriate Ansible version in a virtualenv? Maybe the virtualenv would get activated and deactivated at some clearly defined point - like vagrant up and vagrant halt,…

We can sort of already have that, since Vagrant supports ansible-local now, basically installing Ansible on the virtual machine and running everything from there. The difference would be that if you want to provision or deploy your project you would have to SSH into the box and run your commands the…

I just ran into this myself and wanted to post back to emphasize that Virtualenv really is handy for this sort of thing. The gist of it is: Install Virtualenv- sudo pip install virtualenv Create a directory, anywhere, call it whatever you want. I called mine “virtualenvs”. I made mine in my home d…

Getting Started
Releases
Support us

WP Packages is our new WPackagist replacement that's 17x faster and updates every 5 minutes

Roots Discourse

Updated to Ansible 2.4, deploys broken, now what?

trellis

show post in topic

Home
Categories
Guidelines
Terms of Service
Privacy Policy

Powered by Discourse, best viewed with JavaScript enabled