vlad version 2.2.4 has been released!
Vlad the Deployer is pragmatic application deployment automation,
without mercy. Much like Capistrano, but with 1/10th the
complexity. Vlad integrates seamlessly with Rake, and uses familiar
and standard tools like ssh and rsync.
Impale your application on the heartless spike of the Deployer.
Changes:
2 bug fixes:
On Thu, Dec 22, 2011 at 09:56:13AM +0900, Ryan D. wrote:
vlad version 2.2.4 has been released!
Why is it such a pain in the butt to find source, license information,
and so on?
On Dec 21, 11:06pm, Chad P. [email protected] wrote:
Why is it such a pain in the butt to find source, license information,
and so on?
How hard is that?
Am 22.12.2011 05:06, schrieb Chad P.:
On Thu, Dec 22, 2011 at 09:56:13AM +0900, Ryan D. wrote:
vlad version 2.2.4 has been released!
Why is it such a pain in the butt to find source, license information,
and so on?
Maybe it’s like a pretty girl hiding her beauties, only shown to those
really interested with a long enough breath.
– Matthias
On Wed, Dec 21, 2011 at 10:06 PM, Chad P. [email protected] wrote:
On Thu, Dec 22, 2011 at 09:56:13AM +0900, Ryan D. wrote:
vlad version 2.2.4 has been released!
Why is it such a pain in the butt to find source, license information,
and so on?
Most licenses are in a license file in the root, or in the readme, so I
clicked the docs and there it was http://hitsquad.rubyforge.org/vlad/
On Thu, Dec 22, 2011 at 02:53:29PM +0900, Yossef M. wrote:
On Thu, Dec 22, 2011 at 03:04:59PM +0900, Josh C. wrote:
On Wed, Dec 21, 2011 at 10:06 PM, Chad P. [email protected] wrote:
On Thu, Dec 22, 2011 at 09:56:13AM +0900, Ryan D. wrote:
vlad version 2.2.4 has been released!
Why is it such a pain in the butt to find source, license information,
and so on?
Most licenses are in a license file in the root, or in the readme, so I
clicked the docs and there it was http://hitsquad.rubyforge.org/vlad/
In my experience, RDoc documentation is API documentation, and things
like README files and LICENSE files are delivered with the source, so
checking the RDoc documentation did not seem like an approach that would
be very likely to yield positive results. There it is, though.
On Dec 22, 1:58pm, Chad P. [email protected] wrote:
API documentation, for some reason – and that appears to be the only
place to find it. This definitely seems suboptimal.I guess it’s easy if you know in advance that’s where the link is hidden.
Taking an approach of checking the places one might think are most likely
to offer a link to the source first, and those least likely last or not
at all, it would be a while before one might think to check API
documentation. I it might be worth rethinking this approach to making
sources available.
You don’t have to convince me. Seattle.rb is special, or at least a
couple of its members are.
On the other hand (the “blaming you for laziness” hand), getting
source for any gem is easy. Once you have the source for vlad,
README.txt provides the repo and license.
On Fri, Dec 23, 2011 at 05:51:08AM +0900, Yossef M. wrote:
On the other hand (the “blaming you for laziness” hand), getting
source for any gem is easy. Once you have the source for vlad,
README.txt provides the repo and license.
One should not have to install software to see its license and, in this
age of ubiquitous source hosting and rather evolved open source
development communities, one should not have to install software to see
its source either.
The doco links here are wrong:
http://rubyhitsquad.com/Vlad_the_Deployer.html
For example,
http://hitsquad.rubyforge.org/vlad/files/doco/getting_started_txt.html
should be
http://hitsquad.rubyforge.org/vlad/doco/getting_started_txt.html
This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.
Sponsor our Newsletter | Privacy Policy | Terms of Service | Remote Ruby Jobs