When running a standalone container users will be connecting directly to

HGKeeper for both HTTP and SSH access. You can put an HTTP reverse proxy in

front of HGKeeper's HTTP server if you would like to add TLS support as

HGKeeper does not currently offer direct TLS support.

This methods is how we run our own instance under

[Kubernetes](https://kubernetes.io/). If you're interested in learning more

about our setup, you can find our

[Kustomization](https://kubernetes.io/docs/tasks/manage-kubernetes-objects/kustomization/)

manifests at

[keep.imfreedom.org/imfreedom/k8s-cluster/](https://keep.imfreedom.org/imfreedom/k8s-cluster/file/default/50-keep.imfreedom.org).

{%

include-markdown "../includes/container.md"

heading-offset=1

%}

{%

include-markdown "../includes/adminrepositorycontainer.md"

heading-offset=1

%}

{%

include-markdown "../includes/hostkeys.md"

heading-offset=1

%}

{%

include-markdown "../includes/runningcontainer.md"

heading-offset=1

%}

You should now be able to clone the `hgkeeper` administration repo from the

container. We will use the following command to verify that everything has been

setup correctly.

From your host, run the following command:

If the repository cloned, you are good to go!

If that didn't work, be sure to check the logs of the HGKeeper container and

double check all of your configuration.