2 ms·

Capistrano maintainer here, I gave a more comprehensive answer in this thread [1], I hope that answers some of your questions. Specifically to address your poi

Capistrano maintainer here, I gave a more comprehensive answer in this thread [1], I hope that answers some of your questions. Specifically to address your point about having "nothing to do with the tool for the vast majority" there may be some sense to that. We first built a pure, pure literal web front end for Capistrano, it turns out something that limited is not that useful, however when you boil the problem down in to: - Management of secrets, variables, keys, etc - Tasks that can be combined with sets environment specific config and re-used It turns out to be fairly universal. https://xkcd.com/927/ https://xkcd.com/927/ springs to mind, if we'd built another custom web front end for another specific tool it would be nearly useless. As it is we've got customers who have cut their monthly spend on testing/monitoring services from 800$ to $160 and have a better, more consistent experience. It's all relative, frankly my company invested a lot to build this and I personally truly believe it in, and after 18 months intentional slow-burn to make sure it worked well for the people who did use it, it's time to test the water and see if we can bring the product to profitability. If we can't I'm almost certainly going to have to cease working on FOSS due to business and family commitments, given my love for FOSS that's something I'd rather not do! [1]: https://news.ycombinator.com/item?id=11596602 https://news.ycombinator.com/item?id=11596602

tomstuart 10y ago
Your answer doesn’t explain why you made `capistrano-harrow` a dependency of `capistrano`. For example, RSpec 3.4 will use `coderay` for syntax highlighting [1] if it’s available, but doesn’t make `coderay` a dependency of the `rspec` gem. That’s great! People who want syntax highlighting can install the extra gem and get the benefit; people who don’t care about syntax highlighting, or who don’t think it’s worth adding a dependency, can carry on as before. Why didn’t you do the same with `capistrano-harrow`? (I have no investment in the answer, just trying to clarify what others are asking about here.) [1] http://rspec.info/blog/2015/11/rspec-3-4-has-been-released/#install-coderay-for-syntax-highlighting http://rspec.info/blog/2015/11/rspec-3-4-has-been-released/#...
- codebeaker 10y ago
  > For example, RSpec 3.4 will use `coderay` for syntax highlighting [1] if it’s available, but doesn’t make `coderay` a dependency of the `rspec` gem. Absolutely true, two observations: - I've often wondered about syntax highlighting in rspec to make things more readable in tests, I wish I would have known about this and seen it featured more prominently. - RSpec have no vested interest in promoting Coderay. I do have a vested interest in making Harrow come to break-even, if we don't make it break even I may have to step away from the FOSS work that I so enjoy. Thanks for sharing rspec+coderay, that's gonna make life in rspec projects much more bearable!

tomstuart 10y ago

Your answer doesn’t explain why you made `capistrano-harrow` a dependency of `capistrano`. For example, RSpec 3.4 will use `coderay` for syntax highlighting [1] if it’s available, but doesn’t make `coderay` a dependency of the `rspec` gem. That’s great! People who want syntax highlighting can install the extra gem and get the benefit; people who don’t care about syntax highlighting, or who don’t think it’s worth adding a dependency, can carry on as before. Why didn’t you do the same with `capistrano-harrow`? (I have no investment in the answer, just trying to clarify what others are asking about here.) [1] http://rspec.info/blog/2015/11/rspec-3-4-has-been-released/#install-coderay-for-syntax-highlighting http://rspec.info/blog/2015/11/rspec-3-4-has-been-released/#...

codebeaker 10y ago
> For example, RSpec 3.4 will use `coderay` for syntax highlighting [1] if it’s available, but doesn’t make `coderay` a dependency of the `rspec` gem. Absolutely true, two observations: - I've often wondered about syntax highlighting in rspec to make things more readable in tests, I wish I would have known about this and seen it featured more prominently. - RSpec have no vested interest in promoting Coderay. I do have a vested interest in making Harrow come to break-even, if we don't make it break even I may have to step away from the FOSS work that I so enjoy. Thanks for sharing rspec+coderay, that's gonna make life in rspec projects much more bearable!