From 8a60fc0870899ac55b5afa2fd4198be759ae03bd Mon Sep 17 00:00:00 2001 From: mahula Date: Thu, 9 Nov 2023 14:42:48 +0100 Subject: [PATCH] revert changes on old doc files --- deployment/src/old/digital-ocean/README.md | 2 +- deployment/src/old/volumes/neo4j-offline-backup/README.md | 2 +- deployment/src/old/volumes/velero/README.md | 8 ++++---- 3 files changed, 6 insertions(+), 6 deletions(-) diff --git a/deployment/src/old/digital-ocean/README.md b/deployment/src/old/digital-ocean/README.md index ab02754ac..c5893f645 100644 --- a/deployment/src/old/digital-ocean/README.md +++ b/deployment/src/old/digital-ocean/README.md @@ -30,7 +30,7 @@ do this as a last step. We are storing our images in the s3-compatible [DigitalOcean Spaces](https://www.digitalocean.com/docs/spaces/). -We still want to take backups of our images in case something happens to the images in the cloud. See these [instructions](https://docs.digitalocean.com/products/spaces/reference/s3cmd/) about getting set up with `s3cmd` to take a copy of all images in a `Spaces` namespace, i.e. `ocelot-social-uploads`. +We still want to take backups of our images in case something happens to the images in the cloud. See these [instructions](https://www.digitalocean.com/docs/spaces/resources/s3cmd-usage/) about getting set up with `s3cmd` to take a copy of all images in a `Spaces` namespace, i.e. `ocelot-social-uploads`. After configuring `s3cmd` with your credentials, etc. you should be able to make a backup with this command. diff --git a/deployment/src/old/volumes/neo4j-offline-backup/README.md b/deployment/src/old/volumes/neo4j-offline-backup/README.md index 76dd844a2..7c34aa764 100644 --- a/deployment/src/old/volumes/neo4j-offline-backup/README.md +++ b/deployment/src/old/volumes/neo4j-offline-backup/README.md @@ -23,7 +23,7 @@ So, all we have to do is edit the kubernetes deployment of our Neo4J database and set a custom `command` every time we have to carry out tasks like backup, restore, seed etc. -First bring the application into [maintenance mode](https://github.com/Ocelot-Social-Community/Ocelot-Social/blob/master/webapp/maintenance/README.md#maintenance-mode) to ensure there are no +First bring the application into [maintenance mode](https://github.com/Ocelot-Social-Community/Ocelot-Social/blob/master/deployment/ocelot-social/maintenance/README.md) to ensure there are no database connections left and nobody can access the application. Run the following: diff --git a/deployment/src/old/volumes/velero/README.md b/deployment/src/old/volumes/velero/README.md index 96a9bf926..bf63f13c8 100644 --- a/deployment/src/old/volumes/velero/README.md +++ b/deployment/src/old/volumes/velero/README.md @@ -9,9 +9,9 @@ working reliably. It is very likely that DigitalOcean had some bugs when I tried out the steps below. {% endhint %} -We use [velero](https://github.com/vmware-tanzu/velero) for on premise backups, we +We use [velero](https://github.com/heptio/velero) for on premise backups, we tested on version `v0.11.0`, you can find their -documentation [here](https://github.com/vmware-tanzu/velero/releases/tag/v0.11.0). +documentation [here](https://heptio.github.io/velero/v0.11.0/). Our kubernets configurations adds some annotations to pods. The annotations define the important persistent volumes that need to be backed up. Velero will @@ -22,8 +22,8 @@ pick them up and store the volumes in the same cluster but in another namespace You have to install the binary `velero` on your computer and get a tarball of the latest release. We use `v0.11.0` so visit the -[release](https://github.com/vmware-tanzu/velero/releases/tag/v0.11.0) page and -download and extract e.g. [velero-v0.11.0-linux-arm64.tar.gz](https://github.com/vmware-tanzu/velero/releases/download/v0.11.0/velero-v0.11.0-linux-arm64.tar.gz). +[release](https://github.com/heptio/velero/releases/tag/v0.11.0) page and +download and extract e.g. [velero-v0.11.0-linux-arm64.tar.gz](https://github.com/heptio/velero/releases/download/v0.11.0/velero-v0.11.0-linux-amd64.tar.gz). ## Setup Velero Namespace