capistrano online with Winfy

We have hosted the application capistrano in order to run this application in our online workstations with Wine or directly.

Quick description about capistrano:

A remote server automation and deployment tool written in Ruby. Capistrano extends the Rake DSL with methods specific to running commands on() servers. Capistrano is written in Ruby, but it can easily be used to deploy any language. If your language or framework has special deployment requirements, Capistrano can easily be extended to support them. Capistrano is bundled as a Ruby Gem. It requires Ruby 2.0 or newer. Capistrano can be installed as a standalone Gem, or bundled into your application. It is recommended to fix the version number when using Capistrano, and is therefore recommended to use an appropriate bundler. The capistrano-rails gem includes extras specifically designed for Ruby on Rails, specifically Asset Pipeline Support and Database Migration Support. Capistrano deploys using SSH. Thus, you must be able to SSH (ideally with keys and ssh-agent) from the deployment system to the destination system for Capistrano to work.

Features:

• Capistrano uses a strictly defined directory hierarchy on each remote server to organise the source code and other deployment-related data
• "current" is a symlink pointing to the latest release. This symlink is updated at the end of a successful deployment. If the deployment fails in any step the current symlink still points to the old release
• "releases" holds all deployments in a timestamped folder. These folders are the target of the current symlink.
• "repo" holds the version control system configured. In case of a git repository the content will be a raw git repository (e.g. objects, refs, etc.)
• "revisions.log" is used to log every deploy or rollback. Each entry is timestamped and the executing user (: local_user, defaulting to the local username) is listed. Depending on your VCS data like branch names or revision numbers are listed as well
• "shared" contains the linked_files and linked_dirs which are symlinked into each release. This data persists across deployments and releases. It should be used for things like database configuration files and static and persistent user storage handed over from one release to the next

Programming Language: Ruby.
Categories: