# Capistrano, beta deployment and different database?

**URL:** <https://www.ruby-forum.com/t/capistrano-beta-deployment-and-different-database/91586>\
**Category:** Rails\
**Created:** [April 10, 2007, 6:56pm UTC](https://www.ruby-forum.com/t/capistrano-beta-deployment-and-different-database/91586 "2007-04-10T18:56:40Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![elliterate](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/e/9de053/32.png) [@elliterate](https://www.ruby-forum.com/u/elliterate)\
**Post date:** [April 10, 2007, 6:56pm UTC](https://www.ruby-forum.com/t/capistrano-beta-deployment-and-different-database/91586/1 "2007-04-10T18:56:40Z")

</div>

Hi,

I’ve modified my deploy.rb to deploy a beta version of my site (trunk,  
rather than a tag) if I supply the BETA environment variable. It uses a  
different mongrel config and a different deploy\_to. I’d also like to use  
a  
seperate MySQL database, yet as far as I know, we’re stuck with the  
test,  
development and production databases. I don’t want development mode  
(don’t  
want the reloads) so something like appname\_beta\_production would be  
good.  
Any idea how I can stay in production mode but override the database?

Cheers  
Ian