ashfurrow
commented
5 years ago This fell behind the radar a bit because a) I got busy, and b) Peril Staging got a bit Sherlocked by GitHub Actions. As development on Peril Staging slows, I think it might make sense to keep using the Heroku server for Moya Peril. Hosted Peril introduces a lot of complexity and while taking on that complexity was worth it to help the Peril project grow, but the tradeoff might not be worth it anymore (especially with Orta and I outside of the day-to-day of Moya, unable to spot issues that need Peril Staging fixes).
I'm closing this issue but I'm happy to clarify any of these points.
Peril Staging is a soon-to-be-launched, in-closed-beta project of @orta. It's like a hosted version of Peril with shared infrastructure, removing the need to setup a Heroku project. Moya and Danger/Peril are distinct OSS projects, but there's a lot of overlap in contributors, so the two projects have a history of trying out cool new things and providing a place to test cutting-edge feature of Danger/Peril. We began with Dangerfiles ran on CI, added Peril, and now it's time to try Peril Staging. We'll be at the cutting edge of Peril development, so we may run into issues, but I think the benefit to Peril would be worth the risk of issues with Moya's Peril installation. I'm happy to answer any questions. /cc @Moya/core-team
So here's what I'm thinking for next steps:
To help document this for people migrating from Heroku to Peril Staging in the future, I'm going to keep notes on the process here. This means that if anyone has questions about the process, I encourage them to ask below because they'll be helpful for others, too.
@SD10 I think you're the owner of the Heroku project, can you add me to it? Email is
ash@ashfurrow.com.