feat(cli): Add --directory flag to specify site path#24
Open
feat(cli): Add --directory flag to specify site path#24
Conversation
Adds a `-d, --directory` option to allow running Ukko from
outside the site's root directory.
This makes the development workflow more robust by enabling
commands like `lein run -- -d example` from the project
root, fixing the issue where Ukko previously assumed the
current working directory was always the site root.
The documentation has been updated to reflect this new,
recommended workflow.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Adds a
-d, --directoryoption to allow running Ukko from outside the site's root directory.This makes the development workflow more robust by enabling commands like
lein run -- -d examplefrom the project root, fixing the issue where Ukko previously assumed the current working directory was always the site root.The documentation has been updated to reflect this new, recommended workflow.