About archiving the project

[ajgon]

Let's face it - OpsWorks is dead, and containers won. There is no will on Amazon side to support it in any way. It uses ancient versions of almost everything, with no will to update.

I moved on from Chef and AWS almost completely, heck I don't even have AWS account anymore. I also don't do Ruby much these days. Which brings me to the subject - I'm going to archive opsworks_ruby by the end of the year. Forks are of course very welcome, and I do my best to provide support and help with a transition. But personally, I won't maintain or fix any new issue from today (not that, there were many). This project would probably slowly die, same way as Amazon OpsWorks did.

I want to thank all the supporters, and our great, small community for all these years. I learned a lot from you, and had fun developing this project with you together.

If your project/startup relied on this to this very day, first of all - thank you for putting up the trust, but secondly - I strongly suggest you to search for some other solution, or fork this project and patch it on your own.

Thank you, and good luck!

[qdegraeve]

Hi ajgon,
so sad to read this but you are right, it became obvious with the time that AWS had no more interest into working on Opsworks.
Thanks for all what you did, this has been a great help for us at Capsens.
Best regards
Quentin