centersl/portainer-docs
1
0
Fork 0
mirror of https://github.com/portainer/portainer-docs.git synced 2026-03-27 04:48:31 +07:00
Code Issues Packages Projects Releases Wiki Activity

GITBOOK-32: Fix broken policies link

Browse Source
This commit is contained in:
Hannah Cooper
2026-03-11 22:24:20 +00:00
committed by gitbook-bot
parent aaa41c94da
commit ce192824e6
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
faqs/getting-started/why-do-we-recommend-using-the-edge-agent-instead-of-the-traditional-agent.md
View File

@@ -9,7 +9,7 @@ The Edge Agent unlocks Portainer’s full Edge Compute feature set, including:
* [Edge Stacks](../../user/edge/stacks/) - deploy and manage stacks across distributed systems from one place.
* [Edge Jobs](../../user/edge/jobs.md) - schedule scripts or tasks on edge hosts.
* [Edge Configurations](../../user/edge/configurations.md) - pre-deploy config sets to environments.
* [Agent updates](../../admin/environments/update.md) and [policy management](/broken/pages/sVXwh5AjWlxKSXVhHQ5d) - centrally manage agent versions and policies across fleets.
* [Agent updates](../../admin/environments/update.md) and [policy management](../../admin/environments/policies/) - centrally manage agent versions and policies across fleets.
These capabilities don’t exist with the traditional Agent, which is focused on basic connectivity rather than edge orchestration.