mirror of
https://github.com/funkypenguin/geek-cookbook/
synced 2025-12-12 17:26:19 +00:00
Fix RSS redirect
Signed-off-by: David Young <davidy@funkypenguin.co.nz>
This commit is contained in:
@@ -17,6 +17,7 @@
|
||||
[duplicity]: /recipes/autopirate/duplicity/
|
||||
[emby]: /recipes/emby/
|
||||
[ghost]: /recipes/ghost/
|
||||
[flux]: /kubernetes/deployment/flux/
|
||||
[funkwhale]: /recipes/autopirate/funkwhale/
|
||||
[github_sponsor]: https://github.com/sponsors/funkypenguin
|
||||
[headphones]: /recipes/autopirate/headphones/
|
||||
|
||||
@@ -24,7 +24,7 @@ In this particular case, the following apply:
|
||||
|
||||
## How does Velero work?
|
||||
|
||||
Velero runs within a cluster, listening for custom resources defining backups, restores, destinations, schedules, etc. Based on a combination of all of these, Velero scrapes the kubernetes API, works out what to backup, and does so, according to a schedule.
|
||||
Velero backup runs within a cluster, listening for custom resources defining backups, restores, destinations, schedules, etc. Based on a combination of all of these, Velero scrapes the kubernetes API, works out what to backup, and does so, according to a schedule. Typically you'd deploy the velero helm chart into your repository either manually, or using a GitOps-like tool, such as [FluxCD][flux] or ArgoCD.
|
||||
|
||||
## Velero backup hooks
|
||||
|
||||
|
||||
@@ -25,7 +25,7 @@ https://geeks-cookbook.funkypenguin.co.nz/* https://geek-cookbook.funkypenguin.c
|
||||
|
||||
|
||||
# Use a better convention for RSS feed (could add more if necessary)
|
||||
/rss/ /rss/
|
||||
/rss/ /feed_rss_created.xml
|
||||
|
||||
# Old URLs which we need to redirect to working URLs
|
||||
/kubernetes/start/ /kubernetes/ 301!
|
||||
|
||||
Reference in New Issue
Block a user