IF YOU WOULD LIKE TO GET AN ACCOUNT, please write an
email to Administrator. User accounts are meant only to access repo
and report issues and/or generate pull requests.
This is a purpose-specific Git hosting for
BaseALT
projects. Thank you for your understanding!
Только зарегистрированные пользователи имеют доступ к сервису!
Для получения аккаунта, обратитесь к администратору.
This hides the TOC by default on narrower screens (< 1000 px/dp) and
adds a simple toggle menu to make it pop out.
Most is handled purely through CSS, but to hide the menu when clicking
on links or when there is no TOC at all (e.g., for the index or FAQ)
we need a bit of JavaScript. There just monkey patch the asciidoc TOC
JS function to ensure we get called in the correct moment.
Further, add a modal-like "label" over the content if the TOC menu is
open, clicking on that will also close the TOC, again with pure CSS.
This also tries to improve styling and readability for mobile in
general, while I tested on many sizes, virtual devices in Firefox and
Chromiums developer mode, and also some actual smartphone, it
certainly will not yet be perfect everywhere, but it definitively
should be better than the status quo.
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
This avoids that wide tables where the cell content cannot easily wrap
cause horizontal scrolling for the whole page, rather just cause that
scrolling for the table itself, so wrap in in a div and make that use
overflow-x: auto style.
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
This is just a short paragraph anyway and quite definitively was only
declared as toplevel by mistake.
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
Migrating proxmox-firewall to the proxmox_log crate has removed the
RUST_LOG environment variable, among other things. Additionally, the
proxmox-firewall binary now has subcommands for dumping the generated
firewall ruleset. Update the documentation to provide information on
how to use the new subcommands for debugging proxmox-firewall.
Signed-off-by: Stefan Hanreich <s.hanreich@proxmox.com>
Link: https://lore.proxmox.com/20250527135800.190084-5-s.hanreich@proxmox.com
The latest updates to the backup-job UI completely drop the term
"Notification System" from the UI, instead we now use "Global
notification settings", which should be hopefully a bit clearer to users
with regards to what this actually means.
Furthermore, the 'auto' notification mode is not exposed anymore in the
UI, hence we also drop it from the documentation to avoid confusion. It
is still listed in the backup job option reference section, for any user
who might still be using it.
Some of the touched sections were slightly rephrased to improve clarity.
Signed-off-by: Lukas Wagner <l.wagner@proxmox.com>
Reviewed-by: Michael Köppl <m.koeppl@proxmox.com>
Link: https://lore.proxmox.com/20250725082046.51199-1-l.wagner@proxmox.com
Mirroring pve-storage commit 7669a99 ("drop support for using
GlusterFS directly"). Native GlusterFS support will not be available
for PVE 9, one still can manually mount and use such a storage as
directory storage though, or keep using PVE 8 until EOL and use that
time for migrating to e.g. Ceph or the like.
The main reason is that upstream has stopped development and various
integrations are planned to go away soon, like the QEMU one. That's
why we cannot promote it as stable storage for PVE 9.
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
Fix the IPv6 section, now we don't enable IPv6 forwarding anymore, but
the user has to manually enable it. Also add some more info on how to do
it.
When applying the last fabrics series, this patch was missed, so update
the old docs to the latest version.
Signed-off-by: Gabriel Goller <g.goller@proxmox.com>
Reviewed-by: Hannes Duerr <h.duerr@proxmox.com>
Link: https://lore.proxmox.com/20250718080826.88560-1-g.goller@proxmox.com
It's explained in a foot-note at the bottom of the table anyway, so no
need to use harder to understand terms here, the essence is: yes, it's
supported now.
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
It seems that the shutdown procedure which we had documented (and many
others as well) can potentially cause problems when the cluster starts
up again.
There is a blog article from croit explaining it in detail [0] if you
are interested.
The shorter explanation is that when unsetting 'pause' it might take
half an hour to get out of that state. Unsetting nodown also could take
a long time. During all this OSDs and MONs might consume a lot of CPU
resources, increasing the CPU load on the host considerbly.
nobackfill and norecover are not needed, but also not harmful.
Archeology revealed that the procedure with all the other flags (which
this commit removes), originated in the RedHat documentation, but was
never part of Ceph's shutdown procedure which is tested by the Ceph
team.
[0] https://web.archive.org/web/20250624082830/https://www.croit.io/blog/how-not-to-shut-down-a-ceph-cluster
Signed-off-by: Aaron Lauterer <a.lauterer@proxmox.com>
Link: https://lore.proxmox.com/20250624085306.3224755-1-a.lauterer@proxmox.com
Add the required "Fingerprint" option of the NetBox IPAM plugin to the
docs. Also add a quick `openssl` command to retrieve the fingerprint
from the default certificate on a NetBox installation. AFAIK NetBox
doesn't provide a way to easily get the fingerprint from the gui.
Signed-off-by: Gabriel Goller <g.goller@proxmox.com>
Link: https://lore.proxmox.com/20250611123216.236179-1-g.goller@proxmox.com
