dashy // why

why should i use dashy?

dashy will make your deployment process automatic and reliable. dashy will be of great benefit if your are currently maintaining different configs for different deployments of your application across many servers (different dbs/etc). You may be interested in dashy if:

Your website needs to be configured differently for different servers

dashy allows you to configure different variables per "release". it will then place these in the appropriate files when it comes time to deploy, fully automating the process!

You deploy your website to multiple physical/virtual servers

dashy will perform all the uploading work for you, as fast as is generally possibly, by making use of your underlying source-control system for diffs).

Further, if you want to switch environments, move to a new server, or just deploy a different version, the process is made much faster with dashy! You can simply and quickly configure a new release on the client, or, if switching to a new physical box, just install dashy server on it, and point it at your svn repository!

You enjoy a beautiful and structured environment

Sometimes, in live code bases, you end up with code deployed that is not under source control, (images, pdfs, other such things). Dashy will make sure all these items are under source control, and part of your typical build process, because without that being the case, they will not make it up there in the first place!.

You want to run some post-deploy commands on your deployment

dashy allows you to configure commands on post/pre deploy, so you can perform some additional functionality. This may be synching directories, stop/starting services, sending emails, or updating social networking sites with information about your new release :)