tkmind/tkmind_go
1
0
Fork 0
Code Issues Pull Requests Actions 4 Packages Projects Releases Wiki Activity

docs: lowercase goose in remaining topics (#5861)

Browse Source
This commit is contained in:
dianed-square
2025-11-24 11:05:41 -08:00
committed by GitHub
parent b357e99b30
commit e7eb18b67a
37 changed files with 306 additions and 306 deletions
Download Patch File Download Diff File Expand all files Collapse all files
documentation/docs/tutorials/goose-in-docker.md
+8 -8
View File
@@ -1,14 +1,14 @@
---
title: Building Goose in Docker
sidebar_label: Goose in Docker
title: Building goose in Docker
sidebar_label: goose in Docker
---
:::info Tell Us What You Need
There are various scenarios where you might want to build Goose in Docker. If the instructions below do not meet your needs, please contact us by replying to our [discussion topic](https://github.com/block/goose/discussions/1496).
There are various scenarios where you might want to build goose in Docker. If the instructions below do not meet your needs, please contact us by replying to our [discussion topic](https://github.com/block/goose/discussions/1496).
:::
You can build Goose from the source file within a Docker container. This approach not only provides security benefits by creating an isolated environment but also enhances consistency and portability. For example, if you need to troubleshoot an error on a platform you don't usually work with (such as Ubuntu), you can easily debug it using Docker.
You can build goose from the source file within a Docker container. This approach not only provides security benefits by creating an isolated environment but also enhances consistency and portability. For example, if you need to troubleshoot an error on a platform you don't usually work with (such as Ubuntu), you can easily debug it using Docker.
To begin, you will need to modify the `Dockerfile` and `docker-compose.yml` files to suit your requirements. Some changes you might consider include:
@@ -16,7 +16,7 @@ To begin, you will need to modify the `Dockerfile` and `docker-compose.yml` file
- **Optional:** Changing the base image to a different Linux distribution in the `Dockerfile`. This example uses Ubuntu, but you can switch to another distribution such as CentOS, Fedora, or Alpine.
- **Optional:** Mounting your personal Goose settings and hints files in the `docker-compose.yml` file. This allows you to use your personal settings and hints files within the Docker container.
- **Optional:** Mounting your personal goose settings and hints files in the `docker-compose.yml` file. This allows you to use your personal settings and hints files within the Docker container.
@@ -32,7 +32,7 @@ Next, run the container and connect to it using the following command:
docker-compose -f documentation/docs/docker/docker-compose.yml run --rm goose-cli
```
Inside the container, run the following command to configure Goose:
Inside the container, run the following command to configure goose:
```bash
goose configure
@@ -40,7 +40,7 @@ goose configure
When prompted to save the API key to the keyring, select `No`, as you are already passing the API key as an environment variable.
Configure Goose a second time, and this time, you can [add any extensions](/docs/getting-started/using-extensions) you need.
Configure goose a second time, and this time, you can [add any extensions](/docs/getting-started/using-extensions) you need.
After that, you can start a session:
@@ -48,4 +48,4 @@ After that, you can start a session:
goose session
```
You should now be able to connect to Goose with your configured extensions enabled.
You should now be able to connect to goose with your configured extensions enabled.