Docker default rails default startup should run rails s.

[chaoticbear]

Current default command in docker-compose is bash -c 'bundle install --no-deployment && rails db:migrate && rails s'

Behavior should be:

1. docker-compose up
2. everything spins up, rails s command sent
3. likely there are failures on first run
4. docker-compose run rails bundle install (if needed)
5. docker-compose run rake db:create (if needed)
6. docker-compose run rake db:migrate (if needed)

[chaoticbear]

@elskwid @phlipper Do you agree with this? I'm trying to figure out the best start up behavior for the container. I think it shouldn't run bundle install every time it starts.

[phlipper]

@joshfleming personally I like a pattern where:

• ENTRYPOINT is bundle exec by default
• CMD is rails server by default (or possibly just rails with compose handling the service bits)
• bundle install is handled during docker build vs. manually
• docker-compose run --rm app rails db:setup is a fine one-time setup, possibly automated via a project bootstrap step (e.g. bin/bootstrap.sh) with other required setup steps

I'm happy to contribute the Dockerfile bits over in renocollective/docker-rails-dev and the compose bits in here as needed.