Why can I test against a route that doesn't exist? AKA I have a GET for an action, but a test against a POST for the same action works in TEST. Obviously, it 404's in production or development.
I'm saying that the higher throughput sites would require you pay for service, and DO would be WAY WAY cheaper.
Plus, you could host all your apps on one instance (may not be good depending on what your apps do, but possible)
Also DO scales much more cheaply than Heroku, and again, you'd only have to change the size of one DO droplet instead of paying for a Dyno for each of your apps that needed more power.
How do you mean? On a DO instance, you could have 20 apps running in parallel answering at different domains.
So, on that point, brandon_j, if you have no experience managing a server, this would be a great time to learn! There are a bunch of guides all over (DigitalOcean has a GREAT collection) for protecting your new server and getting apps running.
Why would my capybara tests be blowing up not being able to find assets? I am serving static files. It's looking here: ""/assets/main/e56ecb6d-da41-4bd9-982d-2d295bec9ab0.woff", which exists.