I see merits for running both together. Ansible is great at provisioning
servers, where phing cannot truly offer that. Getting code coverage
information, linting a project, and placing only the necessary application
files from a repo onto the vhost are things phing excels at. Phing
seamlessly works with Jenkins for staging / production CI. Ansible works
great with vagrant for server provisioning.
What I am in the process of doing, is taking our phing build xml and adding
tasks to handle development building of the application and creating a
support for kicking off the phing dev build in our vagrant / ansible config.
On Friday, December 20, 2013 10:29:51 AM UTC-5, Rafał Hajduk wrote:
>
> Should I use Phing and Ansible together or use just one of these tools ?
>
> Ansible is great to configure the server, but is it any good for
> deployment ?
>
> What I understand as deployment is:
>
> 1. Upload new version of code (specified git branch) to /{timestamp}/
> 2. Replace current .htaccess with "Deny from all"
> 3. Change symlink /current/ to timestamp
> 4. Perfrom all SQL queries that change anything in databases
> 5. Restore old .htaccess file
> 6. Delete /{older-timestamp}/
>
> It seems that the only way to achieve it in Ansible is to write a bash
> script oneself and tell Ansible to execute it. Am I wrong?
> The most important thing to me is to make the deployment invisible to
> users - I want to avoid situations when somebody requests a file that is
> currently being updated.
>
--
You received this message because you are subscribed to the Google Groups
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/ansible-project/34979a0c-6b20-4973-8d91-d6a1e7cd6717%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
