docs: Expand + clarify --embed
docs, esp. for usage without alias
#206
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Another small docs PR for
--embed
flag usage 🎏My main goal here was to add documentation for the way
--embed
behaves without an alias for the source directory, which writes the contents of the source directory into the root* of the embedded FS without any containing subdirectory. This behavior, while perfectly ergonomic for making a file server, had confused me briefly as a new user (see #202).Since the
--embed
examples in the README have been expanded + annotated, I removed the inline example from the command usage text in the source code. I think using this space for text that documents the unaliased behavior is worth it, but I'm happy to re-add the inline example if preferred.*yes, technically into the
/files
intermediate dir, but this is the root from the user's perspective