post home assistant update
This commit is contained in:
14
README.md
14
README.md
@@ -17,6 +17,8 @@ A project to store container-based hosting stuff.
|
||||
- [Nextcloud](#nextcloud)
|
||||
- [Test Deploy](#test-deploy)
|
||||
- [Gitea](#gitea)
|
||||
- [Staging](#staging)
|
||||
- [Install](#install)
|
||||
- [Minecraft](#minecraft)
|
||||
- [Nimcraft](#nimcraft)
|
||||
- [Testing](#testing)
|
||||
@@ -313,7 +315,6 @@ helm upgrade \
|
||||
--values truenas-iscsi-enc0.yaml \
|
||||
--namespace democratic-csi \
|
||||
--create-namespace \
|
||||
--set-file driver.config.sshConnection.privateKey=secrets/democratic_rsa \
|
||||
--set driver.config.httpConnection.apiKey=$(cat secrets/truenas-api-key) \
|
||||
zfs-iscsi-enc0 democratic-csi/democratic-csi
|
||||
|
||||
@@ -323,7 +324,6 @@ helm upgrade \
|
||||
--values truenas-iscsi-enc1.yaml \
|
||||
--namespace democratic-csi \
|
||||
--create-namespace \
|
||||
--set-file driver.config.sshConnection.privateKey=secrets/democratic_rsa \
|
||||
--set driver.config.httpConnection.apiKey=$(cat secrets/truenas-api-key) \
|
||||
zfs-iscsi-enc1 democratic-csi/democratic-csi
|
||||
|
||||
@@ -333,7 +333,6 @@ helm upgrade \
|
||||
--values truenas-nfs-enc1.yaml \
|
||||
--namespace democratic-csi \
|
||||
--create-namespace \
|
||||
--set-file driver.config.sshConnection.privateKey=secrets/democratic_rsa \
|
||||
--set driver.config.httpConnection.apiKey=$(cat secrets/truenas-api-key) \
|
||||
zfs-nfs-enc1 democratic-csi/democratic-csi
|
||||
```
|
||||
@@ -537,6 +536,15 @@ they decide to change things. This is the first chart (besides ingress-nginx) wh
|
||||
we need to pay attention to the MetalLB annotation. This has been set in the values.yaml
|
||||
file.
|
||||
|
||||
#### Staging
|
||||
|
||||
There is a `gitea-staging.yaml` file with staging values. This should be installed in
|
||||
the `gitea-staging` namespace. Follow the instructions below, but replace the `gitea`
|
||||
namespace with `gitea-staging`. Staging is useful for testing major release upgrades,
|
||||
especially since Gitea tends to change how `values.yaml` is structured.
|
||||
|
||||
#### Install
|
||||
|
||||
First we need to create the gitea admin secret
|
||||
|
||||
```bash
|
||||
|
||||
Reference in New Issue
Block a user