R
Railway•13mo ago
BrentBarnes

Build/Deploy failed for multiple reasons (Rails & PostgreSQL)

General Service ID: f5211a82-385f-48c4-a826-2f79eef83091 Hi, all! I'm trying to deploy my Ruby-on-Rails application. It uses a PostgreSQL database. It's been a while since I have used Rails/Backend tech and have had to deploy something. A year ago, I had this up and running perfectly on Heroku, then it got detached. Now I'm here to use Railway! I've gotten multiple issues so far, but the one I'm stuck on at the moment is this error from my build logs (Photo attached) Here are my ideas as to what it could be related to: - One of the biggest differences between now and back then is that I stopped using a virtual machine and switched to Windows. It may be related to trying to run/deploy this app on a new machine? I had to download PostgreSQL again, and use a new password, and maybe I don't have the right password? - I also had to download Ruby on my Windows machine. When I first deployed this, it was built on Ruby 3.1.2. The Ruby I just downloaded is 3.2.2. Maybe it has something to do with those not matching? I tried to update that in my codebase, but it might not have been the right fix? Here is the full repo to the project Chipper Social: https://github.com/BrentBarnes/Chipper-Social Thanks for taking the time to read 🙂
GitHub
GitHub - BrentBarnes/Chipper-Social: A Ruby-on-Rails Facebook clone...
A Ruby-on-Rails Facebook clone that has posts, comments, likes, and friendships! - GitHub - BrentBarnes/Chipper-Social: A Ruby-on-Rails Facebook clone that has posts, comments, likes, and friendships!
2 Replies
Percy
Percy•13mo ago
Project ID: f5211a82-385f-48c4-a826-2f79eef83091
Adam
Adam•13mo ago
I’m not too familiar with Ruby, but the version mismatch is almost certainly the issue. Rollback your PC’s version to 3.1.2 and see if it runs. If it doesn’t, google your issue and you’ll certainly find results Always keep your package and language versions in sync. Any differences between them across platforms will be the cause of a host of issues If you’re used to it, testing your code in a vm is the way to go. That way you can customize versions without affecting your main pc some languages have “virtual environments” that accomplish the same thing without a vm. Not sure if Ruby can do that