Capistrano Maintainer throws in the Towel?
Due to burnout, lack of community support, and Rails Asset pipeline compatibility issues (amongst other things): the Capistrano maintainer is seeking help maintaining the project. Lee Hambley has released a “final” version of Capistrano, recommends switching to a containerized deployment method or a PaaS.
Comments
If you read this, thanks for your hard work Mr. Hambley! I used Cap on a non-rails project at my last job and it was quite handy.
Echoing planetmcd’s sentiments, thank you Lee.
Post a comment