--
You received this message because you are subscribed to the Google Groups "play-framework" group.
To view this discussion on the web visit https://groups.google.com/d/msg/play-framework/-/kBB5s16DiMAJ.
To post to this group, send email to play-fr...@googlegroups.com.
To unsubscribe from this group, send email to play-framewor...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/play-framework?hl=en.
Maybe I am doing something wrong then? Sorry, this is my first time deploying a play application on heroku, so might be something silly. I didn't make any changes to config files or anything, just used the standard settings and pushed to heroku as in the tutorial.I noticed two things, do I need to do something special?1. If my server is idle for a while, it's brought down and on the next restart, the database is flashed.2. When I do a new push, using git push heroku master, the database refreshes.Any help is appreciated, thanks a lot!!!
On Fri, Jun 1, 2012 at 9:29 AM, James Ward <ja...@jamesward.org> wrote:
The shared database is external and persistent.-James
On Thursday, May 31, 2012 8:46:14 PM UTC-6, Sam Walker wrote:Hi All,I am testing my first play app on heroku as it was nice and easy to setup. I am just using a shared database right now. How do I ensure that the database persists across server restarts/updates?Also, any gotcha on running the app on heroku? Any other feedback/suggestions welcome too.Thanks a ton,Sam
--
You received this message because you are subscribed to the Google Groups "play-framework" group.
To view this discussion on the web visit https://groups.google.com/d/msg/play-framework/-/kBB5s16DiMAJ.
To post to this group, send email to play-framework@googlegroups.com.
To unsubscribe from this group, send email to play-framework+unsubscribe@googlegroups.com.