Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs: Goose on Windows via WSL #901

Merged
merged 9 commits into from
Jan 30, 2025
Merged

docs: Goose on Windows via WSL #901

merged 9 commits into from
Jan 30, 2025

Conversation

acekyd
Copy link
Collaborator

@acekyd acekyd commented Jan 29, 2025

This pull request adds a new section to the installation documentation for Goose, providing detailed instructions on how to install and configure Goose CLI on Windows using the Windows Subsystem for Linux (WSL).

Documentation updates:

  • documentation/docs/getting-started/installation.md: Added a new subsection "Installing on Windows via WSL" with step-by-step instructions for installing WSL, updating packages, installing Goose CLI, setting environment variables, and configuring Goose.

@angiejones
Copy link
Collaborator

update SuppirtingEnvironments component

@acekyd acekyd requested a review from angiejones January 29, 2025 16:05
Co-authored-by: Angie Jones <jones.angie@gmail.com>
@angiejones
Copy link
Collaborator

It's a bit hard to see the windows instructions, and people may follow the macOS/Linux instructions before ever realizing you have a section for Windows

image

Let's make sections that appear on the right nav bar with h2 and h3

Install

macOS | Linux

...

Windows

...

acekyd and others added 5 commits January 29, 2025 20:05
Co-authored-by: Angie Jones <jones.angie@gmail.com>
Co-authored-by: Angie Jones <jones.angie@gmail.com>
Co-authored-by: Angie Jones <jones.angie@gmail.com>
@acekyd
Copy link
Collaborator Author

acekyd commented Jan 29, 2025

Update: Realized I was completing all the steps under WSL, so I cleaned that up and have them follow the rest of the steps.

@angiejones angiejones merged commit ccd1427 into main Jan 30, 2025
1 check passed
@angiejones angiejones deleted the docs/goose-windows branch January 30, 2025 05:41
salman1993 added a commit that referenced this pull request Jan 30, 2025
* origin/main:
  fix: clarify linux cli install only (#927)
  feat: update ui for ollama host (#912)
  feat: add CONFIGURE=false option in install script (#920)
  fix: truncation agent token calculations (#915)
  fix: request payload for o1 models (#921)
  Update SupportedEnvironments.js so others don't get confused on why they can not open the macos app on x86 (#888)
  fix: improve configure process with error message (#919)
  docs: Goose on Windows via WSL (#901)
  fix: more graceful handling of missing usage in provider response (#907)
  feat: rm uv.lock cause it points to square artifactory (#917)
  feat: Update issue templates for bug report for goose (#913)
  fix: post endpoint url on sse endpoint event (#900)
michaelneale added a commit that referenced this pull request Jan 31, 2025
* main: (28 commits)
  ci: per semver build metadata should be after + (#971)
  fix: temp fix to make CI workflow pass (#970)
  chore: bump patch version to 1.0.3 (#967)
  fix: load shell automatically from env for GUI (#948)
  fix: update versions in release and canary workflows (#911)
  docs: fix typo, name (#963)
  docs: typo fix (#961)
  chore: remove gpt-3.5-turbo UI suggestion, as it is deprecated (#959)
  chore: remove o1-mini suggestion from UI add model view (#957)
  fix: missing field in request (#956)
  docs: update provider docs, fix rate limit link (#943)
  fix: clarify linux cli install only (#927)
  feat: update ui for ollama host (#912)
  feat: add CONFIGURE=false option in install script (#920)
  fix: truncation agent token calculations (#915)
  fix: request payload for o1 models (#921)
  Update SupportedEnvironments.js so others don't get confused on why they can not open the macos app on x86 (#888)
  fix: improve configure process with error message (#919)
  docs: Goose on Windows via WSL (#901)
  fix: more graceful handling of missing usage in provider response (#907)
  ...
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants