Compare commits

..

5 Commits

Author SHA1 Message Date
Danish
d1c3639c77
docs(web): show the doc version in the install manifest text (#1077)
The installation page said "the manifest for the latest release"
everywhere, even on older versioned docs and on the unreleased Dev
docs. Show the actual version instead (or "the latest development
snapshot from the main branch" on Dev docs).

The "Testing the latest development snapshot" section now explains,
on Dev docs, that the command above already installs that snapshot,
instead of duplicating it.

Signed-off-by: Danish <danish.khan@enterprisedb.com>
2026-08-28 10:55:30 +02:00
Marco Nenciarini
de67340c71
refactor(web): drop the now-dead useCurrentVersion abstraction
Its 'latestReleased' branch had no remaining caller after the
previous commit, and InstallationSnippet was calling useActiveVersion
twice (once directly, once through the hook) to re-run the same
check. Build the manifest URL straight from the active version and
drop hooks/versions.ts entirely.

Signed-off-by: Marco Nenciarini <marco.nenciarini@enterprisedb.com>
2026-08-28 10:55:30 +02:00
Marco Nenciarini
df0359ce68
feat(web): point unreleased docs install snippet at main manifest
The unversioned "current" docs describe unreleased functionality, so
a tagged release manifest doesn't make sense there. Install from the
manifest built off main instead.

Signed-off-by: Marco Nenciarini <marco.nenciarini@enterprisedb.com>
2026-08-28 10:55:30 +02:00
Marco Nenciarini
5532b5b2fd
refactor(web): simplify useLatestReleasedVersion
Docusaurus already exposes the latest released version via
useLatestVersion (backed by GlobalVersion.isLast), making the manual
filter and numeric-string sort redundant.

Signed-off-by: Marco Nenciarini <marco.nenciarini@enterprisedb.com>
2026-08-28 10:55:30 +02:00
Marco Nenciarini
294e9c44ed
docs(web): use active doc version for install manifest link
The install snippet always linked to the manifest of the latest
released version, regardless of which versioned docs page it was
rendered on. Viewing the 0.13.0 installation page therefore pointed
at the 0.14.0 manifest.

Fall back to the latest released version only when there is no
active version, or the active version is the unreleased "current"
docs.

Signed-off-by: Marco Nenciarini <marco.nenciarini@enterprisedb.com>
2026-08-28 10:55:30 +02:00

View File

@ -35,7 +35,7 @@ object storage system. It allows you to configure:
- **Base backup options**—with similar settings for compression, concurrency, - **Base backup options**—with similar settings for compression, concurrency,
and encryption—under `.spec.configuration.data` and encryption—under `.spec.configuration.data`
- **Retention policies** to manage the life-cycle of archived WALs and backups - **Retention policies** to manage the life-cycle of archived WALs and backups
via `.spec.retentionPolicy` via `.spec.configuration.retentionPolicy`
WAL files are archived in the `wals` directory, while base backups are stored WAL files are archived in the `wals` directory, while base backups are stored
as **tarballs** in the `base` directory, following the as **tarballs** in the `base` directory, following the