So, this is all because of the Heroku Bamboo retirement (for which there was a years notice anyway)
Bamboo had pre-installed gems that will be needed to be added to your Gemfile, with explicit versions Current secure (or semi secure anyway) gems will not target ruby 1.8.7 (Heroku actually used the patched REE versions) The fact that this is still running on Rails 2 (which has been out of support since June 2013), together with ruby 1.8.7 which went end of (extended) support in July 2014, means that you will have a hard time getting it to run now on a modern stack. Also, if you are no longer hosting on Heroku, the deployment method will need to change (you cant just git push to the server, and hope it will ok - although there is the dokku project that used heroku buildpacks, but the only supported one there is Ceder) Depending on if it can be classified as open source (in which case you could get some free help), or closed-source (in which case you will probably need to pay consultants under an NDA), you may be able to upgrade to a supported version (which will basically be Rails 4 or higher, as 3.2 will go end of support when Rails 5 is released in a couple of months), depending on the apps complexity, it may actually be worth rewriting it entirely from scratch. If you can host the code somewhere (either Github if it is open-source), or somewhere like Gitlab, or BitBucket if it is closed source (unless you want to pay Github for private repos), and then ask if anyone is prepared to help you fix it. Sorry if this seems negative, but it is probably realistic. On 03/07/15 06:57, OPSPL Goan wrote: > Hassan Schroeder wrote in post #1176058: >> On Thu, Jul 2, 2015 at 8:01 AM, OPSPL Goan <li...@ruby-forum.com> wrote: >> >>>> Yes. Hire someone who knows what they're doing. >>> You wanna try? I can send you the stuff..... Basically need it ported >>> off heroku for a friend that would like to run it all on a cloud server. >> OK, let's back up a second. >> >> Why did this application need to be "ported off heroku" in the first >> place? Because *no one was maintaining it.* >> > Not exactly. Mainly coz they now have their own company server and they > would like all their company apps on that server. Easier to maintain in > one place etc. And Yes, the original developer is *Not available* to > them anymore. So that's also an issue. > >> I wouldn't get this running somewhere else without upgrading it to >> supported versions of Ruby/Rails/etc. > It isn't happening on heroku and frankly I can't really be bothered as > then they're still stuck to that platform. I'd prefer to get it running > stand-alone on a Ubuntu box. So then we can migrate it to their own > server. > >> and having an agreement in >> place for at least handling security updates. >> > All in good time. It's gotta work first. Isn't working on heroku > as-of-now and isn't working anywhere else either :-( It is working code > though Ok. > >> And if your friend doesn't understand the point of this, someone >> needs to educate him or her :-) >> > We work kinda differently here... ;-) We'll get it working, > up-and-running, then discuss what needs to be done for the future... For > now - just trying to get it past first-base to see that it *can run* on > a stand-alone webserver and isn't too tightly bound to the heroku stuff. > See? > > So, again - any help is appreciated. Constructive criticism is too. ;-) > You even been to Goa (India)? I you haven't you must visit - it'll > improve your disposition :-D > > Goan. > -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-talk+unsubscr...@googlegroups.com. To post to this group, send email to rubyonrails-talk@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/55968C79.5000304%40gmail.com. For more options, visit https://groups.google.com/d/optout.
