Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add CLI switch to flores init to allow for existing base dir #9

Closed
kokkonisd opened this issue Jan 17, 2023 · 0 comments
Closed

Add CLI switch to flores init to allow for existing base dir #9

kokkonisd opened this issue Jan 17, 2023 · 0 comments
Assignees
Labels
enhancement New feature or request

Comments

@kokkonisd
Copy link
Owner

Currently, the init subcommand has a sort of "safety feature" where it will decline to initialize a default site given a non-empty directory. I think that's still useful, because it prevents the user from accidentally destroying a directory. However, there are cases where you might legitimately want to do that; init should have some sort of switch (maybe -f/--force?) to initialize a site even if the directory exists, without destroying the current content of the directory (only adding what's necessary for the site to function).

@kokkonisd kokkonisd added the enhancement New feature or request label Jan 17, 2023
@kokkonisd kokkonisd self-assigned this Jan 17, 2023
kokkonisd added a commit that referenced this issue Jan 21, 2023
The `-f/--force` switch allows the initialization command to proceed
even if the project directory already exists.

[#9]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant