Seperate built in commands from custom on help #21

Activity

1. dkarzon commented on Jan 16, 2012

   

   dkarzon

   on Jan 16, 2012

   Contributor

   More actions

   Maybe one of the Attribute properties could be a group?
   Or clients can manage it and do it somehow in web.config:
   <NetBash> <CommandGroups> <group name="builtin"> <command name="server" /> <command name="uptime" />
   ...?
2. lukencode commented on Jan 16, 2012

   

   lukencode

   on Jan 16, 2012

   OwnerAuthor

   More actions

   I was thinking an optional group param on the attribute could work.
3. dkarzon commented on Jan 16, 2012

   

   dkarzon

   on Jan 16, 2012

   Contributor

   More actions

   hurray!
   But yeah I thought that at first, but then its on the developer to manage the grouping when really you want to give that to the client(?)
4. phdesign commented on Jan 17, 2012

   

   phdesign

   on Jan 17, 2012

   Contributor

   More actions

   I don't see a benefit for the end user to know what's a built in command over custom commands. There's no such equivalent in unix bash right?
5. dkarzon commented on Jan 17, 2012

   

   dkarzon

   on Jan 17, 2012

   Contributor

   More actions

   Its not really just so the end user can see what commands are builtin verses custom. Its more for if you had about 50 commands available you can see them grouped by what sort of function they do.

   An example would probably be: a group for user based functions (membership, users online, session details) then a group for web admin (run database scripts, check caching, etc.)
   Just a thought at the moment.

   Also, @lukencode wonder if we could manage the permissions on groups with something like the Authorize action?