ocelot-Social-Community/Ocelot-Social
1
0
Fork 0
mirror of https://github.com/Ocelot-Social-Community/Ocelot-Social.git synced 2025-12-13 07:46:06 +00:00
Code Issues Packages Projects Releases Wiki Activity

fix further links in documentation

Browse Source
This commit is contained in:
mahula 2023-11-09 14:28:12 +01:00
parent 52c8d5cf9c
commit 82e15d4305
2 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
deployment/README.md
View File

@ -48,7 +48,7 @@ Since all deployment methods described here depend on [Docker](https://docker.co
The next step is: The next step is:
- [Set Environment Variables and Configurations](./deployment-values.md) - [Set Environment Variables and Configurations](./deployment-values.md)
- [Configure And Branding](./deployment/configurations/stage.ocelot.social/branding/README.md) - [Configure And Branding](./configurations/stage.ocelot.social/branding/README.md)
### Optional: Locally Testing Configuration And Branding ### Optional: Locally Testing Configuration And Branding

8
deployment/src/old/volumes/velero/README.md
View File

@ -9,9 +9,9 @@ working reliably. It is very likely that DigitalOcean had some bugs when I
tried out the steps below. tried out the steps below.
{% endhint %} {% endhint %}
We use [velero](https://github.com/heptio/velero) for on premise backups, we We use [velero](https://github.com/vmware-tanzu/velero) for on premise backups, we
tested on version `v0.11.0`, you can find their tested on version `v0.11.0`, you can find their
documentation [here](https://heptio.github.io/velero/v0.11.0/). documentation [here](https://github.com/vmware-tanzu/velero/releases/tag/v0.11.0).
Our kubernets configurations adds some annotations to pods. The annotations Our kubernets configurations adds some annotations to pods. The annotations
define the important persistent volumes that need to be backed up. Velero will 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 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 the latest release. We use `v0.11.0` so visit the
[release](https://github.com/heptio/velero/releases/tag/v0.11.0) page and [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/heptio/velero/releases/download/v0.11.0/velero-v0.11.0-linux-amd64.tar.gz). 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).
## Setup Velero Namespace ## Setup Velero Namespace