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

feature request: 'nanoc compile --config' #70

Open
0x1eef opened this issue Nov 23, 2024 · 2 comments
Open

feature request: 'nanoc compile --config' #70

0x1eef opened this issue Nov 23, 2024 · 2 comments

Comments

@0x1eef
Copy link

0x1eef commented Nov 23, 2024

Would it be possible for the nanoc compile command to accept a --config option that
would point at nanoc.yaml ? Tools like webpack and typescript's compiler provide a similar
feature, and it would be nice if nanoc could do the same.

I looked into it briefly and it appeared that it would require some refactoring. If a path was
given then we would use its contents to determine the "site dir" instead of how enter_site_dir
and friends currently work. It might require some effort but I'm curious if there's interest in supporting
a feature like that. Thanks

@denisdefreyne denisdefreyne transferred this issue from nanoc/nanoc Nov 24, 2024
@denisdefreyne
Copy link
Member

That would most likely be possible. As you said, it would indeed require some refactoring beforehand.

Can you let me know what your use case would be?

@0x1eef
Copy link
Author

0x1eef commented Nov 24, 2024

Thanks!

Can you let me know what your use case would be?

I have organized the configuration files of my website in the etc/ directory. The rubocop.yml, tsconfig.json, and webpack.*.js configuration files all live there. The idea would be to eventually move nanoc.yaml as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants