<!--Delete sections as needed -->
## Description
As per https://docker.atlassian.net/browse/ENGDOCS-2836
Next up:
- tidy up/ split the security FAQs
- move the 'for developers' content up one level
- beef up the Deploy DD page
- AOB
(didn't want to include in this PR as it's already too long)
## Reviews
<!-- Notes for reviewers here -->
<!-- List applicable reviews (optionally @tag reviewers) -->
- [ ] Technical review
- [ ] Editorial review
- [ ] Product review
## Description
* I updated the code in the main Python guide. I noticed some
deprecations in the libraries. I made a refactor and updated the whole
code to be totally up to date with the recent library version
* I added a section about linting, formatting, and type checking to
follow the best practices. I include them in the CI/CD too
@craig-osterhout
@usha-mandya
- [ ] Technical review
- [ ] Editorial review
- [ ] Product review
This PR introduces a new CI pipeline using Azure Pipelines to automate
the process of building and pushing Docker images to Docker Hub.
---------
Co-authored-by: Julien Maitrehenry <julien.maitrehenry@me.com>
## Description
Replaced "Configure CI/CD" step of the Python guide with "Configure
GitHub Actions" step to have it similar structure as the Rails guide.
## Related issues or tickets
#22114
## Reviews
- [ ] Technical review
- [x] Editorial review
- [ ] Product review
<!--Delete sections as needed -->
## Description
Introduces small update of the Laravel framework guide (bump versions to
the latest Laravel 12 and php 8.4 + updates the related examples repo -
the fork needs to be synced).
## Related issues or tickets
#21268
## Reviews
<!-- Notes for reviewers here -->
As was discussed on the last docs meeting, to simplify the process the
review will be sent to the one of Docker Captains first.
@igor-alexandrov @ajeetraina
- [ ] Technical review
- [ ] Editorial review
- [ ] Product review
This PR introduces a comprehensive, language-specific guide for
containerizing Angular applications using Docker, aimed at helping
developers streamline development, testing, and deployment workflows. It
includes practical steps and examples to set up CI/CD pipelines using
GitHub Actions, aligning with modern DevOps best practices.
**What’s Included**
- Step-by-step instructions to containerize Angular apps using Docker
- Configuration for a local development environment inside containers
- Guidance on running unit tests (Karma/Jasmine) inside Docker
containers
- Full CI/CD pipeline setup using GitHub Actions for automated builds
and deployments
- Deployment instructions for a local Kubernetes cluster to validate
production readiness
**Credits**
[Kristiyan
Velkov](https://www.linkedin.com/in/kristiyan-velkov-763130b3/), Docker
Captain and experienced Front-end Engineer
- replace some examples using EOL alpine versions
- replace some examples using EOL ubuntu versions
<!--Delete sections as needed -->
## Description
<!-- Tell us what you did and why -->
## Related issues or tickets
<!-- Related issues, pull requests, or Jira tickets -->
## Reviews
<!-- Notes for reviewers here -->
<!-- List applicable reviews (optionally @tag reviewers) -->
- [ ] Technical review
- [ ] Editorial review
- [ ] Product review
Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
<!--Delete sections as needed -->
## Description
The app service port is `8000`, and I mistakenly mentioned `8080` for
health check while creating this guide. So, it will give an error.
- [ ] Technical review
- [x] Editorial review
- [ ] Product review
## Description
This PR introduces a comprehensive, language-specific guide for
containerizing React.js applications using Docker, aimed at helping
developers streamline development, testing, and deployment workflows. It
includes practical steps and examples to set up CI/CD pipelines using
GitHub Actions, aligning with modern DevOps best practices.
**What’s Included**
- Step-by-step instructions to containerize React.js apps using Docker.
- Configuration for a local development environment inside containers.
- Guidance on running unit tests inside Docker containers.
- Full CI/CD pipeline setup using GitHub Actions for automated builds
and deployments.
- Deployment instructions for a local Kubernetes cluster to validate
production readiness.
**Credits**
[Krisityan
Velkov](https://www.linkedin.com/in/kristiyan-velkov-763130b3/), Docker
Captain and experienced Front-end Engineer.
---------
Co-authored-by: kristiyan.velkov <kristiyan.velkov@ffw.com>
Co-authored-by: Craig Osterhout <103533812+craig-osterhout@users.noreply.github.com>
## Description
- Fixed minor typos like `msyql`, `model`, `.json|`.
- Although `docker remove` works due to CLI fallback, it's not an
official command. Replaced with `docker rm` for correctness and clarity.
- Replaced `docker-compose.yml` with `compose.yaml` to align with the
[Compose
specification.](https://github.com/compose-spec/compose-spec/blob/main/03-compose-file.md)
<!--Delete sections as needed -->
## Description
In this guide I want to show how to run and configure Dex as container,
to mock an OAuth service, which can be really useful in
development/testing.
## Related issues or tickets
<!-- Related issues, pull requests, or Jira tickets -->
## Reviews
<!-- Notes for reviewers here -->
<!-- List applicable reviews (optionally @tag reviewers) -->
- [ ] Technical review
- [ ] Editorial review
- [ ] Product review
---------
Co-authored-by: Craig Osterhout <103533812+craig-osterhout@users.noreply.github.com>
## Description
Replace `docker-compose` with `docker compose` CLI in the Java and
Node.js guides to align with the latest Docker standards and ensure
consistency across the docs.
## Related issues or tickets
Closes#22319
<!-- Related issues, pull requests, or Jira tickets -->
<!--Delete sections as needed -->
## Description
Update develop.md for highlighted lines
<!-- Tell us what you did and why -->
## Related issues or tickets
N/A
<!-- Related issues, pull requests, or Jira tickets -->
## Reviews
<!-- Notes for reviewers here -->
<!-- List applicable reviews (optionally @tag reviewers) -->
@aevesdocker @sarahsanders-docker
- [ ] Technical review
- [ ] Editorial review
- [ ] Product review
<!--Delete sections as needed -->
## Description
Updated Hub nav items to new left nav.
## Related issues or tickets
ENGDOCS -2447
## Reviews
<!-- Notes for reviewers here -->
<!-- List applicable reviews (optionally @tag reviewers) -->
- [ ] Editorial review
- [ ] Product review
Signed-off-by: Craig <craig.osterhout@docker.com>
## 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
Kafbath publishes its images to Docker Hub, so changing the registry source to Hub instead of GHCR. Also, instead of using the latest tag, they publish merged changes onto a `main` tag.
## Description
This PR updates `git clone` command for sample repositories with `&& cd
<repo name>`. Forcing to change the working directory should reduce the
risk of forgetting to do.
## Related issues or tickets
## Reviews
@usha-mandya
- [ ] Technical review
- [x] Editorial review
- [ ] Product review
<!--Delete sections as needed -->
## Description
<!-- Tell us what you did and why -->
Fix a few grammar and spelling errors.
## Reviews
<!-- Notes for reviewers here -->
<!-- List applicable reviews (optionally @tag reviewers) -->
- [ ] Technical review
- [ ] Editorial review
- [ ] Product review
## Description
Having a multi-stage build is an essential thing to learn for
containerizing a compiled language.
## Related issues or tickets
N/A
## Reviews
- [ ] Technical review
- [ ] Editorial review
- [ ] Product review
<!--Delete sections as needed -->
## Description
There were a couple leftover buttons from when the layout changed and
the buttons became auto-generated. Removed the buttons.
## Related issues or tickets
<!-- Related issues, pull requests, or Jira tickets -->
## Reviews
<!-- Notes for reviewers here -->
<!-- List applicable reviews (optionally @tag reviewers) -->
- [ ] Editorial review
Signed-off-by: Craig <craig.osterhout@docker.com>
## Description
In this PR I added an article that was missing from several similar
pages.
## Reviews
- [ ] Technical review
- [x] Editorial review
- [ ] Product review
## Description
Added a new guide about RAG with genAI which also explains how RAG
actually work
## Reviews
- [ ] Technical review
- [x] Editorial review
- [ ] Product review
---------
Signed-off-by: Your Name <you@example.com>
Co-authored-by: Your Name <you@example.com>
Co-authored-by: Baransel SAGINDA <redirecter2@gmail.com>
Co-authored-by: Craig Osterhout <103533812+craig-osterhout@users.noreply.github.com>
