You probably can disable them, but why wouldn't you want to run the migrations on production? How else would you update the db schema?

I do want to be able to run migrations, but I want to make it hard for example to refresh the migrations by accident on the production env and not the development server.

Instead of making it hard, I'd get a proper deployment system set up that then deals with your migrations automatically. Rocketeer and Capistrano come to mind. That way you wouldn't have any reason to run these commands directly on production.

I've created a blank file on the server (outside the project root) and in my migration file I check if this file exists, if it does I skip the migration ;)

shabushabu said:

Instead of making it hard, I'd get a proper deployment system set up that then deals with your migrations automatically. Rocketeer and Capistrano come to mind. That way you wouldn't have any reason to run these commands directly on production.

Thanks! I'll look into rocketeer! Scanned the website and it seems to be what I was looking for.