Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Evidentally, you can't update a force-pushed PR. This is a copy of #1
This also sets up something kinda cool for dev/testing/what-have-you. Should you choose, you can have a data-only container that houses the nginx config. The nginx config actually defines your environment, so what you'd do in that container is have multiple tagged branches of it... one for each environment. That way you could run
And be able to use the container for dev. Anywho, throw it away, use it, whatever.
IMPORTANT NOTE: This uses the DATABASE_URL as an environmental to override what's in database.yml, so don't exclude or forget it.
PR Updated to bring the redis and es containers to initializer configurations. This allows a little bit more flexibility in upgrading/whathaveyou to those containers.