Closed davidbasalla closed 8 years ago
Previously running rails s would not start the server locally and instead only display the usage in the terminal. This also meant that running bowl tradetariffapi from the Dev VM 'development' directory would not start the app properly. See http://edgeguides.rubyonrails.org/4_0_release_notes.html#railties-notable-changes
rails s
bowl tradetariffapi
We run rake rails:update:bin to generate these files
rake rails:update:bin
Hi @davidbasalla, the tariff will be extracted out of the dev vm once we move to CF, going to hold off with this as I think we have a similar commit in our CF branch
Previously running
rails s
would not start the server locally and instead only display the usage in the terminal. This also meant that runningbowl tradetariffapi
from the Dev VM 'development' directory would not start the app properly. See http://edgeguides.rubyonrails.org/4_0_release_notes.html#railties-notable-changesWe run
rake rails:update:bin
to generate these files