Support This Project

Ticket #96 (new enhancement)

Opened 2 years ago

Last modified 1 year ago

Make site-commands consistent

Reported by: simmel Assigned to: anonymous
Priority: normal Milestone: 0.9.0
Component: server core Version: 0.8.1
Severity: tweak Keywords:
Cc: virdiq, pollux

Description

site-commands needs to be restructured to be consistant. I'll be editing and updating this for a while (busy at work) so don't assign it, because you'll get loads of mail =D

We make a decision. Either we use site change/add/delete user/group or we use site user/group add/change/delete.

Legacy support for glftpd syntax is something we should remove IMO. It just confuses. Instead create an wiki page which explains how to go from glftpd to wzd. I've never admined gl, so someone else needs to make it.

site group

#53 as a point.

Change History

04/25/07 06:59:45 changed by simmel

  • owner changed from pollux to anonymous.

The default group-subcommand should be the most used command. IMO this is info, so people can do stuff like this:

site group admin to see what kind of settings an group has and then use:

site group change admin flags OiST to change the flags of it.

Same thing with user.

05/22/07 08:58:57 changed by virdiq

  • cc set to virdiq.
  • version changed from svn to 0.8.1.

I agree with your suggestion here. I would also like to see a simpler site configuration which has commands like:

  • site group [change|delete|add] <group> ...
  • site user [change|delete|add] <user> ...

When change is used, I'd like the see the following syntax:

  • site group change admins field1=value1 field2=value2 field3=value3

Example:

  • site group change admins name=administrators default_home=/home/ftp/something/ flags=+ab-C

The main problem I see is working out parsing spaces (descriptions, taglines, home directories, etc) and also with other parsing complications.

07/10/07 11:49:49 changed by virdiq

  • milestone changed from 0.8.3 to 0.9.0.

11/13/07 06:29:29 changed by simmel

  • cc changed from virdiq to virdiq, pollux.

It's not a bad idea. But for this to be consistent we need to change every other command to use the option=value syntax.

Thoughts pollux?