Use the Avvo base OS images so all the images include avvoenv, allowing easy fetching of environment variables config as the container starts (as apposed to our current practice of setting it on deploy).
The rails-5 image was based on ruby:2.3-alpine rather than alpine, so it's a little bit of a bigger change there, but I think the end result should be the same. I've done that in a separate commit so I can always drop that and just merge the other stuff if that's objectionable.
Use the Avvo base OS images so all the images include avvoenv, allowing easy fetching of environment variables config as the container starts (as apposed to our current practice of setting it on deploy).
The
rails-5image was based onruby:2.3-alpinerather thanalpine, so it's a little bit of a bigger change there, but I think the end result should be the same. I've done that in a separate commit so I can always drop that and just merge the other stuff if that's objectionable.