-
-
Notifications
You must be signed in to change notification settings - Fork 14.9k
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
etesync-web: init at 0.6.1, nixos/etesync-web: init module and test #130680
base: master
Are you sure you want to change the base?
Conversation
8da3406
to
a405e21
Compare
Result of 2 packages built successfully:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would be very reluctant to accept 24k new lines for a single package.
}; | ||
defaultServer = mkOption { | ||
type = with types; nullOr str; | ||
default = if etebaseHost != "0.0.0.0" then etebaseHost else null; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you explain this line? Why is 0.0.0.0 not a valid value?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'll clarify with a comment. But the idea is that etebase-server's default allowed_host1 is 0.0.0.0, so I'm only setting the etebase host if its not the default.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this is actually useful, since it won't cause etesync-web
to be rebuilt for the default setup.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I suggest default = "0.0.0.0"
. The resulting package will be cached anyway due to the test.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I suggest default = "0.0.0.0". The resulting package will be cached anyway due to the test.
Thats not a working or sane default. If you enable etesync-web without an etebase server then the best default is the official etebase server instance(etesync.com). That way etesync-web will actually work without setting a server. 0.0.0.0 doesn't really mean anything.
Thats not really fair, the standard way to package yarn2nix without IFD involves committing the lockfile and yarn2nix output. I'm just followed the standard, your concern is more about nixpkgs semantics itself. |
I marked this as stale due to inactivity. → More info |
Co-authored-by: Sandro <[email protected]>
Still relevant to me |
|
Motivation for this change
Provide the official web ui for etesync and make it easy to setup.
Things done
sandbox
innix.conf
on non-NixOS linux)nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
./result/bin/
)