-
Notifications
You must be signed in to change notification settings - Fork 339
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
Example for extending the flake module #664
Comments
@roberth maybe you can help here, how can additional devenv modules be specified? |
All NixOS modules can be extended further with the 'imports' key (array of files containing modules). Have you tried doing that already? |
@thenonameguy I haven't, but the challenge I see is that I don't want to extend the flake-parts module, I want to extend devenv directly. It's possible I'm missing something obvious though. |
Not sure exactly in which way you want to extend it, but here's one: I think that's what @thenonameguy wanted to suggest. If the import needs to reference another repo, I could write something for the case where both repos are flake based. Otherwise I have to ask: @domenkozar Can devenv.yaml import a devenv module from a flake attribute? |
Thanks @roberth , I believe that's exactly what I was looking for.
In my case, I'd like to reuse a set of modules across a number of repos, so yeah, I'm thinking something like this: {
inputs = {
# ...
}
outputs = inputs@{ ... }: {
devenvModules = {
default = {};
};
}
} And then import that module in a shell. Let me give this a try and get back to you. |
Does that work? :) |
I'm trying to add custom features to the flake module that would help with some deduplication across a few environments:
I'm also using flake-parts.
Can someone point me in a direction for extending the devenvType?
The text was updated successfully, but these errors were encountered: