c3431b0474
## Description This PR has two goals. First of all it continues work that has been done in #21559. Besides this, and this is more significant, I tried to improve the structure of the documentation that is currently used for different language-specific guides like [PHP](https://docs.docker.com/guides/php/configure-ci-cd/), [Go](https://docs.docker.com/guides/golang/), [Python](https://docs.docker.com/guides/python/) and others, including, of course, Ruby itself. Each of these guides currently has a [Configure CI/CD](https://docs.docker.com/guides/python/configure-ci-cd/) section. Inside this section there is a GitHub Actions workflow example that has nothing in common with a CI/CD pipeline. It's just an example of how to build and push an image to a Docker Hub registry. We should be clear in our documentation and not mislead our users. This was the main reason why I renamed this section to "Automate your builds with GitHub Actions". I also updated the content of this section to reflect the new name and to make it more clear what the user can expect from this guide. I suggest the same be done for all other language-specific guides. Besides this, I changed the order of the sections in the Ruby guide. The "Develop your app" section has been moved down to the bottom of the guide. This makes more sense to me because of two reasons: 1. It is more important to start using Docker Hub right after you added the Dockerfile to your project (section number one in all language-specific guides). 2. I can hardly imagine anybody using Docker to run the app locally for development purposes (at least for Ruby). What is really essential and useful is to know how to run services, that are required by your app, like a database, a cache server, or a local LLM. This is why the "Develop your app" section should be rewritten to explain how to run the infrastructure services that are required by the app and not the app itself. Below there are screenshots reflecting the changes that have been made in this PR. **Before** <img width="1512" alt="Screenshot 2025-02-27 at 11 26 39" src="https://github.com/user-attachments/assets/1ca06aea-ffeb-4efb-a14d-27254d2a2110" /> **After** <img width="1512" alt="Screenshot 2025-02-27 at 11 26 01" src="https://github.com/user-attachments/assets/7abbe8b7-d1b3-480f-8105-49f967b51e47" /> ## Related issues or tickets #21559 ## Reviews - [x] Technical review - [x] Editorial review - [ ] Product review |
||
|---|---|---|
| .github | ||
| _vale | ||
| _vendor | ||
| archetypes | ||
| assets | ||
| content | ||
| data | ||
| hack | ||
| i18n | ||
| layouts | ||
| static | ||
| .dockerignore | ||
| .gitattributes | ||
| .gitignore | ||
| .htmltest.yml | ||
| .markdownlint.json | ||
| .prettierrc | ||
| .vale.ini | ||
| CONTRIBUTING.md | ||
| Dockerfile | ||
| LICENSE | ||
| Makefile | ||
| README.md | ||
| compose.yaml | ||
| docker-bake.hcl | ||
| go.mod | ||
| go.sum | ||
| hugo.yaml | ||
| hugo_stats.json | ||
| netlify.toml | ||
| package-lock.json | ||
| package.json | ||
| pagefind.yml | ||
| postcss.config.js | ||
| tailwind.config.js | ||
README.md
Docs @ Docker
Welcome to the Docker Documentation repository. This is the source for https://docs.docker.com/.
Feel free to send us pull requests and file issues. Our docs are completely open source, and we deeply appreciate contributions from the Docker community!
Provide feedback
We’d love to hear your feedback. Please file documentation issues only in the Docs GitHub repository. You can file a new issue to suggest improvements or if you see any errors in the existing documentation.
Before submitting a new issue, check whether the issue has already been reported. You can join the discussion using an emoji, or by adding a comment to an existing issue. If possible, we recommend that you suggest a fix to the issue by creating a pull request.
You can ask general questions and get community support through the Docker Community Slack. Personalized support is available through the Docker Pro, Team, and Business subscriptions. See Docker Pricing for details.
If you have an idea for a new feature or behavior change in a specific aspect of Docker or have found a product bug, file that issue in the project's code repository.
We've made it easy for you to file new issues.
-
Click New issue on the docs repository and fill in the details, or
-
Click Request docs changes in the right column of every page on docs.docker.com and add the details, or
-
Click the Give feedback link on the side of every page in the docs.
Contribute to Docker docs
We value your contribution. We want to make it as easy as possible to submit
your contributions to the Docker docs repository. Changes to the docs are
handled through pull requests against the main branch. To learn how to
contribute, see CONTRIBUTING.md.
Copyright and license
Copyright 2013-2025 Docker, Inc., released under the Apache 2.0 license .