Even though Play Framework 2 is a young framework, we found it to be quite stable for production use. Still, here are some points you may want to consider when working on a serious web project using Play 2.2.
This is a series of blog posts touching different aspects of web development and deployment. Here’s the list of topics:
If you provide some sort of user login on your page, you’ll probably want to use HTTPS/SSL. This is a how-to for using Play with an nginx reverse proxy.
If you’re using a relational database such as MySQL, you’re probably also using Play’s Evolutions Plugin for database migrations. This article shows how to integrate the new Slick 2.0 code generator with the Play Framework so that code for querying your tables is automatically generated.
3.) Logging (coming soon)
By default, there will be only one log file created by Play, this may not be what you want on your production server. How-to coming soon.
4.) Developing with Play: CSS/less compilation (coming soon)
If you have lots of stylesheets, or when using Twitter Bootstrap, the built in less compiler can become annoyingly slow during development. Thankfully there is an easy workaround using the faster lessc compiler. How-to coming soon.