msb-public
/
helm
mirror of https://github.com/helm/helm
1
0
Code Issues Projects Releases Wiki Activity

clarify helm serve's intent

Browse Source 
A lot of community members are looking at `helm serve` as a production webserver to host their
charts. There are much better solutions out there like s3, wabs or gcs for cloud storage and
nginx, haproxy or apache for DIY dedicated web servers. Steering users in the right direction
will help users make the right decision when it comes to serving their charts in production.
pull/2267/head
Matthew Fisher 8 years ago
parent bc8b3bb17d
commit 43b393f617
3 changed files with 27 additions and 3 deletions
Show Stats Download Patch File Download Diff File

7
cmd/helm/serve.go
Unescape View File

@ -34,6 +34,13 @@ This command starts a local chart repository server that serves charts from a lo
The new server will provide HTTP access to a repository. By default, it will
scan all of the charts in '$HELM_HOME/repository/local' and serve those over
the local IPv4 TCP port (default '127.0.0.1:8879').
This command is intended to be used for educational and testing purposes only.
It is best to rely on a dedicated web server or a cloud-hosted solution like
Google Cloud Storage for production use.
See https://github.com/kubernetes/helm/blob/master/docs/chart_repository.md#hosting-chart-repositories
for more information on hosting chart repositories in a production setting.
`
type serveCmd struct {

9
docs/helm/helm_serve.md
Unescape View File

@ -12,6 +12,13 @@ The new server will provide HTTP access to a repository. By default, it will
scan all of the charts in '$HELM_HOME/repository/local' and serve those over
the local IPv4 TCP port (default '127.0.0.1:8879').
This command is intended to be used for educational and testing purposes only.
It is best to rely on a dedicated web server or a cloud-hosted solution like
Google Cloud Storage for production use.
See https://github.com/kubernetes/helm/blob/master/docs/chart_repository.md#hosting-chart-repositories
for more information on hosting chart repositories in a production setting.
```
helm serve
@ -38,4 +45,4 @@ helm serve
### SEE ALSO
* [helm](helm.md) - The Helm package manager for Kubernetes.
###### Auto generated by spf13/cobra on 11-Mar-2017
###### Auto generated by spf13/cobra on 12-Apr-2017

14
docs/man/man1/helm_serve.1
Unescape View File

@ -1,4 +1,4 @@
.TH "HELM" "1" "Mar 2017" "Auto generated by spf13/cobra" ""
.TH "HELM" "1" "Apr 2017" "Auto generated by spf13/cobra" ""
.nh
.ad l
@ -22,6 +22,16 @@ The new server will provide HTTP access to a repository. By default, it will
scan all of the charts in '$HELM\_HOME/repository/local' and serve those over
the local IPv4 TCP port (default '127.0.0.1:8879').
.PP
This command is intended to be used for educational and testing purposes only.
It is best to rely on a dedicated web server or a cloud\-hosted solution like
Google Cloud Storage for production use.
.PP
See
\[la]https://github.com/kubernetes/helm/blob/master/docs/chart_repository.md#hosting-chart-repositories\[ra]
for more information on hosting chart repositories in a production setting.
.SH OPTIONS
.PP
@ -66,4 +76,4 @@ the local IPv4 TCP port (default '127.0.0.1:8879').
.SH HISTORY
.PP
11\-Mar\-2017 Auto generated by spf13/cobra
12\-Apr\-2017 Auto generated by spf13/cobra

Write Preview
Loading…
Cancel
Save