Instant ColdFusion with Vagrant
1 like454 views
This document discusses using Vagrant and VirtualBox to create a virtual development environment for ColdFusion applications. It outlines installing Vagrant and VirtualBox, creating a Windows virtual machine, provisioning it with ColdFusion and IIS, and accessing the VM from the host computer. The benefits mentioned are having a repeatable, isolated environment that saves time over manual setup and allows teams to work consistently.
Ad
More Related Content
What's hot (19)
Similar to Instant ColdFusion with Vagrant (20)
Ad
More from ColdFusionConference (20)
Ad
Recently uploaded (20)
Instant ColdFusion with Vagrant
- 2. Introduction • Web guy • Coder • Multiple projects/Multiple Teams • Work in teams of 1-5 developers
- 3. Agenda • What is Virtualization • What we are covering • Why Leverage Vagrant and ColdFusion • Installing Virtual Box and Vagrant • VBGuest Plugin • Creating a Workstation VM • Accessing Your VM • ColdFusion Development Against Your new VM
- 4. What is Virtualization • Separate computer inside of a computer. • OS, IP address, users, groups, files, etc • Host and guest, can communicate if proper sharing set up
- 5. What We’re Covering • Windows platform • Found very little discussion/tutorials • Base Set of Tools • VirtualBox • Vagrant • Windows Server • ColdFusion 11 • IIS
- 6. Old Process Setting up Workstation/Server • Document based instructions • Many hours • Often multi team • Human error/troubleshooting • Different platforms on team/elevated environments • Subtle differences even on the same platform • Polluting workstation with different versions of software
- 7. New Way • Build Scripted Vagrant Image (mostly) • Pick your platform • Provisioning/Install All Required Software • Configuration settings • Immediate Benefits • Repeatable and verifiable • Abstracts complexity out of set up • Can work on host in all your normal tools and process
- 8. Installing Vagrant and Virtual Box • Download/Install VirtualBox • Free • VirtualBox providers are bundled with Vagrant • Used as demonstration in documentation • Preferences, Save Location, Windows Images Large • Download/Install Vagrant • Plug Ins • vagrant plugin install vagrant-vbguest • Gather Resources • Download CF installer • IIS modules • .car files
- 9. Creating a New VM • Create new folder - /testVM_Demo • If you use eclipse, probably in workspace • Check out project code to folder –/testVM_Demo/websiteCode • Make the directory name something generic such as /website it makes the scripts much easier to duplicate • Open command prompt in /myProject • Shift + right click • Type vagrant init • Creates .vagrant folder and vagrant file • Create ./scripts and ./resources • Add provisioners • Write/Borrow scripts • Modify vagrant file • Type vagrant up • Watch console
- 10. Accessing Your VM • From Guest • VM Desktop • IIS Modules • ColdFusion Admin – http://localhost:89 • Deploy .car file • Project Code – http://localhost • From Host • Add host entry with the IP from vagrant file and the URL
- 11. ColdFusion Development Against Your new VM • Develop as you do today • Code on local • IDE of choice • Confidence when switching projects
- 12. What We’re Not Covering • Linux, Unix/Solaris, OSX • “ix” platforms are significantly easier to implement and maintain • Many more resources/tutorials out there – See last slide for resources • Concepts are the same • Chef/Puppet • All great tools but out of scope for the discussion • Creating Base boxes
- 13. Why Leverage Vagrant and ColdFusion • How will virtualization help me build robust ColdFusion Applications • Simplifies building out local environments - Saves time and patience • Closely mimic elevated environments – better chance of same behavior • Repeatable, Verifiable – e.g. Spin up new VM for load testing • Box updates, Stored in source control in separate repo • Distributable, Team Environments – Everyone runs on same environment • Create isolation between CF instances – e.g. No mapping collisions • Work on projects running on older versions of CF • Take new versions of CF for a test drive – No longer chore to test code on different versions of CF
- 15. Things to note • Docker • Containers not very friendly for windows users – yet! • Not mutually exclusive from vagrant • Linux, Unix/Solaris, OSX • “ix” platforms are significantly easier to implement and maintain • Many more resources/tutorials out there – See last slide for resources • Concepts are the same • Chef/Puppet • All great tools but out of scope for the discussion • Creating Base boxes
- 16. Vagrant File • Automatically created • Syntax is Ruby • Ruby knowledge is not required • Mostly variable setting • Local network IP Address • Synched Folders • Automatically get c:vagrant on guest • /website • Must use sym link with sharing