meissa/c4k-nextcloud
6
0
Fork 0
Code Issues Pull requests Projects Releases 19 Packages Wiki Activity

update readme

Browse source
This commit is contained in:
bom 2021-11-12 11:53:00 +01:00
parent 2cff7879ac
commit 22fe84cb45
1 changed files with 6 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
src/test/resources/local-integration-test/README.md
View file

@ -51,6 +51,12 @@ k3d is a k3s system which is running inside of a container. To install k3d run `
* Create and deploy the c4k yaml for nextcloud (incl. postgres etc): * Create and deploy the c4k yaml for nextcloud (incl. postgres etc):
`java -jar target/uberjar/c4k-nextcloud-standalone.jar valid-config.edn valid-auth.edn | kubectl apply -f -` `java -jar target/uberjar/c4k-nextcloud-standalone.jar valid-config.edn valid-auth.edn | kubectl apply -f -`
* With `kubectl get ingress` you can view the ingress' ip (e.g. 10.0.2.15), add (resp. change if already existing) a line to file "/etc/hosts" e.g. `10.0.2.15 k3stesthost cloudhost` * With `kubectl get ingress` you can view the ingress' ip (e.g. 10.0.2.15), add (resp. change if already existing) a line to file "/etc/hosts" e.g. `10.0.2.15 k3stesthost cloudhost`
* you can also use `kubectl get ingress ingress-localstack -o jsonpath="{.status.loadBalancer.ingress[0].ip}"`
* Scale the backup-restore pod to one replica with `kubectl scale deployment backup-restore --replicas 1`
* connect onto the newly created pod with `kubectl exec -it backup-restore<hash> -- bash`
* add the ingress ip to /etc/hosts on the pod
* copy the certificate file `ca.crt` to the pod and set the environment variable `$CERTIFICATE_FILE` to its path
* test the scripts in /usr/local/bin first `init.sh` then `backup.sh` and `restore.sh`
Some of the steps may take some min to be effective, but eventually nextcloud should be available at: https://cloudhost Some of the steps may take some min to be effective, but eventually nextcloud should be available at: https://cloudhost