New translations update.mdx (Dutch)

[ci skip]
This commit is contained in:
crowdin 2024-07-07 13:55:24 +00:00
parent 4f9d8cabbe
commit 62f5421342

View File

@ -1,5 +1,5 @@
---
title: How to update Castopod?
title: Hoe update ik Castopod?
---
import { Aside } from "@astrojs/starlight/components";
@ -8,7 +8,7 @@ After installing Castopod, you may want to update your instance to the latest
version in order to enjoy the latest features ✨, bug fixes 🐛 and performance
improvements ⚡.
## Update instructions
## Instructies voor updaten
0. ⚠️ Before any update, we highly recommend you backup your Castopod files and
database.
@ -30,7 +30,7 @@ improvements ⚡.
- Note that you can also download the latest package from
[castopod.org](https://castopod.org/)
3. On your server:
3. Op uw server:
- Remove all files except `.env` and `public/media`
- Copy the new files from the downloaded package into your server
@ -51,6 +51,7 @@ improvements ⚡.
5. Clear your cache from your `Castopod Admin` > `Settings` > `general` >
`Housekeeping`
6. ✨ Enjoy your fresh instance, you're all done!
<Aside>
@ -63,13 +64,13 @@ Releases may come with additional update instructions (see
</Aside>
## Fully Automated updates
## Volledig geautomatiseerde updates
> Coming soon... 👀
> Binnenkort beschikbaar... 👀
## Frequently asked questions (FAQ)
## Veelgestelde vragen (FAQ)
### Where can I find my Castopod version?
### Waar kan ik mijn Castopod versie vinden?
Go to your Castopod admin panel, the version is displayed on the bottom left
corner.
@ -77,9 +78,9 @@ corner.
Alternatively, you can find the version in the `app > Config > Constants.php`
file.
### I haven't updated my instance in a long time… What should I do?
### I haven't updated my instance in a long time… Wat moet ik doen?
No problem! Just get the latest release as described above. Only, when going
Geen probleem! Just get the latest release as described above. Only, when going
through the release instructions (4), perform them sequentially, from the oldest
to the newest.
@ -89,7 +90,7 @@ to the newest.
For example, if you're on `v1.0.0-alpha.42` and would like to upgrade to
`v1.0.0-beta.1`:
0. (highly recommended) Make a backup of your files and database.
0. (sterk aanbevolen) Maak een back-up van je bestanden en database.
1. Download the latest release, overwrite your files whilst keeping `.env` and
`public/media`.
@ -98,9 +99,9 @@ For example, if you're on `v1.0.0-alpha.42` and would like to upgrade to
newest) starting with `v1.0.0-alpha.43`, `v1.0.0-alpha.44`,
`v1.0.0-alpha.45`, …, `v1.0.0-beta.1`.
3. ✨ Enjoy your fresh instance, you're all done!
3. ✨ Geniet van je nieuwe instantie, je bent helemaal klaar!
### Should I make a backup before updating?
### Moet ik een back-up maken voordat ik update?
We advise you do, so you don't lose everything if anything goes wrong!