Chapter 6. Deploying

So now you’re a budding Enyo developer looking to deploy your app to all the platforms supported by Enyo. 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. We’ll now have to set up a “real” development environment since we’re not likely to deploy our apps by directing users to a jsFiddle page.

For this chapter I’ll assume you’ve followed the Bootplate environment setup guide in Appendix A. You will be able to apply some of these tools to other setups.

Web Targets

One of the simplest ways to deploy Enyo is to host it on a server and serve the apps embedded into a web page. Although all our examples have shown rendering Enyo objects into the document body, it is possible to render them into any element on the page. For web deployment, simply copy the Enyo library and app source code up to a directory on your server and include them into your HTML source.

Bootplate makes this process easy by including a deploy script that packages all the files and minimizes the source. This process speeds up loading and combines everything into a single directory. Once packaged, deploying is as simple as transferring the files to your host. Keep in mind that deployed code is much tougher to debug than debug code.

Desktop Targets

If you want to create an installable Windows app, then Intel’s AppUp encapsulator makes it easy. Visit their site, fill out the fields in the “Make ...

Get Enyo: Up and Running now with the O’Reilly learning platform.

O’Reilly members experience live online training, plus books, videos, and digital content from nearly 200 publishers.