Evolute 'default' database by default.

[Kicey]

The application doesn't create the 'default' database by default. So, I need add the evolution configuration.
If there is a better way, just tell me.

[mkurz]

The application doesn't create the 'default' database by default.

The Play evolutions module does not create a database for you (also not the Play jdbc module). You have to create the database yourself and then Play can connect to it and if you have evolutions enabled, then Play(-evolutions) will create necessary meta tables and will run the evolutions scripts you set up.

[Kicey]

The application doesn't create the 'default' database by default.

The Play evolutions module does not create a database for you (also not the Play jdbc module). You have to create the database yourself and then Play can connect to it and if you have evolutions enabled, then Play(-evolutions) will create necessary meta tables and will run the evolutions scripts you set up.

I use the new config autoApply to replace the deprecated one(applyEvolutions.default), described as below:

    # Whether evolutions should be automatically applied.  In prod mode, this will only apply ups, in dev mode, it will
    # cause both ups and downs to be automatically applied.
    autoApply = false

(https://github.com/playframework/playframework/blob/18b6720d6a395f6a94b47804a3db5368cada44ef/persistence/play-jdbc-evolutions/src/main/resources/reference.conf#L29-L31)

[mkurz]

@Kicey So I finally run the play-scala-anorm-example locally myself. What is the problem you trying to solve? When starting the application with sbt run and going to http://localhost:9000 in your browser, you will see a screen that asks you to run evolutions:

This is totally expected and how it should work.

Don't you see that page in your browser?

[Kicey]

@Kicey So I finally run the play-scala-anorm-example locally myself. What is the problem you trying to solve? When starting the application with sbt run and going to http://localhost:9000 in your browser, you will see a screen that asks you to run evolutions:

This is totally expected and how it should work.

Don't you see that page in your browser?

Since the behavior is expected (It's too much like an error interface.), I'll close the pr.

[mkurz]

I will enhance the UI here:

• Make clear the evolutions page shows a button playframework#12287