Navigation Menu

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

nixos/calibre-server: Add address configuration #73110

Closed
wants to merge 2 commits into from

Conversation

endocrimes
Copy link
Member

@endocrimes endocrimes commented Nov 9, 2019

This commit introduces two new fields into the configuration of calibre-server, listenAddress and port. These allow the operator to configure the addresses that calibre should listen on, and the port it should bind to respectively.

The default values here are copied from calibre itself, to avoid backwards compatibility issues or more complicated service configuration.

Motivation for this change

calibre defaults to listening on port 8080 on all interfaces, which isn't ideal in almost any configuration outside of developing calibre itself. Exposing this configuration lets people run calibre more reasonably.

Things done
  • Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
  • Built on platform(s)
    • NixOS
    • macOS
    • other Linux distributions
  • Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
  • Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
  • Tested execution of all binary files (usually in ./result/bin/)
  • Determined the impact on package closure size (by running nix path-info -S before and after)
  • Ensured that relevant documentation is up to date
  • Fits CONTRIBUTING.md.
Notify maintainers

cc @domenkozar @pSub @AndersonTorres

This commit introduces two new fields into the configuration of
calibre-server, listenAddress and port. These allow the operator to
configure the addresses that calibre should listen on, and the port it
should bind to respectively.

The default values here are copied from calibre itself, to avoid
backwards compatibility issues or more complicated service
configuration.
default = "::";
example = "127.0.0.1";
description = ''
The interface on which to listen for connections. The value "::" will
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we change it to The address on which to listen for connections

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could do - I was keeping it inline with the upstream documentation for now, but don't feel strongly either way.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

OK. Thanks for the explanation.

@endocrimes
Copy link
Member Author

endocrimes commented Apr 7, 2020

Hey @domenkozar / @pSub - Was hoping that one of you may be able to take a look at this soon? Thanks!

@stale
Copy link

stale bot commented Jun 4, 2021

I marked this as stale due to inactivity. → More info

@stale stale bot added the 2.status: stale https://github.com/NixOS/nixpkgs/blob/master/.github/STALE-BOT.md label Jun 4, 2021
@AndersonTorres
Copy link
Member

@endocrimes PING

@stale stale bot removed the 2.status: stale https://github.com/NixOS/nixpkgs/blob/master/.github/STALE-BOT.md label Nov 12, 2021
@stale stale bot added the 2.status: stale https://github.com/NixOS/nixpkgs/blob/master/.github/STALE-BOT.md label Jun 19, 2022
@Petemir
Copy link

Petemir commented Oct 20, 2022

@endocrimes Any chance of solving the conflict? Thanks!

@stale stale bot removed the 2.status: stale https://github.com/NixOS/nixpkgs/blob/master/.github/STALE-BOT.md label Oct 20, 2022
@pSub
Copy link
Member

pSub commented Oct 28, 2022

@AndersonTorres Why are you closing this issue? I tried to resolve the conflicts yesterday. Somehow ofborg fail and I wanted to investigate this weekend.

@AndersonTorres
Copy link
Member

Two years and the original poster ignored the pings and replies. I closed it because it was abandoned.

If anyone is interested, certainly it can be reopened.

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

Successfully merging this pull request may close these issues.

None yet

8 participants