My wife has a website that was built using ruby on rails and is currently hosted on heroku.
We'd like to bring it over to elastic beanstalk on AWS. I've seen that you've done this sort of thing before, which is why I'm reaching out :)
We have the code, full AWS access, and a dump of the production database but do not have access to the Heroku instance itself, as its hosted inside the personal account of her outgoing tech lead.
Now I can get the code up running perfectly locally in dev mode, but I'm hitting some ruby specific issues when I push it in production mode into elastic beanstalk.
a specific example-
if I push a strait deployment some of the assets like fonts and images return 404, such as
http://<hostname>/assetsfonts/[url removed, login to view]
those assets are located in the ./app/assets/stylesheets/fonts/ path in project. I figured out through trial and error that if put them in the ./public/assets/fonts/ path, those assets load. However, I'm not sure exactly why it would work in heroku but break when pushing to AWS. Thats why I'm think it would make more sense to bring in an expert to show me "the right way" to do it.
If this sounds interesting and something you could handle, I'd love to talk with you.
I have quite a bit of DevOps experience but not much in the way of ruby on rails.
Everything I know about ruby I've picked up while hacking on this project.