• UnpledgedCatnapTipper@piefed.blahaj.zone
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 day ago

    Alright that gives me a good idea what your working with.

    I am running it along side some other projects, so I already had a reverse proxy set up, so I didn’t look closely at the other parts of the guide in that section.

    If you want to be able to use this server for other hosting in the future, you may want to set up a reverse proxy. I can give some advice about that if you’re interested!

    In your case, if the only thing you ever want to host on this box is Matrix, you don’t need a reverse proxy. You should be able to do the steps here and it should result in a working deployment.

    It looks like that should give you a tls.yaml file, which you need to include when issuing the helm command to deploy everything. This one:

    helm upgrade --install --namespace "ess" ess oci://ghcr.io/element-hq/ess-helm/matrix-stack -f ~/ess-config-values/hostnames.yaml <optional additional values files to pass> --wait
    

    You need to make sure that in the <optional> section, you include:

    -f ~/ess-config-values/tls.yaml
    

    So your command would be this, if you have no additional yaml files, and if you do, simply put “-f path/to/file” at the end, right before the “–wait”:

        helm upgrade --install --namespace "ess" ess oci://ghcr.io/element-hq/ess-helm/matrix-stack -f ~/ess-config-values/hostnames.yaml -f ~/ess-config-values/tls.yaml --wait