Would be nice to make it easy deployable with capistrano

[jurgis]

Not sure how to achieve that because every user would need to configure it differently.
But maybe there is an elegant way. Any ideas?

[kennethkalmer]

huginn seems to have a basic capistrano setup and documentation in their README - https://github.com/cantino/huginn/#deployment

Would a similar model be helpful?

I also saw they provide additional configuration stubs and directions, for things like ActionMailer... I think this is a great idea.

[jurgis]

For the application configuration I would prefer something as simple as this
http://railscasts.com/episodes/85-yaml-configuration-revised
So that there is only one file which needs to be changed and it is not committed in to the git (just like database.yml)

About capistrano deployment, do not know yet. Would prefer that a user can redeploy without changing anything.
That means that server information and other info need to be placed in some config file or we provide sample config/deploy.rb file which can be renamed once, edited and used.

Besides normally at least 2 deployments are needed for master and slave DNS servers.