Chapter 7. Deploying
So now you’re a budding Enyo developer looking to deploy your app to all the supported platforms. The only question you have is: how? In this chapter we’ll explore the tools and techniques you’ll need to structure your apps and deploy them to various targets. At this point, we’ll need to set up a “real” development environment, since we can’t deploy apps by directing users to a page on jsFiddle.
For this chapter you should follow the Bootplate environment setup guide in Appendix A. Bootplate is a ready-to-use template that includes tools for easy deployment. Even if you ultimately choose a different structure for your app, you may still be able to apply some of these tools.
Bootplate App Structure
It’s worth taking a few moments to discuss how an Enyo Bootplate app is structured. Until now, all of our samples have been run on jsFiddle and have consisted of, at most, three files. We haven’t had to concern ourselves with where the Enyo framework files are coming from or how to add assets. Here’s the Bootplate directory structure:
debug.html index.html assets/ build/ deploy/ enyo/ lib/ source/ tools/
There are some additional files included but these are the most important. debug.html is the file to load during debugging. It includes non-minified versions of Enyo and the libraries. index.html will load a deployed version of the app that has been minified (compressed). If a non-minified build of the application is not available, index.html will redirect to debug.html ...