Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.Sign up
GitHub is where the world builds software
Millions of developers and companies build, ship, and maintain their software on GitHub — the largest and most advanced development platform in the world.
Our company uses rake task to migrate data.
Probably I should not use migration_servers always, but make it configurable?
IMHO, building a generic system for running arbitrary rake tasks from the command line is beyond the scope of core capistrano/rails. The degree of configurability required in the long run is likely to be an issue (around picking servers, etc). The Capistrano configuration syntax is essentially already designed to do this, and if you really need arbitrary rake tasks to be run, you can add the code block in the PR.
This might be another good candidate for my "Cookbook" doc page idea… #199 (comment)
I'm entirely open to different opinions from the other Cap maintainers.
I to some degree agree, in our case, we have moved the code to populate new fields into rake task. These are some tasks that will only be run once. I would just add a file for our case and would probably good enough for us. I just thought that this was a common case.
Thanks for the comment