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

Remove hosted chef from docs #3285

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs-chef-io/content/workstation/config_rb.md
Original file line number Diff line number Diff line change
Expand Up @@ -229,10 +229,10 @@ settings:
`http_proxy_pass`
: The password for the proxy server when the proxy server is using an HTTP connection. Default value: `nil`.

#### HTTPS Proxy Settings (such as the hosted Chef Infra Server)
#### HTTPS Proxy Settings

`https_proxy`
: The proxy server for HTTPS connections. (The hosted Chef Infra Server uses an HTTPS connection.) Default value: `nil`.
: The proxy server for HTTPS connections. Default value: `nil`.

`https_proxy_user`
: The user name for the proxy server when the proxy server is using an HTTPS connection. Default value: `nil`.
Expand Down
28 changes: 14 additions & 14 deletions docs-chef-io/content/workstation/getting_started.md
Original file line number Diff line number Diff line change
Expand Up @@ -23,9 +23,9 @@ This guide walks you through the four parts to set up Chef Workstation on your c

## Prerequisites

1. [Download and install Chef Workstation]({{< relref "install_workstation.md" >}})
1. A running instance of [Chef Infra Server]({{< relref "server/install_server.md" >}}) or [Hosted Chef Server](https://manage.chef.io/signup).
1. Unless using Chef Manage or Hosted Chef, the `CLIENT.PEM` file supplied by your Chef administrator.
- [Chef Workstation]({{< relref "install_workstation.md" >}})
- A running instance of [Chef Infra Server]({{< relref "server/install_server.md" >}}).
- Unless using Chef Manage, the `CLIENT.PEM` file supplied by your Chef administrator.

## Configure Ruby Environment

Expand Down Expand Up @@ -102,7 +102,7 @@ The `knife configure` command requires the following values:
- `Chef Server URL`: the full URL to your Chef Infra Server including the org
- `Client Name`: the client name your server administrator created for you

Your Chef administrator should provide this information. For Hosted Chef or Chef Manage, you can find this information in the Starter Kit file. Download the file on the Manage site by navigating to the Administration tab and selecting Starter Kit. (**Manage > Administration > Starter Kit > Download Starter Kit**)
Your Chef administrator should provide this information. For Chef Manage, you can find this information in the Starter Kit file. Download the file on the Manage site by navigating to the Administration tab and selecting Starter Kit. (**Manage > Administration > Starter Kit > Download Starter Kit**)

Find the `.chef/config.rb` file in the Starter Kit. It should look like:

Expand All @@ -127,7 +127,7 @@ The steps for downloading or generating these files vary depending on how you in
<!----Tabs Section--->
{{< foundation_tabs tabs-id="tabs-panel-container" >}}
{{< foundation_tab active="true" panel-link="infra_and_automate_keys" tab-text="Chef Infra Server / Automate">}}
{{< foundation_tab panel-link="hosted-keys" tab-text="Hosted Chef / Manage" >}}
{{< foundation_tab panel-link="hosted-keys" tab-text="Chef Manage" >}}
{{< /foundation_tabs >}}
<!----End Tabs --->

Expand All @@ -137,33 +137,33 @@ The steps for downloading or generating these files vary depending on how you in

Your Chef administrator will provide you with your client.pem file. Copy this file to the `~/.chef` directory.

On macOS and Linux systems this looks something like:
On macOS and Linux systems, this looks something like:

```bash
cp ~/Downloads/MY_NAME.pem ~/.chef/
cp ~/Downloads/USERNAME.pem ~/.chef/
```

On Windows systems this will look something like this:
On Windows systems this, looks something like this:

```powershell
Copy-Item -Path C:\Users\MY_NAME\Downloads\MY_NAME.pem -Destination C:\Users\MY_NAME\.chef\
Copy-Item -Path C:\Users\MY_NAME\Downloads\USERNAME.pem -Destination C:\Users\MY_NAME\.chef\
```

{{< /foundation_tabs_panel >}}
{{< foundation_tabs_panel panel-id="hosted-keys" >}}

The client key file is located in the Starter Kit at `.chef/MY_NAME.pem`. Copy the .pem file to the `~/.chef` directory.
The client key file is located in the Starter Kit at `.chef/USERNAME.pem`. Copy the .pem file to the `~/.chef` directory.

On macOS and Linux systems this looks something like:
On macOS and Linux systems, this looks something like:

```bash
cp ~/Downloads/chef-repo/.chef/MY_NAME.pem ~/.chef/
cp ~/Downloads/chef-repo/.chef/USERNAME.pem ~/.chef/
```

On Windows systems this will look something like this:
On Windows systems, this looks something like this:

```powershell
Copy-Item -Path C:\Users\MY_NAME\Downloads\chef-repo\.chef\MY_NAME.pem -Destination C:\Users\MY_NAME\.chef\
Copy-Item -Path C:\Users\MY_NAME\Downloads\chef-repo\.chef\USERNAME.pem -Destination C:\Users\MY_NAME\.chef\
```

{{< /foundation_tabs_panel >}}
Expand Down
Loading