Our existing dockerfile builds an image suitable for Drone tests and perhaps local development, but it's not great for production workloads. In preparation for adding additional Docker options, this PR removes the presumption that this is the only or primary dockerfile, making room for additional dockerfiles.

For example, I am working on a 'minimal' or 'dependencies only' Dockerfile that contains only system dependencies for building and running the rails application. It will not contain developer tools, a mysql server, or testing dependencies like browser drivers.

Two major things are happening here:

• renaming "docker/dockerfiles" to "docker/drone" to isolate the Dockerfile and entrypoint script that we use for drone.
• renaming the image we push to Docker Hub from codedotorg/code-dot-org to codedotorg/cdo-drone. Chosing this name vs just drone because it's an image of the code-dot-org application, cdo for brevity, prepared specially for executing in drone. Future images might be cdo-minimal and cdo-activejob or cdo-dashboard.

Links

Testing story

Deployment strategy

Follow-up work

After merging this, a new image should be pushed to Docker Hub with the new naming convention. After this is pushed, we can create a new Pull Request that updates the docker compose files and the drone configuration to use the new image. Then we can complete all the 'TODO' items in this PR.

Privacy

Security

Caching

PR Checklist:

• Tests provide adequate coverage
• Privacy and Security impacts have been assessed
• Code is well-commented
• New features are translatable or updates will not break translations
• Relevant documentation has been added or updated
• User impact is well-understood and desirable
• Pull Request is labeled appropriately
• Follow-up work items (including potential tech debt) are tracked and linked