- To have
Dockerfile.devanddocker-compose.dev.ymlfiles that enable Ruby on Rails development completely in Docker. - The developer should be able to run commands such as
bin/rails sandbin/rails c,bin/rspec; ideally, we should have some containers that run inRAILS_ENV=developmentandRAILS_ENV=test. - Some of the database config and other related files were copied from another project, but we need to change this project to use sqlite
- We shouldn't need any config to AWS, for example, but that might change in the future; for now, I don't think we need any references to AWS in the Docker files.
I'm not sure if sqlite needs database user, password, name, port, host, etc, or if we even need a service for it in Docker. I'm relying on the Copilot Agent for guidance on this.
We need the following ENV variables:
- ${RAILS_ENV}
- DOCKER_CONTAINER: true
- Successful build of the image from a Dockerfile.dev
- Successful execution of
docker compose upusing ourdocker-compose.dev.yml - This Rails app is reconfigured to use SQLITE
- A user can
docker exec -it <app_name> /bin/bashto enter:
- A container in
developmentenvironment and executebin/rails s,bin/rails c. - A container in
testenvironment and executebin/rspec