Merge pull request #21132 from docker/published-update

publish updates from main

content/guides/bun/_index.md

@@ -0,0 +1,34 @@
+---
+description: Containerize and develop Bun applications using Docker.
+keywords: getting started, bun
+title: Bun language-specific guide
+summary: |
+  Learn how to containerize JavaScript applications with the Bun runtime.
+linkTitle: Bun
+levels: [beginner]
+languages: [js]
+params:
+  time: 10 minutes
+---
+
+The Bun getting started guide teaches you how to create a containerized Bun application using Docker. In this guide, you'll learn how to:
+
+> **Acknowledgment**
+>
+> Docker would like to thank [Pradumna Saraf](https://twitter.com/pradumna_saraf) for his contribution to this guide.
+
+## What will you learn?
+
+* Containerize and run a Bun application using Docker
+* Set up a local environment to develop a Bun application using containers
+* Configure a CI/CD pipeline for a containerized Bun application using GitHub Actions
+* Deploy your containerized application locally to Kubernetes to test and debug your deployment
+
+## Prerequisites
+
+- Basic understanding of JavaScript is assumed.
+- You must have familiarity with Docker concepts like containers, images, and Dockerfiles. If you are new to Docker, you can start with the [Docker basics](/get-started/docker-concepts/the-basics/what-is-a-container.md) guide.
+
+After completing the Bun getting started modules, you should be able to containerize your own Bun application based on the examples and instructions provided in this guide.
+
+Start by containerizing an existing Bun application.

content/guides/bun/configure-ci-cd.md

@@ -0,0 +1,131 @@
+---
+title: Configure CI/CD for your Bun application
+linkTitle: Configure CI/CD
+weight: 40
+keywords: ci/cd, github actions, bun, shiny
+description: Learn how to configure CI/CD using GitHub Actions for your Bun application.
+aliases:
+- /language/bun/configure-ci-cd/
+---
+
+## Prerequisites
+
+Complete all the previous sections of this guide, starting with [Containerize a Bun application](containerize.md). You must have a [GitHub](https://github.com/signup) account and a [Docker](https://hub.docker.com/signup) account to complete this section.
+
+## Overview
+
+In this section, you'll learn how to set up and use GitHub Actions to build and test your Docker image as well as push it to Docker Hub. You will complete the following steps:
+
+1. Create a new repository on GitHub.
+2. Define the GitHub Actions workflow.
+3. Run the workflow.
+
+## Step one: Create the repository
+
+Create a GitHub repository, configure the Docker Hub credentials, and push your source code.
+
+1. [Create a new repository](https://github.com/new) on GitHub.
+
+2. Open the repository **Settings**, and go to **Secrets and variables** >
+   **Actions**.
+
+3. Create a new **Repository variable** named `DOCKER_USERNAME` and your Docker ID as value.
+
+4. Create a new [Personal Access Token (PAT)](/manuals/security/for-developers/access-tokens.md#create-an-access-token)for Docker Hub. You can name this token `docker-tutorial`. Make sure access permissions include Read and Write.
+
+5. Add the PAT as a **Repository secret** in your GitHub repository, with the name
+   `DOCKERHUB_TOKEN`.
+
+6. In your local repository on your machine, run the following command to change
+   the origin to the repository you just created. Make sure you change
+   `your-username` to your GitHub username and `your-repository` to the name of
+   the repository you created.
+
+   ```console
+   $ git remote set-url origin https://github.com/your-username/your-repository.git
+   ```
+
+7. Run the following commands to stage, commit, and push your local repository to GitHub.
+
+   ```console
+   $ git add -A
+   $ git commit -m "my commit"
+   $ git push -u origin main
+   ```
+
+## Step two: Set up the workflow
+
+Set up your GitHub Actions workflow for building, testing, and pushing the image
+to Docker Hub.
+
+1. Go to your repository on GitHub and then select the **Actions** tab.
+
+2. Select **set up a workflow yourself**.
+
+   This takes you to a page for creating a new GitHub actions workflow file in
+   your repository, under `.github/workflows/main.yml` by default.
+
+3. In the editor window, copy and paste the following YAML configuration and commit the changes.
+
+   ```yaml
+   name: ci
+
+   on:
+     push:
+       branches:
+         - main
+
+   jobs:
+     build:
+       runs-on: ubuntu-latest
+       steps:
+         -
+           name: Login to Docker Hub
+           uses: docker/login-action@v3
+           with:
+             username: ${{ vars.DOCKER_USERNAME }}
+             password: ${{ secrets.DOCKERHUB_TOKEN }}
+         -
+           name: Set up Docker Buildx
+           uses: docker/setup-buildx-action@v3
+         -
+           name: Build and push
+           uses: docker/build-push-action@v6
+           with:
+             platforms: linux/amd64,linux/arm64
+             push: true
+             tags: ${{ vars.DOCKER_USERNAME }}/${{ github.event.repository.name }}:latest
+   ```
+
+   For more information about the YAML syntax for `docker/build-push-action`,
+   refer to the [GitHub Action README](https://github.com/docker/build-push-action/blob/master/README.md).
+
+## Step three: Run the workflow
+
+Save the workflow file and run the job.
+
+1. Select **Commit changes...** and push the changes to the `main` branch.
+
+   After pushing the commit, the workflow starts automatically.
+
+2. Go to the **Actions** tab. It displays the workflow.
+
+   Selecting the workflow shows you the breakdown of all the steps.
+
+3. When the workflow is complete, go to your
+   [repositories on Docker Hub](https://hub.docker.com/repositories).
+
+   If you see the new repository in that list, it means the GitHub Actions
+   successfully pushed the image to Docker Hub.
+
+## Summary
+
+In this section, you learned how to set up a GitHub Actions workflow for your Bun application.
+
+Related information:
+ - [Introduction to GitHub Actions](/manuals/build/ci/github-actions/_index.md)
+ - [Workflow syntax for GitHub Actions](https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions)
+
+## Next steps
+
+Next, learn how you can locally test and debug your workloads on Kubernetes before deploying.

content/guides/bun/containerize.md

@@ -0,0 +1,127 @@
+---
+title: Containerize a Bun application
+linkTitle: Containerize your app
+weight: 10
+keywords: bun, containerize, initialize
+description: Learn how to containerize a Bun application.
+aliases:
+  - /language/bun/containerize/
+---
+
+## Prerequisites
+
+* You have a [Git client](https://git-scm.com/downloads). The examples in this section use a command-line based Git client, but you can use any client.
+
+## Overview
+
+For a long time, Node.js has been the de-facto runtime for server-side
+JavaScript applications. Recent years have seen a rise in new alternative
+runtimes in the ecosystem, including [Bun website](https://bun.sh/). Like
+Node.js, Bun is a JavaScript runtime. Bun is a comparatively lightweight
+runtime that is designed to be fast and efficient.
+
+Why develop Bun applications with Docker? Having multiple runtimes to choose
+from is great. But as the number of runtimes increases, it becomes challenging
+to manage the different runtimes and their dependencies consistently across
+environments. This is where Docker comes in. Creating and destroying containers
+on demand is a great way to manage the different runtimes and their
+dependencies. Also, as it's fairly a new runtime, getting a consistent
+development environment for Bun can be challenging. Docker can help you set up
+a consistent development environment for Bun.
+
+## Get the sample application
+
+Clone the sample application to use with this guide. Open a terminal, change
+directory to a directory that you want to work in, and run the following
+command to clone the repository:
+
+```console
+$ git clone https://github.com/Pradumnasaraf/bun-docker.git
+```
+
+You should now have the following contents in your `bun-docker` directory.
+
+```text
+├── bun-docker/
+│ ├── compose.yml
+│ ├── Dockerfile
+│ ├── LICENSE
+│ ├── server.js
+│ └── README.md
+```
+
+In the Dockerfile, you'll notice that the `FROM` instruction uses `oven/bun`
+as the base image. This is the official image for Bun created by Oven, the
+company behind Bun. This image is [available on the Docker Hub](https://hub.docker.com/r/oven/bun).
+
+```dockerfile
+# Use the Bun image as the base image
+FROM oven/bun:latest
+
+# Set the working directory in the container
+WORKDIR /app
+
+# Copy the current directory contents into the container at /app
+COPY . .
+
+# Expose the port on which the API will listen
+EXPOSE 3000
+
+# Run the server when the container launches
+CMD ["bun", "server.js"]
+```
+
+Aside from specifying `oven/bun` as the base image, this Dockerfile also:
+
+- Sets the working directory in the container to `/app`
+- Copies the contents of the current directory to the `/app` directory in the container
+- Exposes port 3000, where the API is listening for requests
+- And finally, starts the server when the container launches with the command `bun server.js`.
+
+## Run the application
+
+Inside the `bun-docker` directory, run the following command in a terminal.
+
+```console
+$ docker compose up --build
+```
+
+Open a browser and view the application at [http://localhost:3000](http://localhost:3000). You will see a message `{"Status" : "OK"}` in the browser.
+
+In the terminal, press `ctrl`+`c` to stop the application.
+
+### Run the application in the background
+
+You can run the application detached from the terminal by adding the `-d`
+option. Inside the `bun-docker` directory, run the following command
+in a terminal.
+
+```console
+$ docker compose up --build -d
+```
+
+Open a browser and view the application at [http://localhost:3000](http://localhost:3000).
+
+
+In the terminal, run the following command to stop the application.
+
+```console
+$ docker compose down
+```
+
+## Summary
+
+In this section, you learned how you can containerize and run your Bun
+application using Docker.
+
+Related information:
+
+ - [Dockerfile reference](/reference/dockerfile.md)
+ - [.dockerignore file](/reference/dockerfile.md#dockerignore-file)
+ - [Docker Compose overview](/manuals/compose/_index.md)
+ - [Compose file reference](/reference/compose-file/_index.md)
+
+## Next steps
+
+In the next section, you'll learn how you can develop your application using
+containers.