#826 ✓wontfix
claes

feature request: increased support for deployment and app packaging

Reported by claes | May 13th, 2011 @ 08:53 AM | in 1.3 (closed)

I have a play app fronted by apache. To simplify deployment it would be nice with framework support for updating a running play app, similar to the auto-deployment of war files in a servlet container.

I haven't thought of all details, but the gist of it is something like this:

  1. A command like "play zip --%" would create a zip file that you could upload to your production server. The zip file would contain only necessary folders (i.e. skipping logs, tmp, test, test-result, eclipse, .svn folders etc), the files would be compiled, and the id would be set to e.g. "prod".
  2. A command like "play auto-deploy myapp.zip" which would unzip the file to some tmp folder, and basically run "play start <unzipped-app-folder>". The "auto-deploy" process would periodically scan for changes to myapp.zip, and run "play stop " followed by "play start ".

This way, to update my running app, all I would have to do is:
1. run "play zip --%prod"
2. upload the zip file to my server

I could probably script the auto-deploy process outside the framework, so I'd say the "play zip" feature for packaging an app is more important.

Comments and changes to this ticket

Please Sign in or create a free account to add a new ticket.

With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.

New-ticket Create new ticket

Create your profile

Help contribute to this project by taking a few moments to create your personal profile. Create your profile »

<h2>Play framework</h2>

Play makes it easier to build Web applications with Java. It is a clean alternative to bloated Enterprise Java stacks. It focuses on developer productivity and targets RESTful architectures. Learn more on the <a href="http://www.playframework.org">http://www.playframework.org</a> website.<br><br>

<h2>Source code is hosted on github</h2>Check out our repository at <a href="http://github.com/playframework/play">http://github.com/playframework/play</a><br><br>

<h2>Contributing, creating a patch</h2> Please read the <a href="http://play.lighthouseapp.com/projects/57987/contributor-guide">contributor guide</a><br><br>

<h2>Reporting Security Vulnerabilities</h2> Since all bug reports are public, please report any security vulnerability directly to <em>guillaume dot bort at gmail dot com</em>.<br><br>

<h2>Creating a bug report</h2> Bug reports are incredibly helpful, so take time to report bugs and request features in our ticket tracker. We’re always grateful for patches to Play’s code. Indeed, bug reports with attached patches will get fixed far quickly than those without any.<br><br>

Please include as much relevant information as possible including the exact framework version you're using and a code snippet that reproduces the problem.<br><br>

Don't have too much expectations. Unless the bug is really a serious "everything is broken" thing, you're creating a ticket to start a discussion. Having a patch (or a branch on Github we can pull from) is better, but then again we'll only pull high quality branches that make sense to be in the core of Play.

People watching this ticket

Referenced by

Pages