PostgreSQL and 2 Redis instances (one as a persistent data store, other as a volatile cache).
Here's my algorithm for managing schema upgrades (copied straight from my docs): Every time a change is made to the the development database, the SQL commands are put in a $appname.sql.changes file. A pre-commit hook will detect this and will automatically dump the new schema and add it to the commit. The deploy script will check for the presence of a sql.changes file, and if found, will execute those changes on the production database. It then renames the sql.changes file to sql.changes.ok. The sql.changes.ok file should then be distributed to any production servers, and when found by the deploy script, those changes are executed and the sql.changes.ok file is then deleted. Once the production server is synced, the original sql.changes.ok file should be manually deleted from the origin repo. -- You received this message because you are subscribed to the Google Groups "Mojolicious" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/mojolicious. For more options, visit https://groups.google.com/d/optout.
