From 32e45107f7cd9d1fab279ffbbecaa51e132bec08 Mon Sep 17 00:00:00 2001 From: Leopold Talirz Date: Fri, 31 Jan 2020 12:48:22 +0100 Subject: [PATCH] add hint on dokku-acl The deployment documentation on scoping user access pointed only to the development documentation for implementing plugins to handle user scoping. Added link to the dokku-acl plugin, which already handles user scoping out of the box. --- docs/deployment/user-management.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/docs/deployment/user-management.md b/docs/deployment/user-management.md index ae0cd96a5..87cfa460a 100644 --- a/docs/deployment/user-management.md +++ b/docs/deployment/user-management.md @@ -72,7 +72,9 @@ dokku ssh-keys:remove KEY_NAME ## Scoping commands to specific users -Keys are given unique names, which can be used in conjunction with the [user-auth](/docs/development/plugin-triggers.md#user-auth) plugin trigger to handle command authorization. Please see the documentation on that trigger for more information. +The community-provided [dokku-acl](https://github.com/dokku-community/dokku-acl) plugin allows restricting dokku commands and push privileges for apps to specific users. + +For *development* of plugins for scoping commands, see the documentation on the [user-auth](/docs/development/plugin-triggers.md#user-auth) plugin trigger to handle command authorization. ## Granting other Unix user accounts Dokku access