|
|
|
|
|
by ryanSrich
1517 days ago
|
|
I'm in the same boat. We were in the process of moving off of Heroku a few months back. We had to pause that migration for a number of reasons, but the initial jump was to save some money. Now I'm kicking myself for not pushing the migration to completion. I've basically had to spend the last week recreating much of our deployment pipeline using a very complicated local deployment structure that only I can execute. It's a complete nightmare. My only guess is that the Heroku team is just a handful of overworked developers. For the Github integration to be down this long they must just not care. Like at all. |
|
Never underestimate the value of a "good enough" bash scrip to deploy ALL your project(s).
First (ok top 5) thing i do when starting any new project is quickly writing a "bash deploy script" which usually goes like this:
Sure it's unsexy as hell in today's world of <insert-fav-deploy-tool-here-that-calls-bash-things-underneath-anyway> but it works so nicely !Interesting side story, about 10 years ago I was employed by a "big"(for me at least) price comparison service, and for 5 of the 7 years we use a simple bash script to deploy most of our API's and frontend.
Everyone agreed (it's the wrong way) to do it but no one wanted to dive into the alternatives.
We even found a bug where there were some race issues (some weird service configs) when we deployed that it only worked every 2nd time ? horror
So we just "always deployed twice"... since it's was super fast !