From 22fe84cb450d36d377c9a81dc0a8582c15f945ec Mon Sep 17 00:00:00 2001 From: bom Date: Fri, 12 Nov 2021 11:53:00 +0100 Subject: [PATCH] update readme --- src/test/resources/local-integration-test/README.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/src/test/resources/local-integration-test/README.md b/src/test/resources/local-integration-test/README.md index 8bfd0c7..8853671 100644 --- a/src/test/resources/local-integration-test/README.md +++ b/src/test/resources/local-integration-test/README.md @@ -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): `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` +* 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 -- 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