Chapter 10. Production Deployment
Deploying a Lift application to production means little more than packaging it and ensuring you set the run mode to production. The recipes in this chapter show how to do this for various hosted services.
You can also install and run a container such as Tomcat or Jetty on your own servers. Containers were introduced in Running your application. This brings with it the need to understand how to install, configure, start, stop, and manage each container, and how to integrate it with load balancers or other frontends. These are large topics, and you can find out more from such sources as:
- The deployment section of the Lift wiki.
- Timothy Perrett, Lift in Action, Chapter 15, “Deployment and Scaling,” Manning Publications, Co.
- Jason Brittain and Ian F. Darwin, Tomcat: The Definitive Guide, O’Reilly Media, Inc.
- Tanuj Khare, Apache Tomcat 7 Essentials, Packt Publishing.
The Lift wiki includes a page on Tomcat configuration options relevant to Lift.
Deploying to CloudBees
Problem
You have an account with the CloudBees PaaS hosting environment, and you want to deploy your Lift application there.
Solution
Use the SBT package command to produce a WAR file that can be deployed
to CloudBees, and then use the CloudBees SDK to configure and deploy your
application.
From within the CloudBees “Grand Central” console, create a new application under your account. In what follows, we’ll assume your account is called myaccount and your application is called myapp.
For the ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access