Permalink
Browse files

changing config to apply db evolutions in prod

  • Loading branch information...
1 parent 1ec1e79 commit 6d6f0c1e092185d125481d28ca97eedf25d9078a @retroryan retroryan committed Jan 31, 2012
Showing with 2 additions and 12 deletions.
  1. +1 −10 README
  2. +1 −0 project/Build.scala
  3. +0 −2 project/plugins.sbt
View
11 README
@@ -1,12 +1,3 @@
This is a re-write of James Ward tutorial - Play Framework, JPA, JSON, jQuery, & Heroku http://www.jamesward.com/2011/12/11/tutorial-play-framework-jpa-json-jquery-heroku
-Using Play 2.0 Beta. It seems JSON support was only recently added to the play framework and so it is not in the play framework jar file. Instead I copied the JSON class out of the play source code. I added the dependencies to the project/Build.scala
-
-
-
-TODO
-
-- Move the Script block into a variable in the index
-- Basic Code Documentation
-- How do you setup a production database configuration?
-- What needs to be done to deploy to Heroku?
+Using Play 2.0 RC1
View
@@ -9,6 +9,7 @@ object ApplicationBuild extends Build {
val postgresql = "postgresql" % "postgresql" % "9.0-801.jdbc3"
+ ebeanEnabled := true
val appDependencies = Seq(
// Add your project dependencies here,
View
@@ -1,7 +1,5 @@
logLevel := Level.Warn
-ebeanEnabled := true
-
resolvers ++= Seq(
DefaultMavenRepository,
Resolver.url("Play", url("https://playframework2.ci.cloudbees.com/job/play2-integrationtest/ws/repository/local/"))(Resolver.ivyStylePatterns),

0 comments on commit 6d6f0c1

Please sign in to comment.