Skip to content

Commit 4288a1c

Browse files
committed
Helm: fix some typos
1 parent 072af2c commit 4288a1c

File tree

1 file changed

+7
-7
lines changed

1 file changed

+7
-7
lines changed

docs/self-hosted/kubernetes-helm.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -2,17 +2,17 @@
22
##
33

44
The Private Packagist Self-Hosted Helm chart allows you to install Private Packagist in an existing Kubernetes cluster,
5-
to instead install Private Packagist Self-Hosted without an existing Kubernetes cluster follow [this guide](./kubernetes-embedded.md).
5+
to instead install Private Packagist Self-Hosted without an existing Kubernetes cluster, follow [this guide](./kubernetes-embedded.md).
66

77
## General requirements
88

99
1. A Kubernetes cluster v1.23 or newer
10-
1. Your username and password to log in to the Helm registry on registry.replicated.com. You can find your credentials with your Private Packagist account on https://packagist.com. Don't have one yet? [Sign up for a free trial license!](https://packagist.com/self-hosted)
10+
1. Your username and password to log in to the Helm registry on registry.replicated.com. You can find your credentials in your Private Packagist account at https://packagist.com. Don't have one yet? [Sign up for a free trial license!](https://packagist.com/self-hosted)
1111
1. One (sub-)domain to operate the web interface, e.g. packagist.myintranet.com
1212
1. One (sub-)domain to operate the composer repository, e.g. repo.packagist.myintranet.com or packagist-repo.myintranet.com
1313
1. An SSL certificate valid for both chosen domains
1414
1. An SMTP server or a GMail account for Private Packagist Self-Hosted to send email
15-
1. If your firewall restricts external connections the following domains must be accessible from the server:
15+
1. If your firewall restricts external connections then the following domains must be accessible from the server:
1616
* hub.docker.com
1717
* proxy.replicated.com
1818
* registry.replicated.com
@@ -26,13 +26,13 @@ Private Packagist Self-Hosted requires PostgreSQL, Redis, and blob storage to st
2626
You can either use the built-in options that come with the Helm chart or use your own PostgreSQL, Redis, and blob storage.
2727
For blob storage, we currently support Azure Blob Storage, Google Cloud Storage, AWS S3, and other S3-compatible storage solutions.
2828

29-
Please note that if you chose to use the built-int solution then each of the storage requires one or more volumes using
29+
Please note that if you choose to use the built-in solution then each of the storage requires one or more volumes using
3030
[dynamic volume provision](https://kubernetes.io/docs/concepts/storage/dynamic-provisioning/) to allocate storage for the different Pods.
31-
Configure the Storage Class in global values section.
31+
Configure the Storage Class in the values.yaml under `global.storageClass`.
3232

3333
### Annotated configuration
3434

35-
To install the Private Packagist Self-Hosted Helm Chart configure values based on your setup, store them in a YAML file, e.g. values.yaml, and then run the commands below.
35+
To install the Private Packagist Self-Hosted Helm Chart configure values based on your setup, store them in a YAML file, e.g. `values.yaml`, and then run the commands below.
3636

3737
HELM_CHART_VALUES_FILE
3838

@@ -91,7 +91,7 @@ You can configure the blog storage in the values.yaml under `storage.type`.
9191
The Private Packagist Self-Hosted application expects that TLS termination happens at or before the Ingress level.
9292
All traffic within the cluster is unencrypted.
9393

94-
Make sure your Kubernetes network plugin encrypts connections between pods to avoid potential security issues.
94+
Ensure your Kubernetes network plugin encrypts connections between pods to avoid potential security issues.
9595

9696
## Backups
9797

0 commit comments

Comments
 (0)