December 8, 2014 — Vagrant, Puppet and WP-CLI. This talk is what these technologies do and how you can use them to automate and source control your environment.
October 28, 2014 — In a distributed working environment with employees spanning multiple countries, it’s very important to get everyone using the same tools for stable development and deployment. In this presentation, Brando Dove walks through the vagrant provisioning process, 3rd party services, and home grown tools that are successful with enterprise clients.
September 12, 2014 — Learn how Vagrant, a tool for creating portable development environments, can help you:
– Easily setup a local development environment
– Match your local development environment to production and avoid surprises during deployment.
– Share development environments with team members and get new team members up and running in record time.
– Easily deploy code by using providers and provisioners.
August 21, 2014 — An entertaining and informative demonstration of a typical use case for WordPress development-, deployment-, and provisioning automation. Using technologies such as Vagrant, Ansible, Nginx, Ubuntu, and WP-CLI, there is a better way than using traditional development tools such as MAMP. This presentation is aimed at everyone with an interest in professional development environments for their WordPress projects, including developers, designers, project managers, as well as users.
August 18, 2014 — VagrantやWP-CLIなど、開発環境を劇的にパワーアップさせる
May 14, 2014 — Learn about Vagrant, a local development tool that’s way better than MAMP or WAMP, standardizes environmental variables and will make you a better developer.
December 31, 2013 — This session goes through an overview of Vagrant and the crazy cool stuff that can be done as well as an introduction to a framework that addresses some of the more common server scenarios of 2013.
October 19, 2013 — With Vagrant you can create and distribute virtual development environments that allows you to match your production environments. This eliminates possible hours of unrelated troubleshooting when a configuration on the server shows a different issue that that of your local environment. This also keeps your local machine clear of the server software it shouldn’t care about by providing a clean sandbox to play in.