Closed melvincarvalho closed 5 months ago
@elipsis-dev can you create an issue for this?
Sorry, I don't know how to help with that. If you tag me (@ellipsis-dev) in a comment, I can do one of these things (but not multiple at once):
@elipsis-dev are the command line arguments well orginaized here?
The command line arguments in the README file appear to be well organized. They are clear, concise, and logically grouped, with optional arguments clearly marked. If there are specific changes or a different organization you would prefer, could you please provide more details?
Responding to this comment by @melvincarvalho. For more information about Ellipsis, check the documentation.
@elipxis-dev do they match the commands in bin/nosdav.js
@elipsis-dev do they match the commands in bin/nosdav.js
Yes, the command line arguments listed in the README file do match the ones in the bin/nosdav.js
file. Both include the 'key', 'cert', 'port', 'root', 'https', 'mode', and 'owners' arguments. The 'owners' argument is handled as a csv in both places, with the bin/nosdav.js
file splitting it into an array for internal use.
Responding to this comment by @melvincarvalho. For more information about Ellipsis, check the documentation.
@elipsis-dev could the true/false command line options be done better?
@melvincarvalho, I have addressed your comments in pull request https://github.com/nosdav/server/pull/17
Summary:
This PR updates the
README.md
to mark certain server options as optional, enhancing documentation clarity.Key points:
README.md
to clarify that-k/--key
,-c/--cert
, and-o/--owners
options are optional.Generated with :heart: by ellipsis.dev