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] Support nesting in .config dotfolders #998

Open
vilkinsons opened this issue Aug 15, 2023 · 4 comments
Open

[feature] Support nesting in .config dotfolders #998

vilkinsons opened this issue Aug 15, 2023 · 4 comments
Labels
enhancement New feature or request

Comments

@vilkinsons
Copy link

Is your feature request related to a problem? Please describe.

Ever-expanding dot clutter in the root of projects is a scourge. I appreciate that you've buried all of yours in a single .moon folder, but this could be improved slightly further.

Describe the solution you'd like

Allow for the .moon folder to be relocated to .config/moon instead. Renovate do something similar, except optionally allow their configurations to be buried within platform-specific .github or .gitlab directories.

Describe alternatives you've considered

n/a

Additional context

We're considering adopting Moon in our # and Þ repos. This would be appreciated.

If you support this, you can get added to the dot-config ecosystem list, as well: https://dot-config.github.io/ (although it is wildly incomplete)

@vilkinsons vilkinsons added the enhancement New feature or request label Aug 15, 2023
@milesj
Copy link
Collaborator

milesj commented Aug 16, 2023

While I'm a big fan of the .config folder approach, the .moon folder contains a lot of non-config files. Some examples are all build caches, VCS hooks integration, Docker stuff, and more.

Would feel a bit weird to nest all that under .config.

@vilkinsons
Copy link
Author

vilkinsons commented Aug 19, 2023

Hey @milesj, thanks for the response. How much of that stuff needs committing to Git? Presumably it is just the config parts? No opposition here to having the rest remain in a .moon folder, and/or having this available on a purely opt-in basis.

p.s. we've been looking for a good Rust/TS monorepo solution for a while as we have Rust libs we maintain like error-stack side-by-side a ton of TS projects in our public monorepo. Excited to see y'all working on this!

@milesj
Copy link
Collaborator

milesj commented Aug 24, 2023

Fair enough. I'll look into it for a future release.

@vilkinsons
Copy link
Author

Awesome, thanks @milesj. This plus Renovate support would both help with entropy a lot (in our use case). :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Development

No branches or pull requests

2 participants